...at all. Confirmed by me and probably by kkafer by PM (via Gabor :-).

It seems, that generated tarball doesn't contain correct strings, so NOTHING is translated at all...

Filenames are OK (beside #203207 which is a duplicate of #193097)

CommentFileSizeAuthor
#13 empty-file.patch2.42 KBgábor hojtsy
#12 l10n_0_bytes_file.patch1.34 KBmeba
#5 drupal-cs-translations(2).tgz0 bytesmeba

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Hm, that was a Drupal core bug with *importing* not working, right?

meba’s picture

meba commented

I don't think so! I tried importing old package and worked. Most of the exported translations are EMPTY

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

I double checked with kkaefer, and he says that the bug he noted is not consistently reproducable with core. Also, l10n_server was not involved there.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Is this still valid?

meba’s picture

meba commented
StatusFileSize
new drupal-cs-translations(2).tgz0 bytes

I am still unable to use exported translations for D6 RC2. I did a CVS update of l10n_server, run update.php, cleared all needed tables and rescanned (as requested in other bugreport). Attaching exported translations...

meba’s picture

meba commented

Reattaching as it seems that the last one didn't go through.

Download it here please:

http://www.drupal.cz/translations.tar.gz

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Postponed (maintainer needs more info)

meba: the file you pointed out is also 0 bytes. Maybe you can explain what's wrong as well, so I can even reply without seeing the exact file. If your issue is this one, then please mark this one a duplicate and continue on there: http://drupal.org/node/212594

meba’s picture

meba commented

Well, the export doesn't work at all now...therefore 0 bytes (And I have the translation complete! :-(

Any suggestions how to debug?

meba’s picture

meba commented

Seems that my module was not properly upgraded. Had to disable and enable the module. Trying now...

meba’s picture

meba commented
Status: Postponed (maintainer needs more info) » Fixed

Voila! :-) Works now...

Two notes:
1) 0 bytes file is when there are NO strings to export. I think that in that case we should return a message, not empty file.
2) Exported translations have unix timestamp "0" and are not globally readable. Will create additional issue for this

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Title: Exporting translations doesn't work » 0 byte file exported when no strings are available
Priority: Critical » Normal
Status: Fixed » Active

Repurposing the bug for what caused it.

meba’s picture

meba commented
Status: Active » Needs review
StatusFileSize
new l10n_0_bytes_file.patch1.34 KB

Let's roll...

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Needs review » Fixed
StatusFileSize
new empty-file.patch2.42 KB

To avoid upgrade problems, when Drupal 6 comes, I moved the check later, so that the generated data array is checked, not db_num_rows(), which is removed in D6. Also, I added project and release information to the message, and also recorded as a watcdog() for possible (later) automated packaging. Thanks for the analysis and the fix! Committed this patch.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.