Hi to all, I now that there bugs in develop about a new method to translate MySQL setup and MARC21/Unimarc sql definitions. But, for paid user, i need to create a full italian MySQl setup for 3.12. And I also need to create a full italian MARC21 sql configuration. So, in you opinion what is the best option for Koha comunity ? My plan is: a)I prepare and send patches to translate the present MySQL setup in master and 3.12 but not for MARC21 translation. I think to use two different bug number, one for master update and an other for 3.12 update. Is it OK ? b)About MARC21 translation, I wait and I help in testing the code. I think that the new translation workflow for MARC21 will be present in 3.14. But I can change my plan. Bye Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate
Hi Zeno and all others,
But, for paid user, i need to create a full italian MySQl setup for 3.12. And I also need to create a full italian MARC21 sql configuration. So, in you opinion what is the best option for Koha comunity ? My plan is: a)I prepare and send patches to translate the present MySQL setup in master and 3.12 but not for MARC21 translation. I think to use two different bug number, one for master update and an other for 3.12 update. Is it OK ?
The proposed i18n function in bug 10509 is for master (3.14), and is still in a Needs Signoff state. So we should see if people are willing to test and sign off. If so, it will not be that hard to move all language folders including Italian to the new style in some weeks after that. (With great benefits: less redundancy and ready for inclusion in a Pootle workflow.) If you only focus on translating 3.12 now (and not on master while in transition), we could pickup your translations from your 3.12 translation and insert them in a followup for the Italian language folder. If you also send patches now for 3.14, we will have competing changes and a duplication of effort. If you create a report with patches for 3.12, it could be helpful if you include [3.12 ONLY] or something similar already in the title of the report? Would this work for you?
b)About MARC21 translation, I wait and I help in testing the code. I think that the new translation workflow for MARC21 will be present in 3.14.
Actually same here: Please translate this in 3.12 and have contact again to pickup your changes to incorporate them in a 3.14 followup for it-IT. Hope I was clear enough.. Regards, Marcel
Hi Marcel and all, Il 02/07/2013 11:08, Marcel de Rooy ha scritto:
The proposed i18n function in bug 10509 is for master (3.14), and is still in a Needs Signoff state. So we should see if people are willing to test and sign off.
As soon as possible I will test 10509 on master.
If you only focus on translating 3.12 now (and not on master while in transition), we could pickup your translations from your 3.12 translation and insert them in a followup for the Italian language folder.
Ok, I will prepare the patches only for 3.12 with a clear mark in the name [3.12 ONLY]. For MySQL setup and for MARC21 translation. Bye Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate
participants (2)
-
Marcel de Rooy -
Zeno Tajoli