From: Teemu A. <te...@io...> - 2005-03-08 15:18:28
|
> 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? That's exactly what I had in mind. MO is simply compiled PO. You write your stuff in as PO files and those get compiled in some weird MO files. I don't know which is faster, I guess MO is more designed towards C-based applications. You can manipulate and play around with MO files with tools from the GNU gettext toolset. > 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. Ok ;) -- Teemu Arina, CTO Ionstream Oy / Dicole Komeetankuja 4 A 02210 Espoo FINLAND Tel: +358-(0)50 - 555 7636 skype: infe00 Corporate website: http://www.dicole.com Personal weblog: http://infedelic.blogspot.com "Discover, collaborate, learn." |