At 01:05 AM 8/15/2003, Dan Oscarsson wrote: >Kurt D. Zeilenga wrote: > >>> >>>You are right, I was thinking only of the attributes representing >>>text values. Not any binary values. Is there a text attribute that is not >UTF-8 encoded? >> >>Yes. >> >>>If so, what character encoding does it use? >> >>I've seen UTF-16, UTF-32, T.61, and a few others... all over LDAPv3. > >What is the name of the attribute?
The names are locally defined. My point here is that the API cannot assume that values of "foo" are transferred as UTF-8 encoded Unicode. "foo" could be T.61. >Can I get commonName back as UTF-32? Since commonName is not a standardized LDAP attribute type name (the X.500 commonName attribute is called CN in LDAP), I couldn't say what syntax/encoding values associated with the commonName attribute description might be without significant more context-specific information. >I thought that one of the good points with LDAPv3 was that >finaly a standard encoding was defined for text values of attributes. The good thing about LDAPv3 is that it doesn't restrict schema designers to a fixed set of syntaxes/encodings. If I need to store a ShiftJS string in an LDAPv3 directory, I can.
