Translation for 3.12 using transifex (feedback)
Hello, Using transifex to translate Koha to french is a real success. Thanks to the improved ergonomy of transifex, compared to pootle, a lot of french librarians have participated to the translation (I think 6 different people, but there is no statistics about that in transifex) The more we use it, the more we like it. There is only one thing that I could not understand : how to UPDATE a translation when there are more english terms to translate. It seems you can't. The workaround I've used is: - in transifex, download the .po files for 3.12.0-beforeStringFreeze - in console ./translate update fr-FR and ./translate update en - in transifex, create new ressources and obsolete/delete old ones - create a new ressource "staff for 3.12", upload english and then upload french translation (this being done for the 4 files to translate) It's not a big deal, but not the best possible choice either. I just updated pootle with all those strings. To do so = - in transifex, download the .po files on your computer - in pootle, you must have admin permission, go to language overview (http://translate.koha-community.org/fr/312/), upload the files, choosing "Overwrite the current file if it exists". It's a little bit long for staff client (3 to 5 minuts), but it work fine. => french translation 99% done, only 499 strings still waiting for translation in staff (should be done tomorrow) (If another language team want to join the french team on transifex, I've no problem with giving you language coordinator permission on transifex) HTH -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
Hello Paul and everybody About Transifex/Pootle : Maybe Transifex is better on some points, but it is not perfect... As Pootle is an opensource tool, with active community, why not take part in its development, or at least take contact with its developping community? *In my opinion, on a "basic translator" point of view, here is some missing features in Pootle : ** *- a way to do an exact search on a string ex : "avail" will search all strings with words begining with avail => hard to find the good string - a way to do an exact search on a phrase ex : "big record" will search all strings with "big" or with "record" => hard to find the good string - a way to do an combined search on an english string, a translated string, and a filename Do you have other ideas? Mathieu Le 16/05/2013 15:15, Paul Poulain a écrit :
Hello,
Using transifex to translate Koha to french is a real success. Thanks to the improved ergonomy of transifex, compared to pootle, a lot of french librarians have participated to the translation (I think 6 different people, but there is no statistics about that in transifex) The more we use it, the more we like it.
There is only one thing that I could not understand : how to UPDATE a translation when there are more english terms to translate. It seems you can't. The workaround I've used is: - in transifex, download the .po files for 3.12.0-beforeStringFreeze - in console ./translate update fr-FR and ./translate update en - in transifex, create new ressources and obsolete/delete old ones - create a new ressource "staff for 3.12", upload english and then upload french translation (this being done for the 4 files to translate) It's not a big deal, but not the best possible choice either.
I just updated pootle with all those strings. To do so = - in transifex, download the .po files on your computer - in pootle, you must have admin permission, go to language overview (http://translate.koha-community.org/fr/312/), upload the files, choosing "Overwrite the current file if it exists". It's a little bit long for staff client (3 to 5 minuts), but it work fine.
=> french translation 99% done, only 499 strings still waiting for translation in staff (should be done tomorrow)
(If another language team want to join the french team on transifex, I've no problem with giving you language coordinator permission on transifex)
HTH
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
Paul, Using transifex to translate Koha to french is a real success.
Thanks to the improved ergonomy of transifex, compared to pootle, a lot of french librarians have participated to the translation (I think 6 different people, but there is no statistics about that in transifex) The more we use it, the more we like it.
Speaking as RM, I was rather less thrilled with the results. When I installed the French translations in order to take a screenshot (twelve hours before I planned to release 3.12.0!), I found that in the translation process, many XML entities were broken, resulting in XSLT being entirely unusable in French. This sort of entity breakage could -- and did -- happen in Pootle, of course, but there seemed to be a lot more broken entities in the French files than in other translations. Twenty versus less than ten in every case. My conclusion from this is that Transifex may make translation easier, but it also makes it easier to add errors like in place of . In order to avoid putting out releases with broken languages in the future, it might be a good idea to add unit tests for the PO files that checks for broken entities, %s mismatches, etc.
From a philosophical point of view, of course, an open source tool like Pootle is superior as well, but my principle concern is technical.
Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/
Le 20/05/2013 14:11, Jared Camins-Esakov a écrit :
My conclusion from this is that Transifex may make translation easier, but it also makes it easier to add errors like in place of .
It's not sure. It may come from the fact that French typography requires colon punctuation mark to be preceded by a space. Not the case in English. Maybe not the case in other languages. It might not be a specific Transifex flaw.
In order to avoid putting out releases with broken languages in the future, it might be a good idea to add unit tests for the PO files that checks for broken entities, %s mismatches, etc.
+1 For the time being, this is to each language translation team to ensure that there translation doesn't contain any default. This isn't that bad since it delegates the translation validation job to those who are effectively doing it. So any unit test for translation should try to send their result to the translators rather than to the Release Manager or Translation Manager who have enough to do.
From a philosophical point of view, of course, an open source tool like Pootle is superior as well, but my principle concern is technical.
I kindly disagree with you from an immanent point of view, even if I transcendently agree. Kind regards, -- Frédéric DEMIANS http://www.tamil.fr/u/fdemians.html
Le 20/05/2013 14:36, Frédéric Demians a écrit :
Le 20/05/2013 14:11, Jared Camins-Esakov a écrit :
My conclusion from this is that Transifex may make translation easier, but it also makes it easier to add errors like in place of . It's not sure. It may come from the fact that French typography requires
colon punctuation mark to be preceded by a space. Not the case in English. Maybe not the case in other languages. It might not be a specific Transifex flaw.
It was also a "timing" problem. We finished our translation work "just in time" for 3.12.0, so we had very very little time to test the files. I plea guilty for the : in the past, this entity has been added in a lot of strings before ":" sign, but not in every string. So each time I found - by chance - a string with a bare ":", I decided to add the in order to make the french templates more coherent. But when I tested it and found the mistakes, there were some problems (locked files) in our Transifex instance, so I was not able to fix the mistakes :( Mathieu
In order to avoid putting out releases with broken languages in the future, it might be a good idea to add unit tests for the PO files that checks for broken entities, %s mismatches, etc. +1
For the time being, this is to each language translation team to ensure that there translation doesn't contain any default. This isn't that bad since it delegates the translation validation job to those who are effectively doing it. So any unit test for translation should try to send their result to the translators rather than to the Release Manager or Translation Manager who have enough to do.
From a philosophical point of view, of course, an open source tool like Pootle is superior as well, but my principle concern is technical. I kindly disagree with you from an immanent point of view, even if I transcendently agree.
Kind regards,
-- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby@univ-rennes2.fr
participants (4)
-
Frédéric Demians -
Jared Camins-Esakov -
Mathieu Saby -
Paul Poulain