locale

I want to change the "Language negotiation" setting (admin/settings/language/configure) from "Path prefix with language fallback" to "Domain name only" on production site that have thousands of translated nodes.

On a first look it seems that I need some Apache redirects for SEO reasons. For example, for the Italian pages it may need

I didn't find any related guidelines. What are the side effects? Are there some "best practices"?

Thank you!
Claudiu

Hi all,

Now we have http://drupall10n.com with us, and we plan we make this as central point for atleast indian languages so i would like to take a feedback should we go for

http://langcode.drupall10n.com

or

http://drupall10n.com should have all indian languages as once independent site

comments please

This would be available for free to all localizers :)

We already have Hindi and Marathi on this functional

http://drupall10n.com

Many out of regional Websites use their own language, different from English, and they don’t need the opportunity to use several language versions of the website. I suggest importing the translation directly into the files of the source code, processing on the functions t() and inserting instead of English expressions, expressions of the required language.

While currently the majority of Drupal people speak English as a native or second language, I think it would artificially limit the scope of the LUGO group to require it. I deliberately did not choose a language when I created this group because there was not an 'all' option. The audience and membership of this group is intended to be anyone, anywhere, who organizes a local Drupal User Group currently, or wants to start one. If we are going to encourage that second group to become part of the first, we will need to accommodate people that do not speak English at all.

Is there any way to translate one single string without having to load the entire locale module? It seems a waste just for one string. Thanks.

I've posted some documentation on multilingual module development for Drupal 6 http://drupal.org/node/303984. The idea is to pull together what module developers would need to add multilingual support to their module.

Please review and improve!

I was under the impression that when selecting a language, from the language selection block (in drupal6), the content is also filtered to display only the nodes in the selected language

This behaviour is also confirmed by this handbook page http://drupal.org/handbook/modules/translation

(maybe this is not really for drupal 6.x as it states ??)

Hi!

In D5, we introduced Autolocale module, enabling users to import translations after enabling module / during installation. However, this had few caveats, as timeouts on cheap shared hosts, etc.

In D6, Autolocale is built-in core, using batch API and just works very well.

What do you think next step should be? From my point of view:

"Let Drupal automatically fetch translations from a server".

One of my three proposed subprojects for this year's Google Summer of Code was about improvements for Drupal 6 to include the autolocale functionality developed for Drupal 5. As always, putting autolocale module into core is not simply a code copy-paste issue, there are several outstanding issues that need to be worked out. The main problem is that when we need to parse and import a half of a megabyte in translation files, PHP can easily time out. So a batch processing framework was in need to process multiple operations in subsequent HTTP requests. Fortunately yched already did a big amount of groundwork on this, and Jakub Suchy tried to map the batch API to autolocale, so I only needed to dig deeper into these to try to make them work nicely together.