internationalization

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

I'm new to Drupal, I am about to create a multi-language site, I had to go with D5.7 since D6 is not yet compatible with many modules that I want to use.
I've been researching drupal sites for a step-by-step guide , I found some information in drupal handbooks but I still have many questions:

• the locale module allows to translate core drupal modules and strings, does the i18n module allow to translate any newly installed modules ? or is it just about translating content (nodes) ?

Updated: June 20, 2007: RTL HTML Email now possible with my patch to the new htmlmail module.

Requirements for Drupal 6 core RTL email support - Request for comments

It has been 8 months since I've implemented a Drupal 4.7 user.module patch to support RTL emails (attached).

My next target is to ask for the RTL/i18n community help to update the code and migrate those proven changes into the Drupal 6 core. This will save tons of later headache.

Here are the basic requirements - I will need your feedback on the concept (implementation is quite straightforward).

I just started the Auto Translate project. This module, when complete, will add a button to the node translation tab that will fill in a textarea with a (very rough) translation from a third party automatic translator, such as Babelfish or Google. The module may also be configured to translate the content within a textarea.

This is an old issue, and I wish to get a clear up-to-date status of the situation in Drupal 6 (or 5). It may have been answered already, so a redirection would be as good as an answer :-)

1. RTL CSS files in core: In order to ease the RTLization of themes, and to set a nice example for themers and module developers, core modules should come with and RTL version of CSS. Such a set already exists, and is used in every hebrew Drupal site, and surely in other RTL languages sites as well.

Hi All,
I've posted the idea of a session on internationalization here on the OSCMS/DrupalCon CA 2007 site http://2007.oscms-summit.org/node/92

You can vote for the presentation and add comments to it over there.

cheers,
Ian

The point of this post is to do a round up for the community, get on the same page with some of the developers, and find a path toward what to do for Drupal 6 core and beyond, as well as with contributed modules.

"Relationship" I understood as relationships between fields (nodes are many relationships, which are subject of more advanced process).

Wanted features:

1. Powerful and without limitation thanks to the most abstract (see: "everything is a field", compare this to: Global CCK fields, A controversial(?) point: store translations as nodes).
2. Build-in categorization features.
3. Build-in views features (listing fields, not necessary nodes).
4. Build-in menu features.
5. Support for Semantic Web/Microformats/similar.

Observations about current situation:

I am a web architect and a system analyst. Now, I've translated Drupal To Hebrew and initiated the creation of a drupal community in Israel. Following Gábor Hojtsy's request, Here is a use-case analysis of my expernece from the Hebrew Translation of Drupal, and with it's implementation on tens of sites, with indexation for search engine relevancy.

Recently, I've tried the Internationalization module on two of my sites, but gave it up and decided to wait for a later time. Problem is that i18n is not yet compatible with many other modules. I am a heavy user of taxonomy / category modules. The i18n module is a big step forward, but more work is needed. I need language specific taxonomy with menu integration. On one site, I have tried to use the taxonomy module, but found that the vocabulary names are not translated (nither in the node entery screens nor in the menu). On the other site, I tried to use the new category module but discovered that the node input form (and the menu) displayed all categories without language distinction.