Hi Sayamindu,
The file includes an error. Could you check it?
$ msgfmt po/es/etoys.po po/es/etoys.po:14807: `msgid' and `msgstr' entries do not both begin with '\n' msgfmt: found 1 fatal error
#: System-Support,Utilities_class>>readServerUpdatesThrough:saveLocally:updateImage: msgid "" "\n" "Would you like to try the next server?\n" "(Normally, all servers are identical, but sometimes a\n" "server won't let us store new files, and gets out of date.)" msgstr "" "Le gustaria intentar el proximo servidor?(Normalmente, todos los servidores " "son identicos, pero algunas veces un servidor no nos dejara guardar nuevos " "archivos y se vuelve obsoleto."
Cheers, - Takashi
On Jan 28, 2008 8:15 AM, Cron Daemon root@crank.laptop.org wrote:
Updating 8fbb1d9..6adbe22 Fast forward po/es/etoys.po | 8427 ++++++++++++++++++++++++++++ +--------------------------- 1 files changed, 4302 insertions(+), 4125 deletions(-) commit 6adbe226e1e7cca7a1c5c326897e9de5a3254227 Author: Pootle Translation pootle@dev.laptop.org Date: Mon Jan 28 11:10:01 2008 -0500
Commit from Pootle by user sayamindu. 3054 of 3660 messagestranslated (37 fuzzy).
At revision 104.
Etoys-notify mailing list Etoys-notify@lists.laptop.org http://lists.laptop.org/listinfo/etoys-notify
Fixed. Thanks, Sayamindu
On Jan 28, 2008 11:27 PM, Takashi Yamamiya tak@metatoys.org wrote:
Hi Sayamindu,
The file includes an error. Could you check it?
$ msgfmt po/es/etoys.po po/es/etoys.po:14807: `msgid' and `msgstr' entries do not both begin with '\n' msgfmt: found 1 fatal error
#: System-Support,Utilities_class>>readServerUpdatesThrough:saveLocally:updateImage: msgid "" "\n" "Would you like to try the next server?\n" "(Normally, all servers are identical, but sometimes a\n" "server won't let us store new files, and gets out of date.)" msgstr "" "Le gustaria intentar el proximo servidor?(Normalmente, todos los servidores " "son identicos, pero algunas veces un servidor no nos dejara guardar nuevos " "archivos y se vuelve obsoleto."
Cheers,
- Takashi
On Jan 28, 2008 8:15 AM, Cron Daemon root@crank.laptop.org wrote:
Updating 8fbb1d9..6adbe22 Fast forward po/es/etoys.po | 8427 ++++++++++++++++++++++++++++ +--------------------------- 1 files changed, 4302 insertions(+), 4125 deletions(-) commit 6adbe226e1e7cca7a1c5c326897e9de5a3254227 Author: Pootle Translation pootle@dev.laptop.org Date: Mon Jan 28 11:10:01 2008 -0500
Commit from Pootle by user sayamindu. 3054 of 3660 messagestranslated (37 fuzzy).
At revision 104.
Etoys-notify mailing list Etoys-notify@lists.laptop.org http://lists.laptop.org/listinfo/etoys-notify
Hi Sayamindu,
Sorry, but still same error. One more "\n" is needed at front of the message. Can I fix it on git repository by my self? Because It is just 4 characters, it is much faster. What's happening on Pootle if I update git from outside?
Cheers, - Takashi
Sayamindu Dasgupta wrote:
Fixed. Thanks, Sayamindu
On Jan 28, 2008 11:27 PM, Takashi Yamamiya tak@metatoys.org wrote:
Hi Sayamindu,
The file includes an error. Could you check it?
$ msgfmt po/es/etoys.po po/es/etoys.po:14807: `msgid' and `msgstr' entries do not both begin with '\n' msgfmt: found 1 fatal error
#: System-Support,Utilities_class>>readServerUpdatesThrough:saveLocally:updateImage: msgid "" "\n" "Would you like to try the next server?\n" "(Normally, all servers are identical, but sometimes a\n" "server won't let us store new files, and gets out of date.)" msgstr "" "Le gustaria intentar el proximo servidor?(Normalmente, todos los servidores " "son identicos, pero algunas veces un servidor no nos dejara guardar nuevos " "archivos y se vuelve obsoleto."
Cheers,
- Takashi
On Jan 28, 2008 8:15 AM, Cron Daemon root@crank.laptop.org wrote:
Updating 8fbb1d9..6adbe22 Fast forward po/es/etoys.po | 8427 ++++++++++++++++++++++++++++ +--------------------------- 1 files changed, 4302 insertions(+), 4125 deletions(-) commit 6adbe226e1e7cca7a1c5c326897e9de5a3254227 Author: Pootle Translation pootle@dev.laptop.org Date: Mon Jan 28 11:10:01 2008 -0500
Commit from Pootle by user sayamindu. 3054 of 3660 messagestranslated (37 fuzzy).
At revision 104.
Etoys-notify mailing list Etoys-notify@lists.laptop.org http://lists.laptop.org/listinfo/etoys-notify
Hi,
On Jan 31, 2008 4:06 PM, Takashi Yamamiya tak@metatoys.org wrote:
Hi Sayamindu,
Sorry, but still same error. One more "\n" is needed at front of the message. Can I fix it on git repository by my self? Because It is just 4 characters, it is much faster.
I would suggest you to do, as maybe you need to resolve it right now to rebuild RPM.
What's happening on Pootle if I update git from outside?
On pushing to git conflict might occur between Pootle and git master but we could around.
Sayamindu, Can we validate it within built-in test of Pootle or can we add new test suite? And it would be great if we run testing periodically and publish test report at somewhere, then we could monitor how healthy translations are and check it before commit.
Cheers, /Korakurider
On Jan 31, 2008 11:16 PM, Korakurider korakurider@gmail.com wrote:
Hi,
On Jan 31, 2008 4:06 PM, Takashi Yamamiya tak@metatoys.org wrote:
Hi Sayamindu,
Sorry, but still same error. One more "\n" is needed at front of the message. Can I fix it on git repository by my self? Because It is just 4 characters, it is much faster.
Oops - sorry fixed that :-)
I would suggest you to do, as maybe you need to resolve it right now to rebuild RPM.
What's happening on Pootle if I update git from outside?
On pushing to git conflict might occur between Pootle and git master but we could around.
As Korakurider suggests - this will result in a conflict in Git. How Pootle handles that depends on the nature of the conflict. If you absolutely need to modify PO files from your side, please let me know after you do that - so that we can coordinate and fix the conflict. Thanks, Sayamindu
Sayamindu, Can we validate it within built-in test of Pootle or can we add new test suite? And it would be great if we run testing periodically and publish test report at somewhere, then we could monitor how healthy translations are and check it before commit.
Cheers, /Korakurider
Hi Sayamindu,
What's happening on Pootle if I update git from outside?
On pushing to git conflict might occur between Pootle and git master but we could around.
As Korakurider suggests - this will result in a conflict in Git. How Pootle handles that depends on the nature of the conflict. If you absolutely need to modify PO files from your side, please let me know after you do that - so that we can coordinate and fix the conflict.
Thanks, Could you update po/de/etoys.po in Pootle? Also there was a similar problem, and I fixed just one line.
Cheers, - Takashi
On Jan 31, 2008 11:16 PM, Korakurider korakurider@gmail.com wrote:
Hi,
On Jan 31, 2008 4:06 PM, Takashi Yamamiya tak@metatoys.org wrote:
Hi Sayamindu,
Sorry, but still same error. One more "\n" is needed at front of the message. Can I fix it on git repository by my self? Because It is just 4 characters, it is much faster.
I would suggest you to do, as maybe you need to resolve it right now to rebuild RPM.
What's happening on Pootle if I update git from outside?
On pushing to git conflict might occur between Pootle and git master but we could around.
Sayamindu, Can we validate it within built-in test of Pootle or can we add new test suite? And it would be great if we run testing periodically and publish test report at somewhere, then we could monitor how healthy translations are and check it before commit.
Cheers, /Korakurider
Regarding test suite - I have plans on adding pre commit hooks to Git which can detect if PO files are malformated, and stop the commit. However, I don't think this can be done immediately, and it is low priority for me atm. However, Pootle has a few tools which lets you check PO files - and I have been encouraging the translators to use them - see http://wiki.laptop.org/go/Localization/Testing#Testing_the_PO_files
Thanks, Sayamindu
Sayamindu,
On Feb 1, 2008 5:43 AM, Sayamindu Dasgupta sayamindu@gmail.com wrote:
On Jan 31, 2008 11:16 PM, Korakurider korakurider@gmail.com wrote:
Can we validate it within built-in test of Pootle or can we add new test suite? And it would be great if we run testing periodically and publish test report at somewhere, then we could monitor how healthy translations are and check it before commit.
<snip>
Regarding test suite - I have plans on adding pre commit hooks to Git which can detect if PO files are malformated, and stop the commit. However, I don't think this can be done immediately, and it is low priority for me atm.
Well, it would be great if commit transaction makes sure required tests pass. But I think just to compile PO with msgfmt periodically from cron job would helps us greatly.
However, Pootle has a few tools which lets you check PO files - and I have been encouraging the translators to use them - see http://wiki.laptop.org/go/Localization/Testing#Testing_the_PO_files
I reviewed currently existing tests, StartPunc/EndPunc and Newline seem close to our requirement to avoid this error. I will check it out.
And let me ask again: can we add new test for Pootle (by writing test class in Python for instance)?
/Korakurider
On Feb 1, 2008 11:44 AM, Korakurider korakurider@gmail.com wrote:
Sayamindu,
On Feb 1, 2008 5:43 AM, Sayamindu Dasgupta sayamindu@gmail.com wrote:
On Jan 31, 2008 11:16 PM, Korakurider korakurider@gmail.com wrote:
Can we validate it within built-in test of Pootle or can we add new test suite? And it would be great if we run testing periodically and publish test report at somewhere, then we could monitor how healthy translations are and check it before commit.
<snip>
Regarding test suite - I have plans on adding pre commit hooks to Git which can detect if PO files are malformated, and stop the commit. However, I don't think this can be done immediately, and it is low priority for me atm.
Well, it would be great if commit transaction makes sure requiredtests pass. But I think just to compile PO with msgfmt periodically from cron job would helps us greatly.
Yeah - I'm trying to come up with a script which does that. It would walk the entire translations directory, running msgfmt --check for all .po files.
However, Pootle has a few tools which lets you check PO files - and I have been encouraging the translators to use them - see http://wiki.laptop.org/go/Localization/Testing#Testing_the_PO_files
I reviewed currently existing tests, StartPunc/EndPunc and Newline seem close to our requirement to avoid this error. I will check it out. And let me ask again: can we add new test for Pootle (by writingtest class in Python for instance)?
Yes - you can. Take a look at the translate toolkit - which is used by Pootle.
Btw - could you guys check if http://dev.laptop.org/~sayamindu/etoys.po is OK. This is a new translation which might be useful for you. It is in Pootle, and I can commit it if you want.
Thanks, Sayamindu
etoys-dev@lists.squeakfoundation.org
-
Korakurider -
Sayamindu Dasgupta -
Takashi Yamamiya