> From: bill lam <[email protected]> > > On Mon, 19 Oct 2009, Chris Burke wrote: > > bill lam wrote: > > > I'm ok with the english language messages in j ide, but as we'll soon > > > have a > > > totally new ide, and for the benefit of new j users, > > > > > > 1. is i18n needed? > > > 2. if yes, should it be implemented with gnu gettext or home-brew > > > scheme? > > > > Good idea. I think we should call gettext on any string that might need > > translating, where gettext is initially gettext=:] . This should allow > > anyone to translate the strings later on.
How about form layouts? > It also need to write a utility to extract all J strings excluding > those inside comment, explicit noun definition, or right after [123] : > > However assuming [n]gettext is already inserted there, we could cheat. What does "right after [123]" mean? Why "all J strings"? Isn't extraction directed at only the place where i18n lookup takes place. Not all strings require translation. I believe gettext is too C-like--too long and too generic a name. An alternative and more suggestive name is "i18n". Here's an i18n suggestion made earlier: http://www.jsoftware.com/jwiki/OlegKobchenko/Unicode%20Test%20Drive#Localization ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
