Hi! Since you have a lot of translations already distributed with CCK, I thought you might be able to give me a clear answer on this:

I'm going to translate a lot of modules (Including CCK) to Danish. But I can't get Drupal to use the translations I make and upload for custom modules.

The way I've understood it is, that if I upload the da.po file to foomodule/translations dir, the module should install this translation automatically, when it is enabled, if the site is set to Danish as its default language.

But I just can't get Drupal to do this. It ignores my translations completely.

Can you give me a clue to what I'm doing wrong here?

It this because the translation files have to be there, when the module is enabled for the first time (Installed)? That wouldn't make much sense, because what then when the module and translation is updated?

Also, can you tell me whether I should compile a catalog file from each of your submodules individually, OR if I can just take one catalog from all CCK modules in one file, OR if I should do both?

Hope you can help, thanks!

Comments

Nubstah’s picture

Nubstah commented

I too would like to know this :)

markus_petrux’s picture

markus_petrux commented
Status: Active » Fixed

Drupal tells locale module to import translations only when the modules are first installed, not when modules are enabled.

Once a module has already been installed, you can import updated translation files from the translate interface.

Each module in the CCK package has its own translations subdirectory. You may want to look at how other languages have included their translations. For example, the text module has its own translation template (modules-text.pot) and individual languages use a file name like modules-text.XX.po where XX is the language code.

That being said, you may want to look at localize.drupal.org, and its FAQ. I hope some time soon all translations will be managed from there.

Status: Fixed » Closed (fixed)

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