[translations] From localization server to translation project?

[Gábor Hojtsy]

Yes, msgfmt requires you have the same whitespace formatting in source
and translation (at the beginning and end of strings). That's some
awkward rule, but that's how it is. l10n_server should programatically
ensure that the white space on source and translation are the same,
but it does not do that yet (http://drupal.org/node/209980) So you
need to go in and fix these translations on the server interface. (Or
submit a cool patch for the issue, including an update function which
fixes these kinds of errors automatically in old translations as well
:P)

Gabor

On Sun, Feb 24, 2008 at 12:50 PM, Jose A. Reyero <drupal at reyero.net> wrote:
> Hey Gabor,
>
>  I've done that export, committed the files and got this error on the
>  release page, see http://drupal.org/node/225715
>
>
>       Packaging error messages
>
>     * ERROR: /msgfmt --statistics es/installer.po 2>> es/STATUS.es.txt/
>       failed with status 1
>
>       es/installer.po:357: `msgid' and `msgstr' entries do not both end with '\n'
>       msgfmt: found 1 fatal error
>       2140 translated messages, 894 untranslated messages.
>
>     * ERROR: Unable to generate statistics for /installer.po/ in /es/
>       translation in version /6.x-1.x-dev/, not packaging
>
>
>
>
>  Gábor Hojtsy wrote:
>  > On Sat, Feb 23, 2008 at 1:48 AM, Jose A. Reyero <drupal at reyero.net> wrote:
>  >
>  >>  We are using the localization server for the Spanish translation, so I
>  >>  get from there the .tar.gz containing all the translation files for
>  >>  Drupal 6 core.
>  >>
>  >>  My problem is that I need to get from that the modules-module.po,
>  >>  themes-theme.po files etc to commit to the CVS so they get packaged as
>  >>  the big tar.gz file for download...
>  >>
>  >>  This may sound funny as what I need is to move my files to a different
>  >>  format for the packager to produce the same file format at the end, but
>  >>  I cant find an easy way to do it. Is there a script somewhere or am I
>  >>  missing anything?
>  >>
>  >
>  > There is an "Export for CVS commit" export format in l10n_server. If
>  > there is no such option, just update to the latest one, I just
>  > released Alpha 3 which includes other bug fixes as well. That should
>  > generate the exact files as needed for CVS commits.
>  >
>
>  > Hopefully later we would not need CVS at all, but a cronjob will
>  > generate packages out of the drupal.org central l10n_server database.
>  > That's the plan:)
>  >
>  > Gabor
>
>
> > _______________________________________________
>  > translations mailing list
>  > translations at drupal.org
>  > http://lists.drupal.org/mailman/listinfo/translations
>  >
>  >
>
>  _______________________________________________
>  translations mailing list
>  translations at drupal.org
>  http://lists.drupal.org/mailman/listinfo/translations
>