rollercoaster@xxxxxxxxxxxxxxxxxxx wrote: > Am Mittwoch, 16. November 2005 17:42 schrieb Lucian Muresan: >> That beeing said, Klaus & everyone, what would you think about letting >> me give it a try? I think and I hope I'll be able to provide a patch in >> few days, with all existing translations migrated to the new aproach and >> adapted makefiles (maybe until this weekend, depending on spare time), >> in the meantime we could discuss the concept, maybe I'll have questioons >> for few details (maybe there are issues other than spare time or >> priorities which made you plan this for 1.5.x). Well, in the end we'll >> see if it's good or not, but we might have the chance to workout the >> breakage in this i18n matter only once and already now (as I said, I >> think I'll be able to do it myself, so it's up to me to find the time, >> and I'll promise I'll yell or let it be if I happen to get stuck, you >> won't have to wait for this if you already plan a feature-freeze for >> releasing 1.4, I only think we could give it a shot, it might turn out >> good enough for having it merged). But please tell me if there is >> ablsolutely no interest for this now. > Seems that you already made some serious thoughts about how this could be > done. > I already thought that Klaus does not want to make major concept changes until > 1.4 is out but if you still want to go for it i wouldn't mind ;) > > @Klaus > did you already make some thoughts about the message format? would gettext be > your choice? do you have other ideas? > > Just a few remarks and thoughts of mine: > - it would be nice if we would not "lose" the already existing translations They wouldn't get lost. > - i would like to have only _one_ language source file for everything to let > the translators deal with. how could we archive that not every plugin has to > be translated on it's own? (we would have some resellers and even > users/customers that could deal with the translations, but only if its easy > to handle for them. i already realized that it's not practicable to send them >> 25 files) I don't see why they should be all sent to one translator. > - i also like your idea of making translation files (.mo) hashable in memory > to speed up things. > I would basicly load them to be accessible in a similar way as they are now. Lucian
