From: David S. <dav...@gm...> - 2006-01-24 12:07:16
|
On 1/24/06, David Stevenson <dav...@gm...> wrote: > > > > On 1/24/06, Massimo Maiurana <mai...@gm...> wrote: > > > > > > hi all, > > I've just made an it.po file for e17 which contains also translated > > strings for every module in the e_modules cvs directory. > > I thought that modules, not being separate applications but living > > inside E, should share a single .mo file with enlightenment itself > > (otherwise I don't see how they can be translated). > > > This was was I thought at first too, but it turns out that it is possible > for an application to have more than a single .mo file in use at once: > > http://edevelop.org/node/1853 > http://edevelop.org/node/1860 > > I have added support in the moon module (and there will be a new version > in the next few days that actually has some more strings to translate!), = and > I noticed that the evolume module too started adding support in this > fashion. > This hasn't been done for the e_modules though, possibly just because no > one got around to it yet? I don't know of any problem with this idea. > > please, let me know either if I'm making wrong assumptions or if I > > can commit this file in cvs. > > > For 3rd party modules not in cvs I think there is no option but to use a > seperate .mo file > For "3rd party modules" that are in cvs, that option makes assumptions > that the user has checked out e_modules (all of them) by the time e's > ./autogen.sh grabs all the strings from the source for translation. I > personally only check out e_modules one by one - and most of them not at > all! > Excuse me for replying to myself, but I was thinking some more and what I wrote is really only a problem in terms of maintaining the strings in one file. However this might get messy with modules changing their strings afte= r e17 is released. Fine for cvs users, but for package maintainers downstream it might be a hassle having to update the e17 .mo file because some new module was added, or because existing modules changed their strings. At any rate, if the dev team likes the idea, I'd be happy to put together some patches for the e_modules along the lines of what I did to add i18n support to the moon module... just give me a yay or nay. Regards! David Anyway, I mainly wanted to note that it is possible to have a module > specific .mo. It's also possible for those module .mo's to use strings fr= om > the main e .mo, if they wish. > > Regards! > David > |