I will not give up untill someone...
...untill someone gives me an explicit reason why we do not have a localization of koha the way it is suggested on the web (cpan.org). Namely, I have read through some modules in cpan directory and have found this: Locale::PO Manipulate .po entries from gettext Locale::Maketext Framework for software localization Locale::gettext Multilanguage messages Locale::PGetText What GNU gettext does, written in pure perl Now, I am wondering whether any of the above modules would be fit to be implemented in koha project. Is it to late to even think about it? Right now, as I see it, for every theme in same language one needs redundant and complete language strings in each file. A gettext like solution might save a bit of work in the future. regards, Benedict. Disclamer: I am not a programmer and I do not have an idea what perl language is... I am just a computer operator.
On Mon, 2003-09-29 at 06:13, Benedykt wrote:
...untill someone gives me an explicit reason why we do not have a localization of koha the way it is suggested on the web (cpan.org).
Hi Benedykt. Ok, the templates serve more than localisation purposes, thats why we are using them. They allow people to customise a lot more.
Namely, I have read through some modules in cpan directory and have found this:
Locale::PO Manipulate .po entries from gettext Locale::Maketext Framework for software localization Locale::gettext Multilanguage messages Locale::PGetText What GNU gettext does, written in pure perl
Now, I am wondering whether any of the above modules would be fit to be implemented in koha project. Is it to late to even think about it?
Nope it sure isnt. It is too late to think about it for koha 2.0. But there is no reason we cant have a discussion with all the developers post release and decide to work on a gettext solution to help with translation. We wont get rid of the templates, since the templates allow you to change much much more than language strings. But we might want to suplement their use with using gettext modules.
Right now, as I see it, for every theme in same language one needs redundant and complete language strings in each file. A gettext like solution might save a bit of work in the future.
Yep you are right. For those templates whose only difference is language, using gettext will save some time. Chris -- Chris Cormack Katipo Communications Programmer www.katipo.co.nz 027 4500 789
Chris Cormack wrote:
Nope it sure isnt. It is too late to think about it for koha 2.0. But there is no reason we cant have a discussion with all the developers post release and decide to work on a gettext solution to help with translation.
We wont get rid of the templates, since the templates allow you to change much much more than language strings. But we might want to suplement their use with using gettext modules.
The 2.0.0 release manager (me :-) ) 100% agree. He would have said this if kiwis were not working many hours before europeans :-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2003-09-28 19:13:35 +0100 Benedykt <kb2qzv@poczta.wp.pl> wrote:
...untill someone gives me an explicit reason why we do not have a localization of koha the way it is suggested on the web (cpan.org).
Time. Do you know if any of the localisation (nb spelling! Use English if you are not USian! ;-) ) modules are in the basic perl installation? I couldn't see any and it's a pain to depend on yet another module. -- MJR/slef My Opinion Only and possibly not of any group I know. http://mjr.towers.org.uk/ gopher://g.towers.org.uk/ slef@jabber.at Creative copyleft computing services via http://www.ttllp.co.uk/
participants (4)
-
Benedykt -
Chris Cormack -
MJ Ray -
paul POULAIN