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