On Sun, 23 Mar 2008 15:19:26 +1100, Brad Hards <[EMAIL PROTECTED]> wrote:
>> Questions:
>> 1 . Should a bad language name be an error (instead of falling back to
>> en-US)?
Hum maybe can we mix both: display a warning message mentioning the user
he used a bad language and mapiprofile will fall back to default en-US.
>> 2. Do you still want to do a substring match (so, for example, French
>> will produce French_Standard)? I can add that quite easily.
>> Update: I implemented this. I think it makes it more tolerant, which
>> is a good thing.
Great!
>> 3. Is there a way to guess a "sane" codepage and method from the
>> language code. I see something that looks possible ("combinations" in
>> the locales[] structure), but I don't understand it. Basically, I'm
>> looking to replace this:
>> mapi_profile_add_string_attr(profname, "codepage", "0x4e4");
>> mapi_profile_add_string_attr(profname, "method", "0x409");
Good question ... it makes quite some time I have not been looking at this
code.
IIRC, a given language has a unique LCID but can be associated with
different
combinations of input locales: all of them "should be correct" but we can
maybe
consider the first entry "default". Please note the explanation is
approximative
and may be incorrect. Luckily I think I've found the resources we used to
implement
the initial API:
* http://www.microsoft.com/globaldev/DrIntl/faqs/Locales.mspx
* http://www.microsoft.com/globaldev/reference/win2k/setup/lcid.mspx
> 4. One more issue: libmapi/util/locale.c is basically private API. Should
> I make the parts I'm using public?
Sure, but maybe we'd need to clean it and rename functions so it matches
the
general API nomenclature such as locale_ or codepage_
Cheers,
Julien.
--
Julien Kerihuel
[EMAIL PROTECTED]
OpenChange Project Manager
GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
