i18n

i am using simpletest with a multilingual drupal 6 site. whenever simpletest executes a link, by using clickLink or drupalLogin for example, the url gets corrupted.

this is because the language code always appears twice in the url. for example: http://example.com/de/de/node.

i was wondering if someone else ran into this issue when testing a multilingual site with simpletest? do you know of any workarrounds / fixes to this issue? (http://drupal.org/node/944066)

thanks a lot,
josef

There are a number of places where for accessibility in D7 we still need to add strings to fields in core. There are still quite a few missing labels for fields in and this is very important so that individuals using screen readers have an opportunity to understand what the field represents. We want to do this however in a way which doesn't loading a tonne more work on translators.

selamlar,

http://www.fematek.com adresinde kurmuş olduğum drupal 6.19 çekirdek ve Internationalization 6.x-1.7 kullanıyorum.

Diller/multilingual system sayfasında, "Mixed current language (if available) or default language (if not) and language neutral." seçili. pathauto kurulu durumda.

şimdi sorunum şu:

Hey all,

Dev seed did an interesting integration with DIA and Drupal.

http://developmentseed.org/blog/2007/oct/19/integrating-drupal-democracy...

We're facing a bit of a sticky problem and are looking for ideas around it. It started with SEO for multilingual sites, but is more general than that.

Some module (e.g., Nodewords), create texts in their own tables. These texts are displayed to visitors (page title, meta description and other), so they need to be translated.

We can use drupal_alter to filter these texts and translate them. The only problem is, how to organize the translations.

Does anyone have recent experience with webforms in a fully internationalised Drupal website?
I saw that the webform module does not fully support the i18n system but there have been patches that successfully address some issues (see: http://drupal.org/node/245424).

Do you think it's worth trying to make it work? or shall I go for a CCK-based solution? I won't be needing anything very complex, just a few beefed-up contact forms. Webforms work really well for that because of the email integration and csv export functionality.

Any opinions will be greatly appreciated!
Cheers,
George

Bygger en hemsida åt en kund där sidan kommer att vara översatt till ca 10 språk. Har installerat internationalization-modulen(i18n) och det fungerar bra.

Problemet jag har nu är att det kommer finnas 1 person i varje land som skall ha rätt att översätta sitt eget språk, men ej något annat språk.
Går detta att lösa med rättigheter eller måste man installera ytterliggare någon modul för att kunna fixa detta?

If you're not a native English speaker doing Drupal, then the i18n module is probably the only way. This is why it seems very strange to me that the performance admin page says that i18n might not work with aggressive caching.

I find it hard to believe that multilingual drupal sites scale worst or harder than sites with one language.

scale worst/hard = scale without advanced caching

Is there anyone with experience using the i18n with aggressive caching?

I have the following situation: a site that has a second language added. Everything gets traslated. Now, I see this. There is a view with a page display. As path it gets "new-programmes/%". There is a possibility to add terms as argument. I found a solution to translate the terms. But when I open the french site I ge t this http://mysite.com/fr/new-programmes/term. I want to have the "new-programmes" translated to "nouveaux-programmes". This will result in http://mysite.com/fr/nouveaux-programmes/translated-term

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?