Hi,
while I agree that the directions in the readme file ultimately say that you should not create filename.xx.po files, they are still somewhat confusing. I was a bit unsure about what to do in the first place as well. Maybe we should add a sentence like "The translation files in the repository have to be named "general.po", "themes- garland.po" etc. They will be automatically renamed upon packaging the translation."
The xx translation is indeed a translation created to test the Drupal UI for untranslatable strings. I used this technique for both the D5 and D6 release to find bugs in the translation. (http://groups.drupal.org/node/7843 is the post for D6 issues).
Konstantin Käfer -- http://kkaefer.com/
On 11.01.2008, at 01:14, Gábor Hojtsy wrote:
On Jan 10, 2008 10:47 PM, Drupal Norge drupalnorge@gmail.com wrote:
I think we're the only ones who followed what's written in the readme.txt:
Drupal 6 comes with automated translation file import, so the translation source strings are organized by location. For the translations to be imported automatically, translated templates should be renamed for the translations such as (for example in Italian):
- general.pot to general.it.po
- themes-garland.pot to themes-garland.it.po....
that instruction is very clear, but unfortunately wrong.
Well, you did not follow the second part about directory names, so seems like you had second thoughts as well.
So Gabor, just to be 100% sure, the language code is NOT a part of the filename? If so, please edit the readme.txt file from the Translation Templates :-)
Drupal 6 RC2 is out (http://drupal.org/drupal-6.0-rc2) and new templates are out for that as well: http://drupal.org/node/208647 There is an updated README included in that package.
Gabor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations