On Sun, 25 Jun 2006 06:06:15 +0200 Roland Mainz wrote: > - The libast API is AFAIK different from the normal Solaris libc API for > that (David/Glenn, please correct me if I am wrong here) so the *.po > stuff will likely not be used.
we generate the l10n files for the whole source tree via nmake and a cc(1)-api-like command that extracts the strings to be localized the runtime files are in an ast form the ast msggen(1) command can list these in utf-8 gencat(1) form for editing if solaris uses another form we can tweak msggen(1) to translate to that form at runtime all localized strings are accessed through the libast errorx() we use the C locale text strings as lookup keys (that way if l10n fails at least C locale text is available) the keys maps to catopen(3) indices since everything goes through errorx() that can also be tweaked to match solaris > - Only a microscopic fraction of languages+encodings supported by > Solaris is currently provided by upstream. We really need more > translators... this has always been the weakest link our truest translations are fudd and swedish chef in some cases the english could use help too -- Glenn Fowler -- AT&T Research, Florham Park NJ --
