Greetins everybody, My name's Francisco Marzoa and I'm from Spain. I work as software developer and system administrator in a little company that's mainly focused on RFID technologies. We're interesting in adding RFID capabilities to koha, but somework must be done before. I've superficially seen koha's code a few minutes ago and I've seen that there's no internazionalization (i18n) and/or localization (l10n) support, (maybe I'm wrong?). Of course, we're interesting in translate Koha mainly to spanish, but I think that we can do it better than only getting the sources and translating strings. Among other things, without (translatable) resource isolation, if we change some koha's code functionality, we'll have to repeat that changes in every language, even if that changes doesn't imply strings. I've seen that in contribute's page TODO there is a "Translate things" entry, but I think the better could be if we prior to code translation, we do prepare that code for internazionalization and localization. I can contribute doing the whole string isolation (prepare code for i18n and l10n) and, later, with an spanish koha translation. Please, let me know what do you thing about this and... excuse my english! Cheers,
"Francisco M. Marzoa Alonso" schrieb:
I can contribute doing the whole string isolation (prepare code for i18n and l10n) and, later, with an spanish koha translation.
Ola Francisco, nice to hear from someone from spain willing to contribute to koha. At the moment we have a very active french translation-team and mainly me as the german translatin-"team". At this point Koha implements a templating-system for i18n and l10n. See http://www.koha.org/contribute/templating/index.html for more information. Not all scripts have been templated yet and we're also still lacking some routines for l10n. (Translating mister -> senor, Monsieur, Herr) Dorian
Dorian Meid wrote:
Ola Francisco, nice to hear from someone from spain willing to contribute to koha. At the moment we have a very active french translation-team and mainly me as the german translatin-"team". At this point Koha implements a templating-system for i18n and l10n. See http://www.koha.org/contribute/templating/index.html for more information. Not all scripts have been templated yet and we're also still lacking some routines for l10n.
Note that I suggested the 2 new french developers (hdl and David) to work on templating everything in koha. I think it's a not-to-hard job, and a good way to enter koha code. David already did one in admin hdl already did one (newbasket2.pl, commited by me yesterday, after some testing) too. If 1.2 manager wants to backport them from main branch to 1.2, it should be easy and without pain. -- Paul
paul POULAIN schrieb:
hdl already did one (newbasket2.pl, commited by me yesterday, after some testing) too.
If 1.2 manager wants to backport them from main branch to 1.2, it should be easy and without pain.
BTW: Can someone tell me which pieces of code should go in which branch? Sometimes I have the impression that two snippets relying on each other are spread over two branches. How do we work with the branches in koha? dorian
On Wed, 6 Nov 2002, Dorian Meid wrote:
paul POULAIN schrieb:
hdl already did one (newbasket2.pl, commited by me yesterday, after some testing) too.
If 1.2 manager wants to backport them from main branch to 1.2, it should be easy and without pain.
BTW: Can someone tell me which pieces of code should go in which branch? Sometimes I have the impression that two snippets relying on each other are spread over two branches. How do we work with the branches in koha?
rel-1-2 should have very limited changes in functionality, and all new features should get added in the trunk. The reason for this is that rel-1-2 is supposed to be our stable branch and big changes make stability hard to maintain. There are also release managers for each of the branches who have the final say on what can and cannot go into their branch. For 1.2 that's Chris Cormack, for 1.3 it's Paul Poulain. In addition to this rule of thumb... any bugs that affect both branches should be fixed in both branches, ideally in an identical fashion so that there are no conflicts when merging the two changed files back together. By identical, I mean that if you are looking at the file shelf.pl in a checkout of the trunk branch of Koha and run: cvs diff -r rel-1-2 shelf.pl There should be no differences in the two versions of the file in the section where you fixed the bug. Steve.
participants (4)
-
Dorian Meid -
Francisco M. Marzoa Alonso -
paul POULAIN -
Tonnesen Steve