Re: LDAP i18n meeting log posted; minor interface changes upcoming

[Dan Mosedale]

Paul Sandoz <[EMAIL PROTECTED]> writes:
> 
> >The contents of last week's LDAP internationalization meeting has been 
> >posted here: .
> >
> 
>   From the latest IRC chat there was a question about pab storage:
>   
> " Do you know if the Mozilla AdBook pab currently stores in
>  UTF-8 or in Unicode (which would be UCS-2 or UTF016)?"
> 
>   More specifically the mork client implementation converts
>   wstring attributes into utf8 strings which are
>   then stored:
>   
> http://lxr.mozilla.org/seamonkey/source/mailnews/addrbook/src/nsAddrDatabase.cpp
> #1236 
> 
> 
>   It is the same for the preferences:
>   
> http://lxr.mozilla.org/seamonkey/source/mailnews/addrbook/src/nsDirPrefs.cpp#217
> 9 
>   

That sounds like it is consistent with Momoi's statement about
UTF16/UCS2 (aka PRUnichar * / wstring) being used in interfaces, but
UTF8 being used as the preferred storage mode for Unicode.

>   What does this imply for full i18n support?

I think that once we convert the LDAP XPCOM SDK to wstrings, we'll be
in good shape, at least with regards to LDAPv3 servers that are
following the standard by having their data in UTF8.

>   When converting from/to unicode is any data lossed?
>   or are unicode characters encoded into the UTF string.

When you say "unicode", I assume you mean wstring (UTF16/UCS2)
format.  UTF8 is also a unicode encoding.  As I understand it, UTF8
<-> UTF16/UCS2 encoding is lossless.

Dan
-- 

Re: LDAP i18n meeting log posted; minor interface changes upcoming

[Paul Sandoz]

>The contents of last week's LDAP internationalization meeting has been 
>posted here: .
>

From the latest IRC chat there was a question about pab storage:

" Do you know if the Mozilla AdBook pab currently stores in UTF-8 or in 
 Unicode (which would be UCS-2 or UTF016)?"

More specifically the mork client implementation converts
wstring attributes into utf8 strings which are
then stored:

http://lxr.mozilla.org/seamonkey/source/mailnews/addrbook/src/nsAddrDatabase.cpp
#1236   


It is the same for the preferences:

http://lxr.mozilla.org/seamonkey/source/mailnews/addrbook/src/nsDirPrefs.cpp#217
9   


What does this imply for full i18n support?
When converting from/to unicode is any data lossed?
or are unicode characters encoded into the UTF string.


Paul.

| ? + ? = To question
\
   Paul Sandoz
x19219
+353-1-8199219
 

LDAP i18n meeting log posted; minor interface changes upcoming

[Dan Mosedale]

The contents of last week's LDAP internationalization meeting has been 
posted here: .

Additionally, some minor interface changes are coming.  One batch, in
http://bugzilla.mozilla.org/show_bug.cgi?id=70658 removes a number of 
methods that shouldn't really have been public anyway.  Those methods 
are all the non-scriptable ones as well as 
nsILDAPChannel::*PendingOperation().  These methods were already all 
commented in the IDL as being for internal use only, so I don't expect 
anyone will be using them.

http://bugzilla.mozilla.org/show_bug.cgi?id=71247 is a bug I just filed 
to replace all the XPIDL string stuff in the LDAP XPCOM SDK with 
wstrings so that there's no dataloss during character conversion.

Dan