It has happened quite a few times to me that after committing new po files, the next morning only to find it fails drupal.org packaging script. The error could simply be a typo in header, or mismatching line breaks. PoEdit doesn't seem to be able to catch the latter. The fact I had to file a support request to have release node removed before I could cvs untag it, makes it more frustrating.
So I am wondering if the drupal.org packaging script available for download, or is there a similar checker script I can run before committing to CVS?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Li schrieb:
It has happened quite a few times to me that after committing new po files, the next morning only to find it fails drupal.org packaging script. The error could simply be a typo in header, or mismatching line breaks. PoEdit doesn't seem to be able to catch the latter. The fact I had to file a support request to have release node removed before I could cvs untag it, makes it more frustrating.
So I am wondering if the drupal.org packaging script available for download, or is there a similar checker script I can run before committing to CVS?
The script is part of project.module:
modules/project/release/package-release-nodes.php
Cheers, Gerhard
translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Hi,
you can also run the following command if you're on Linux/Mac OS X/ Cygwin:
for i in *.po; do echo -n "$i: " ; msgfmt --statistics $i ; done
That will display any errors with files as well as statistics for all po files in the current directory.
Konstantin
On 07.05.2008, at 22:57, Jim Li wrote:
It has happened quite a few times to me that after committing new po files, the next morning only to find it fails drupal.org packaging script. The error could simply be a typo in header, or mismatching line breaks. PoEdit doesn't seem to be able to catch the latter. The fact I had to file a support request to have release node removed before I could cvs untag it, makes it more frustrating.
So I am wondering if the drupal.org packaging script available for download, or is there a similar checker script I can run before committing to CVS? _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
Thanks! I was just reading the package_release_contrib_d6_translation() function and starting to realize msgfmt is what I need.
On Wed, May 7, 2008 at 6:19 PM, Konstantin Käfer kkaefer@gmail.com wrote:
Hi,
you can also run the following command if you're on Linux/Mac OS X/ Cygwin:
for i in *.po; do echo -n "$i: " ; msgfmt --statistics $i ; done
That will display any errors with files as well as statistics for all po files in the current directory.
Konstantin
On 07.05.2008, at 22:57, Jim Li wrote:
It has happened quite a few times to me that after committing new po files, the next morning only to find it fails drupal.org packaging script. The error could simply be a typo in header, or mismatching line breaks. PoEdit doesn't seem to be able to catch the latter. The fact I had to file a support request to have release node removed before I could cvs untag it, makes it more frustrating.
So I am wondering if the drupal.org packaging script available for download, or is there a similar checker script I can run before committing to CVS? _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-
Gerhard Killesreiter -
Jim Li -
Konstantin Käfer