Posted by frank ralf on April 28, 2009 at 9:10am
Hi,
We have a discussion going on at http://drupal.org/node/446360 on whether it is required/better/advisable... to have separate translations folders for each sub-module of a module (each with their own pot/po files).
My opinion is:
- For smaller modules with few translatable strings this is overkill.
- It also makes it harder to maintain a consistent translation across all sub-modules.
- Importing all the translations for one module becomes more difficult.
- Splitting up translations between sub-modules might be wise for really heavy weight modules like CCK, Views and the like. (For a discussion on the general problem of - too many - sub-modules see http://drupal.org/node/437536.)
What do others think?
Cheers,
Frank
Comments
Need help
I built my site on drupal 6.14, 6 months ago. It was set up as general language.
I tried to make it to a multilanguage site and uploaded the required modules such as i18n.
I succeeded to make it work and realized that the site default was english. However I wanted to change the site default to Japanese and then add English version.
I checked on google and everywhere I could but did not find any relevant infos.
I decided to install the Japanese version drupal 6.16 on my former drupal 6.14, thinking that it would works in some way.
Unfortunately, not only it didn't work at all but now, I cannot even access to the admin page.
when I try to access to my site , of course it comes an error.
Can somebody advice me on what to do?
I am newby and have absolutely no knowledge of programming. But I am willing to learn.
Any help is welcome.
my site: http://www.ebiz-con.com
Thanks in advance to all.
Nathalie
Working with languages
Hi Nathalie,
Please see Working with languages for further information, especially Internationalization: Build Multilingual Sites. This thread is the wrong place for your inquiry.
hth
Frank
Frank
My LinkedIn profile