http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8044
--- Comment #13 from D Ruth Bavousett <r...@bywatersolutions.com> --- Frédéric, By the nummbers: 1) I don't have a firm opinion either way on this, myself, but I do like what I see with Locale::TextDomain; it's pretty nice. For the sake of readability, I'd put in a vote for Locale::TextDomain. I'd like to see how we can use it for templates, in another bug, so we don't lose scope here. 2) That is easily-enough accomplished; I can do that work, if Julian hasn't the time for it; we need *some* solution to this part of the problem right away in the Arabic work I'm on right now. 3) I concur that we need a larger discussion of the translation mechanism; the vast number of strings that are present in the staff templates, in particular, make translation increasingly hard. I would like to be part of that discussion, but IMO if we use this as a beachhead for a new way of thinking, then migrate the other parts of the problem into it--where the current mechanism can be used, until we get things switched over fully--then that would probably be best. So the process becomes: a) figure out which library to use, and implement for translating strings directly from Perl--the scope of this bug b) move other parts of the current framework into the new mechanism in a way that doesn't slow things down overmuch c) rejoice! -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/