[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Chinese character access

To: John Kristian <kristian@netscape.com>
Subject: Re: Chinese character access
From: "Kurt D. Zeilenga" <kurt@boolean.net>
Date: Fri, 19 Nov 1999 09:50:06 -0800
Cc: Xuan Huan <huanx@moon.bjnet.edu.cn>, openldap-general@OpenLDAP.org
In-reply-to: <3835876D.A3D41AAD@netscape.com>
References: <3.0.5.32.19991119083920.00a45c80@localhost>

At 09:22 AM 11/19/99 -0800, John Kristian wrote:
>But some existing implementations don't conform to this part of RFC 1777.
>Microsoft Exchange Directory represents characters in the server's local
>code page (for example, CP 1252 in Europe).  Netscape Directory Server
>represents characters in UTF-8, in both LDAP v2 and v3.

Okay, I'll restate:

LDAPv2 uses T.61 as required by RFC1777.
LDAPv3 uses UTF8 encoded ISO 10646 characters as required by RFC2251.

Some implementations do not adhere to LDAPv2 or LDAPv3 character
encoding specifications.  Your mileage may vary.

----
Kurt D. Zeilenga		<kurt@boolean.net>
Net Boolean Incorporated	<http://www.boolean.net/>

Follow-Ups:
- Re: Chinese character access
  - From: John Kristian <kristian@netscape.com>

References:
- Re: Chinese character access
  - From: "Kurt D. Zeilenga" <kurt@boolean.net>
- Re: Chinese character access
  - From: John Kristian <kristian@netscape.com>

Prev by Date: Re: Chinese character access
Next by Date: Re: Chinese character access
Index(es):
- Chronological
- Thread