multilingual

We've just released the first (working) version of the Translation Management module.

The purpose of this module is to create a systematic process for translating large Drupal sites.

Highlights

• Dedicated Translator Role - translators have language pairs and can translate only in them.
• One Translation Dashboard page - shows everything that needs translation including nodes, blocks, CCK, strings and what-have-you.
• Translation Jobs Queue for translators - each translator sees the jobs waiting for him/her.
• Unified Translation Editor - no matter what you're translating, you're always doing it from the same page.

Who is Translating?

Right now, translators can be Drupal users. You can give Translator privileges to existing users or create new users for translators.

In the very near future, we're also working on an API for interfacing to translation services. This API would be open and any translation service is invited to create a connector for itself.

The Module Itself

The module is now released and working. You can get it from:
http://drupal.org/project/translation_management

There's no official guide yet, but this blog post should be a good place to start:
http://drupal-translation.com/content/translation-management-alive

This kind of thing is an enabling feature for using Drupal on enterprise Drupal sites. Managing translation work can be a huge task and we hope that this helps.

Feedback? Ideas? Comments?

We just released the first alpha version of Apache Solr Multilingual which supports language specific stemming, synonyms and compound word splitting. There's still a lot to do but any feedback at this early stage of the project will be helpful.

Hello,

I am currently setting up a multi-country / multi-language site, using one database and one code base. The reason for this is that 90 percent of the content will be shared. I will use 5 different domains for all the countries, using the domain access module package. All domains should have a different default language.

I am trying to run apachesolr on a site which for now has only French content.

I have attached both the schema.xml I use and the query results from solr for a query on the word "Vidéocassettes".

From what I have gathered so far, I assumed that the following filter

charFilter class="solr.MappingCharFilterFactory" mapping="mapping-ISOLatin1Accent.txt"

I have had a lot of research about optimizing Apachesolr for non-english languages, especially for German. It comes out, that there search results can be dramatically improved by adjusting Solr's stemming and by breaking up compound words. This can be easily achieved with slight changes to Apachesolr's schema.xml.

This post is about configuring stemming:
http://www.early-dance.de/news/9188-optimizing-apachesolr-non-english-la...

And this post is about compound word splitting, that is needed in languages like German that have long combined words like "Dampfschifffahrt":
http://www.early-dance.de/news/9189-apachesolr-issues-german-and-other-g...

Hi all,

Mình dùng CCK tạo ra 1 kiểu Content Type là Product, trong Product có thêm 2 Field là:

1. Color: Select list gồm các giá trị
   1|Vàng
   2|Đỏ

2. Warranty: text filed bình thường

Sau khi tạo mình có thể dùng I18N dịch được các string như Color, Warranty, nhưng các value của các field thì không thể dịch được, ví dụ: Vàng, Đỏ. Hoặc khi nhập text cho Warranty xong, click translate thì nó chỉ hiểu được 1 value mà thôi.

Hi,

I am planning a multisite project where I want to be able to share users and some content between sites.

All sites will be more or less clones of each other, but they will have different target markets (countries mainly).

What I want to do is:

<

ul>

Found this review of Location module:

http://civicactions.com/blog/Location_Package_Drupal_6

<

blockquote>

Hi,

I'm not sure if I'm posting this in the correct section, but I posed a similar question on the main drupal forum and received no replies on the subject, so i'm hoping someone can assist me here if possible.

What options does one has when trying to set up an internationalized or multilingual user profile at multilingual site. When useing the core profile option the i18n module provides the posibility to translate the names of the profile fields, which might be enough for some profiles, but if you want a profile where user writes an introduction of him self, you are in trouble. Exposing the user entered text for translation trough t() function is not a good option.