Internationalization

String translation. This works differently to Drupal standard localization system: The strings will be translated from the default language (which may not be English), so changing the default language may cause all these translations to be broken.

I'm encountering an issue with URL's to nodes in a different language than the user's current language. Currently, the site is set up with English as the default language, and French in a path prefix of /fr. On the home page, there is a view of all book nodes, some in French and some in English. However, if your current language is English, the French bookURL's are set to fr/node/. If you switch to French, all English books are shown as node/.

I've found out that if I insert the appropriate paths into the url_alias table I can make things work as expected. For example:

Say we have some sites: uk.example.com, us.example.com and fr.example.com. the last one uses our French pages, the first two use our "English" pages. Is there an easy way to handle the minor but noticeable differences between American English and British English. It seems a pain to create separate nodes for all pages (or even one page) just because of the words "colo(u)r" and "meters"/"metres".

What's the best options(s) to structure our multi-country site. The site probably wants to be managed off one installation, but it will be (in terms of thinking about it) country-based not language-based so for example:

www.example.com/ca/fr/widget/price would be in French with the price in CAN dollars
www.example.com/fr/fr/widget/price would be in French with the price in Euros
www.example.com/us/en/widget/price would be in English with the price in US dollars
www.example.com/gb/en/widget/price would be in English with the price in pounds etc

I'm a little confused about something. I have a view called events (http://www.wimaxforum.org/wimaxevents) and I want to have that same page but with a Japanese Primary Link at the top. My boss and I decided to keep the menu items within events in English and then add a new menu item in Japanese for Japan specific events or any events our Japanese office decides to translate.

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).

New Translations Released this release contains 250+ new translations

Hindi Translations @ http://drupal.org/project/hindi

Contribute to Hindi Translations @ http://drupalhindi.com or http://drupall10n.com

We request you to contribute to The Translations so that we can have a new release as soon as possible

Current Status

Built-in-Interface = 10.65 % Complete
Google Groups Module = 100% Complete

We are adding Japanese to our website with English as our default language. We want to style our Japanese front page with different graphics that have the text in the graphics in Japanese. So right now, I guess our set up is showing the Japanese front page as http://www.mysite.com/ja . My question is how would be template out a new page for the japanese home page? Can we have a template called front-page-japanese.tpl.php? OR, can you not have different page templates for different languages?

Even though English in not a problem for me, I understand the importance and need to offer a website in other languages, so I really like that the new design have that in mind. Particularly as it also means that the internationalisation support for Drupal is moving up a few notches in priority.

Before I go into the main topic of this post, a little note about the placement of the language select. In the mockup (iteration 11), the select language listbox is placed at the bottom. I think it should actually be placed in the header instead as that will make it much easier to find. Especially those, who's English is not very good tend to leave if they don't find a language quickly without having to scroll to the bottom of a very long page. They could also be shown as flags.

Oki, back to topic. I have one site I am using the Internationalization modules in and it works just fine. The only real issue though is that browsing modules and other add-on stuff and finding information on what languages they are available in is not very easy. In most cases I have to actually download the module and check if it supports translations and if so if it is available in the language(s) I need.

So it got me thinking a bit about how this can be improved on drupal.org and I came up with the following. I will use modules as example, but I believe similar features can be applied on other areas as well, such as themes.