Hello David, Thanks for your email. I just checked the web site you suggested and looked at the msgcpp(1), msgcc(1), and msggen(1) man pages also.
It appears you've an implementation of I18N/L10N messaging system based on the X/Open Catalog message file format messaging, i.e., the C locale file(s) are in X/Open Catalog message file format which is BTW one of the Sun G11N supported localizable files. <-- It looks that way but since I didn't actualy downloaded and looked into the source code or ran the AST toolkit commands, I'm not 100% sure. If you could confirm on this, that will be really great and thanks... I also noticed that the initial translation is based on the Babelfish. I also use it frequently and I think it is good but not really good enough yet in so many cases and especially to use as translations for message catalogs. And so I think it would be probably ideal for everyone if ksh93 projet team collect the msg file(s), and give it to G11N community, we (G11N) will be able to translated them and deliver into and for various locales (FIGSSCJK and in these days, Pt and Ru too). <-- I'm talking about this in terms of and within the scope of OSo ksh93 project that I'm so far understanding. If there is any misunderstanding from my side, I'd like to hear from you further including any corrections you would like to make. If the above is agreeable, i.e., drop off your messages files to G11N and use L10N service from G11N, the only concern for me is that it seems the ksh is using perhaps different binary file format for the message catalog files that might not be compatible with gencat(1) generated catfiles. In that case, we (the ksh93 project team and G11N) will have to figure out on how and what to support in terms of the actual binary file format for the translated message catalog files. (If necessary, G11N can certainly use AST tookit commands to generate binary translated message files too.) Would you think this is something we can further discuss? And, I recall a message from Young saying that we have already established a process between ON community and G11N at OSo that whenever there is a new ON build, we will receive ON's fresh localizable files which will be then merged with existing translated messages/localized files at G11N source tree and the result will be made available to everyone to download at G11N community's download site. Ienup David Korn wrote at 07/14/06 13:13: > The AST Toolkit has nmake rules for generating the C locale file > containing all the translation phrases that need to be localized > for each command or library. The file that gets generated > contains both error message strings and built-in man page > strings. It generates a list of numbers and strings. > The source code does not use gettext(). Phrases needing translation > are generated by the AST msgcc command which produces the C locale > version of the message file. > > When given the previous C locale file, the message numbers will > be used for phrases that have not changed and new numbers for > new and changes messages. > > For each locale, the user must generate files with the same > set of message number but with the phrases in the current locale. > > The AST toolkit provides commands for converting from the binary > format for locale files into a textual format that can be > used for editing. The binary format uses UTF-8 format for > the messages. > > For more information go to > http://www.research.att.com/sw/download/ > and click on internationalization and look at the man pages > for msgcc, msggen, and msgget. > > > David Korn > dgk at research.att.com
