D6 core translations are not yet ready to be released
D6 radically changes the way core translations are done, including how things are named, and where they're laid out. The packaging scripts on d.o have to be modified to take this into account, and Gabor and myself have already started discussing the required changes [1]. Until that's done (and we'll definitely let you know when it is), please do *NOT* attempt to tag an official release of your core translations for D6. It's not going to work anyway[2], and will just create more work for us and more hassle for you. Besides, RC2 is going to break a handful of strings, so you're going to have to re-do your existing translations a little bit, anyway... Thanks, -Derek (dww) [1] http://drupal.org/node/207401 [2] http://drupal.org/node/208454 p.s. cross posting from the devel list.
This message should have been out when the translation templates for D6 were published. There are some of us who are very eager in releasing translation files for development, and since we weren't informed that the packaging scripts aren't ready yet, we have already tagged and published a release (tried anyway) of the D6 core traslation files. Anyway, in addition to informing translators in the mailing list, I think that this important message should also be stated in the readme.txt of the D6 translation templates. Something like: "The packaging scripts are being modified to accomodate the new naming conventions as of time of writing. In the meantime, do not attempt to tag an official release of your core translations for D6. Please check http://drupal.org/node/207401 for the status of this issue." Personally speaking, I would have not tagged and tried to release our files if we were informed earlier about this issue. 8-) . Well...sorry for giving Derek and Gabor unnecessary and extra work. With best regards, John (johnnoc) http://drupalnorge.no Derek Wright wrote:
D6 radically changes the way core translations are done, including how things are named, and where they're laid out. The packaging scripts on d.o have to be modified to take this into account, and Gabor and myself have already started discussing the required changes [1].
Until that's done (and we'll definitely let you know when it is), please do *NOT* attempt to tag an official release of your core translations for D6. It's not going to work anyway[2], and will just create more work for us and more hassle for you. Besides, RC2 is going to break a handful of strings, so you're going to have to re-do your existing translations a little bit, anyway...
Thanks, -Derek (dww)
[1] http://drupal.org/node/207401 [2] http://drupal.org/node/208454
p.s. cross posting from the devel list.
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
On Jan 10, 2008 9:10 PM, Drupal Norge <drupalnorge@gmail.com> wrote:
This message should have been out when the translation templates for D6 were published. There are some of us who are very eager in releasing translation files for development, and since we weren't informed that the packaging scripts aren't ready yet, we have already tagged and published a release (tried anyway) of the D6 core traslation files.
Anyway, in addition to informing translators in the mailing list, I think that this important message should also be stated in the readme.txt of the D6 translation templates. Something like: "The packaging scripts are being modified to accomodate the new naming conventions as of time of writing. In the meantime, do not attempt to tag an official release of your core translations for D6. Please check http://drupal.org/node/207401 for the status of this issue."
Personally speaking, I would have not tagged and tried to release our files if we were informed earlier about this issue. 8-) . Well...sorry for giving Derek and Gabor unnecessary and extra work.
No problem. Your job is to make sure your translation file names strictly follow the template file names (eg. where it says root.pot you should have root.po, where it says modules-menu.pot you should have modules-menu.po). The file names are very important for the packaging script, as it figures out the placement from the file names. Sorry for not being clear about where packaging stands now. In http://drupal.org/node/202631 (which is linked to from the RC1 announcement's translators section) I included testing information for your local packaging, but did not mention that the central packaging is not in place. Thankfully it is not all complex, and we hope to fix it in the coming days (hopefully this week). I'll try to be more clear about this in the future. Gabor
2008/1/10, Gábor Hojtsy <gabor@hojtsy.hu>:
[...] Your job is to make sure your translation file names strictly follow the template file names (eg. where it says root.pot you should have root.po, where it says modules-menu.pot you should have modules-menu.po). [...]
Eh. I'm confused now... shouldn't root.pot become root.n[o|b|n].po? -- Frederik 'Freso' S. Olesen <http://freso.dk/>
On Jan 10, 2008 10:08 PM, Frederik 'Freso' S. Olesen <freso.dk@gmail.com> wrote:
2008/1/10, Gábor Hojtsy <gabor@hojtsy.hu>:
[...] Your job is to make sure your translation file names strictly follow the template file names (eg. where it says root.pot you should have root.po, where it says modules-menu.pot you should have modules-menu.po). [...]
Eh. I'm confused now... shouldn't root.pot become root.n[o|b|n].po?
Frederik: that part of the doc explains, where translation files will end up. You did not create all the subdirectories in your translation tree either, right? Anyway, I did a quick look on who understood what based on already tagged translations: - de uses .po - fa uses .po (still with the old D5 file names(?)) - fr uses .po - he uses .po - hu uses .po - nb uses .nb.po - vi uses .po (still with the old D5 file names(?)) - xx uses po (hah, this is a pseudo/testing translation, did not notice it before) Looks like only the NB team misunderstood this one. Note that I admit that the README.txt for the template is not entirely clear either. Will update that as well with the RC2 template rolling. Gabor
Hmmmm..... Gábor Hojtsy wrote:
On Jan 10, 2008 10:08 PM, Frederik 'Freso' S. Olesen <freso.dk@gmail.com> wrote:
2008/1/10, Gábor Hojtsy <gabor@hojtsy.hu>:
[...] Your job is to make sure your translation file names strictly follow the template file names (eg. where it says root.pot you should have root.po, where it says modules-menu.pot you should have modules-menu.po). [...]
Eh. I'm confused now... shouldn't root.pot become root.n[o|b|n].po?
Frederik: that part of the doc explains, where translation files will end up. You did not create all the subdirectories in your translation tree either, right? Anyway, I did a quick look on who understood what based on already tagged translations:
- de uses .po - fa uses .po (still with the old D5 file names(?)) - fr uses .po - he uses .po - hu uses .po - nb uses .nb.po - vi uses .po (still with the old D5 file names(?)) - xx uses po (hah, this is a pseudo/testing translation, did not notice it before)
Looks like only the NB team misunderstood this one. Note that I admit that the README.txt for the template is not entirely clear either. Will update that as well with the RC2 template rolling.
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. 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 :-) John (johnnoc) nb translation team http://drupalnorge.no
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
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
On Jan 12, 2008 10:02 PM, Konstantin Käfer <kkaefer@gmail.com> wrote:
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."
Is this comment still valid for the new README in the RC2 package? Gabor
Is this comment still valid for the new README in the RC2 package?
No, but I'd move the sentence you wrote *a lot* more to the top. You still have to read all the way through the bulk of text only to know that nothing has changed for translators. Konstantin
On Jan 13, 2008 5:16 PM, Konstantin Käfer <kkaefer@gmail.com> wrote:
Is this comment still valid for the new README in the RC2 package?
No, but I'd move the sentence you wrote *a lot* more to the top. You still have to read all the way through the bulk of text only to know that nothing has changed for translators.
OK, we have this near the top. Should I move this even more up? File naming: ------------- Just rename .pot files to .po files when translating, otherwise leave them where they are (see below for information on doing test packages) Gabor
participants (5)
-
Derek Wright -
Drupal Norge -
Frederik 'Freso' S. Olesen -
Gábor Hojtsy -
Konstantin Käfer