In article <1043899829.32549.20.camel@tux>, Micheas Herman <micheas@micheas.dyns.net> wrote:
On Wed, 2003-01-29 at 19:36, Andrew Arensburger wrote:
[stuff deleted]
Unless I'm not understanding something, this would mean that a single koha installation could not be multilingual. This seems like the wrong direction IMO.
No, what Andrew proposed is that we keep one set of master templates (the English ones), and a set of translation files. At buildrelease time (or install time), translated templates are generated by applying the translations to the master templates. The advantage of this is that we separate theme from language, and make the list of strings to translate explicit. On the other hand, changes to the English templates will need to be more carefully controlled, and we will need to, among other things, write a script to apply the translations to the master templates. Depending on how this can be implemented, this could be better than the proposal to use TMPL_VAR, because a gettext-based solution could take care of changes in word order. Of course, images cannot be translated this way; they still have to be manually created (or created with script-fu, if we decide to do that for certain languages). This still sounds like a big change (though definitely a welcome change if things work the way we intend them to work out); I don't know what to think of it. -- Ambrose LI Cheuk-Wing <a.c.li@ieee.org>