Re: UTF-8 / Unicode / Local conversions

[Chris Tomlinson <chris@moonvine.org>]

But T.61 is the main requirement for supporting LDAP v2. Also I don't think there is a standard set of T.61
conversions in Java. In fact as far as I know you can represent characters in T.61 that have no correspondence in
UCS-2/UTF-8.

ciao,
Christine Tomlinson

Mark C Smith wrote:

> "Kurt D. Zeilenga" wrote:
> >
> > At 04:09 PM 6/16/00 -0600, Dave Steck wrote:
> > >Applications need a way to display data obtained through the LDAP C API's.
> > >
> > >To provide truly cross-directory and *cross-platform* API's, it seems there should be
> > >a standard set of C APIs to do UTF-8 <--> Unicode conversions.
> > >
> > >There should also be a standard set of API's to convert between either UTF-8 or Unicode and local strings?
> > >Does anyone know of such a standard or work underway?
> > >
> >
> > I believe it appropriate for the IETF LDAPext WG to specify an
> > an C API to converting between the local charset, T.61, and UTF-8.
> >         local <-> T.61
> >         local <-> UTF-8
> >         UTF-8 <-> T.61
> >
> > However, as previously discussed, this can be specified as
> > a (Standard Track) extension.
>
> In most environments, these functions are already provided.  I am not
> convinced that the LDAPEXT group should duplicate the work being done by
> OS and platform vendors.  T.61 may be a special case, but I for one
> would like to let T.61 die.
>
> --
> Mark Smith
> Directory Product Development / iPlanet E-Commerce Solutions
> My words are my own, not my employer's.            Got LDAP?