From: Chris W. <ch...@cw...> - 2005-03-08 15:14:09
|
* Teemu Arina (te...@di...) [050305 11:39]: >... > I've got four thumbs up here. Gettext in the I18N side ;) I had a thought about this. From what I understand gettext uses .po files to store its data. These are text files in a particular format. There's a perl module Locale::Maketext::Lexicon [1] that's able to read PO or MO files into Locale::Maketext format, which is what we're using. What if OI2 supported both its native .properties format as well as the PO format? (I'm not sure where the MO format comes from, but if it's easy to support we could throw that in as well.) That would allow you to use existing l10n-editing tools but OI2 to continue to use its existing framework. Is that reasonable/possible? FWIW, I'm also still noodling over the abstract vs concrete message keys and *may* wind up automatically translating all keys in OI2 to concrete. Chris [1] http://search.cpan.org/~autrijus/Locale-Maketext-Lexicon-0.47/ -- Chris Winters (http://www.cwinters.com) Building enterprise-capable snack solutions since 1988 |