Hi,
I don't find any clear rules on when to add/update translatable strings (from the developer point of view). I have a suggestions :
master (dev) : - freely add and change translatable strings
when preparing a future stable (4.0-alpha/rc) - no new translatable strings - no updates that changes the content/meaning of a translatable string (but exceptions allowed after discussion on mailing list) - updates fixing typos and grammar are allowed
current stable (QA_3_5) - no new translatable strings - no updates that changes the content/meaning of a translatable string - updates fixing typos and grammar are allowed
old releases - no maintance on translatable strings (no new strings, no fixes on existing strings)
What do you think? BTW : the reason I mentioned allowing grammar/typo fixes in current stable, is because it has almost no influence on the translating process. A string with an fixed typo does not have to be retranslated.
Le 2012-10-14 10:04, Dieter Adriaenssens a écrit :
Hi,
I don't find any clear rules on when to add/update translatable strings (from the developer point of view). I have a suggestions :
master (dev) :
- freely add and change translatable strings
when preparing a future stable (4.0-alpha/rc)
- no new translatable strings
- no updates that changes the content/meaning of a translatable string
(but exceptions allowed after discussion on mailing list)
- updates fixing typos and grammar are allowed
current stable (QA_3_5)
- no new translatable strings
- no updates that changes the content/meaning of a translatable string
- updates fixing typos and grammar are allowed
old releases
- no maintance on translatable strings (no new strings, no fixes on
existing strings)
What do you think? BTW : the reason I mentioned allowing grammar/typo fixes in current stable, is because it has almost no influence on the translating process. A string with an fixed typo does not have to be retranslated.
Fine by me.
Hi
Dne Sun, 14 Oct 2012 16:04:45 +0200 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
I don't find any clear rules on when to add/update translatable strings (from the developer point of view). I have a suggestions :
These are basically okay, maybe this should be put into wiki?
master (dev) :
- freely add and change translatable strings
when preparing a future stable (4.0-alpha/rc)
- no new translatable strings
- no updates that changes the content/meaning of a translatable string
(but exceptions allowed after discussion on mailing list)
- updates fixing typos and grammar are allowed
current stable (QA_3_5)
- no new translatable strings
- no updates that changes the content/meaning of a translatable string
- updates fixing typos and grammar are allowed
old releases
- no maintance on translatable strings (no new strings, no fixes on
existing strings)
What do you think? BTW : the reason I mentioned allowing grammar/typo fixes in current stable, is because it has almost no influence on the translating process. A string with an fixed typo does not have to be retranslated.
These are okay as long as you change source string in all po files, otherwise the strings will appear as fuzzy and will require attention from translators.
2012/10/16 Michal Čihař michal@cihar.com:
Hi
Dne Sun, 14 Oct 2012 16:04:45 +0200 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
I don't find any clear rules on when to add/update translatable strings (from the developer point of view). I have a suggestions :
These are basically okay, maybe this should be put into wiki?
That's the idea, but I wanted to check with the other developers first. I'll put it on later today.
master (dev) :
- freely add and change translatable strings
when preparing a future stable (4.0-alpha/rc)
- no new translatable strings
- no updates that changes the content/meaning of a translatable string
(but exceptions allowed after discussion on mailing list)
- updates fixing typos and grammar are allowed
current stable (QA_3_5)
- no new translatable strings
- no updates that changes the content/meaning of a translatable string
- updates fixing typos and grammar are allowed
old releases
- no maintance on translatable strings (no new strings, no fixes on
existing strings)
What do you think? BTW : the reason I mentioned allowing grammar/typo fixes in current stable, is because it has almost no influence on the translating process. A string with an fixed typo does not have to be retranslated.
These are okay as long as you change source string in all po files, otherwise the strings will appear as fuzzy and will require attention from translators.
What do you mean by 'all po files'? Is running po-update sufficient? Or do you mean it has to be changed in every branch were the string exists?
Hi
Dne Tue, 16 Oct 2012 13:18:21 +0200 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
2012/10/16 Michal Čihař michal@cihar.com:
These are okay as long as you change source string in all po files, otherwise the strings will appear as fuzzy and will require attention from translators.
What do you mean by 'all po files'? Is running po-update sufficient? Or do you mean it has to be changed in every branch were the string exists?
The update-po script just takes strings and updates po file to match them. In case some source string has been changed, translation will be marked as fuzzy. It simply can not detect whether change is important for translation or not.
In case you're sure this is just a typo, that is not affecting translations, you should change the source string manually [*] in po files prior to running update-po.
[*]: Or rather by some something like:
sed -i 's/this is typo/this is a typo/' po/*.po
2012/10/16 Michal Čihař michal@cihar.com:
Hi
Dne Tue, 16 Oct 2012 13:18:21 +0200 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
2012/10/16 Michal Čihař michal@cihar.com:
These are okay as long as you change source string in all po files, otherwise the strings will appear as fuzzy and will require attention from translators.
What do you mean by 'all po files'? Is running po-update sufficient? Or do you mean it has to be changed in every branch were the string exists?
The update-po script just takes strings and updates po file to match them. In case some source string has been changed, translation will be marked as fuzzy. It simply can not detect whether change is important for translation or not.
In case you're sure this is just a typo, that is not affecting translations, you should change the source string manually [*] in po files prior to running update-po.
[*]: Or rather by some something like:
sed -i 's/this is typo/this is a typo/' po/*.po
Added it to the wiki [0], along with the guidelines on when to add/update messages.
[0] http://wiki.phpmyadmin.net/pma/Gettext_for_developers
Kind regards,
Dieter
-- Michal Čihař | http://cihar.com | http://blog.cihar.com
Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Tue, 16 Oct 2012 14:17:28 +0200 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
Added it to the wiki [0], along with the guidelines on when to add/update messages.
Thanks, I've also added explicit section about fixing typos.
-
Dieter Adriaenssens -
Marc Delisle -
Michal Čihař