Internationalization

There are a couple of module that help translate content (eg http://drupal.org/project/translation_overview and http://drupal.org/project/translation_table) but they are either based on i18n or specifically nodes. We're currently making a webshop and for this we're going to use only field translation for the first time and we also need a translation overview.

So before I start a field_translation_overview module I wanted to ask if there are any such efforts already going on?

Drupal.org is great to maintain a solid number of issues but all of us trying to wrangle a huge number of issues need way better tools to have overviews of what is going on and how is work structured. We need to be able to help new people join in quick, let them have an overview of current tasks and also on the place of tasks in a bigger picture. So we need to have the bigger picture documented with the possibility for people to dive in on demand and we need to keep it always up to date and relevant.

The Drupal.org issue queue is great to see a status of issues, but it is not good at all in maintaining relations and especially bad at providing support for hierarchy and in-context structural information. All we get is basically a list of issues like this one: http://drupal.org/project/issues/search/drupal?issue_tags=D8MI

Hi,

Talking with one person in IRC We found a strange behavior in configure prefix language (In drupal 8). For example: you have two language (english and french) and active url detection. You configure a prefix for english => en and french => fr. If you access with language english and access to admin/config/regional/language/configure/url. ¿Is normal that reappears the prefix?.
I think it would be interesting locale automatically remove the prefix in the description if we go with some language. What do you think?

I attached a image for more explanation.

While we made some progress last year for better multilingual support in Drupal 8, the lion's share of the work is still ahead of us. Make no mistake, most planned multilingual features are still vaporware. There is a lot to do to improve what is in there and to add the missing functionality. Never did I see a shortage of tasks to do, much more so lack of people with dedicated time available to focus on the tasks. Therefore it looked only logical to put together a well planned series of in-person sprints with a well planned structure to gather like-minded people who want to make Drupal 8 a much better multilingual release, getting them out of their daily habits to entirely focus on Drupal 8.

Therefore I propose the following threefour in-person sprints for the foreseeable part of this year to gather and improve our codebase. I'd love if more people can come to these sprints, so I purposefully propose them for around the biggest Drupal events of the year. Also, I'm announcing these plans so that we can organize ahead of time for travel, accommodation and sprinting space for each attendee and last but not least sponsors.

I'm currently writing a D7 i18n book for Packt (hopefully out in March). I've written the chapters on the regular stuff: interface translation, node translation, field translation, blocks, views, menus, taxonomy, users, comments. I'm now working on the final chapter that has advanced or less common topics. So far, I have:

• Panels
• SEO
• Theming
• Ecommerce (via Commerce module)

If there is a topic that you'd like covered, please leave a comment. I can't promise it will be included (page count is very short), but, if it's something of general interest, I will try!

It is hard to believe but in a few days it is going to be eight months, since the Drupal 8 Multilingual Initiative (D8MI) was announced. So it is at least as good a time as ever to take a look back and take stock of where we are and where we need to accelerate work to get to results. On one hand, the D8MI is very lucky for being able to do work on many fronts at once and make small incremental changes instead of turning Drupal upside down (making the changes easier to accept). On the other hand, sometimes the changes themselves don't make a big impact and only form a bigger picture when considered all at once and more importantly depend on some bigger changes being done in the entity system or the configuration system, which are big dependencies.

WARNING: In Dries Buytaert's latest published words, Drupal 8 is about to be released in 17 to 23 months from now. (The interview is dated mid-last month and cites 1.5/2 years). All the new stuff detailed here is to be released in a stable Drupal version at that time with a huge number of other improvements. Drupal 8 is not in any way near release.

A three-legged approach

Instead of turning multilingual concepts upside down, D8MI attempts to make the classic three legged multilingual approach in Drupal work much better and more unified, taking best practices from each area. The three legs are interface translation, content language/translation and configuration language/translation. The differences for these come from deep Drupal implementation differences.

1. The built-in software interface is written in English, can be pre-translated by the community and distributed to Drupal installs. The community translation itself is out of the scope of Drupal core, so we need to improve support for the distribution/access to translations itself.

2. The content translation system uses entities and fields, which are great because it encapsulates data storage with the widgets and formats/validation of the data. This is really good for language support / translation, so we are planning to expand this pattern to all entity types and get the user interface for translation in core.

3. For configuration (everything that is not entities or the built-in user interface), Drupal 8 is slated to include a configuration management backend, that is in the works and not yet well defined on the user interface level. This continues to be both the biggest feature gap and biggest unknown for the D8MI.

Hi Guys,

I am working on a bilingual drupal site and the using Drupal 7 version for the same. How can I use different images for headings and other portions of site for each of the language?

Thanks!

A comment by @catch caught my attention three days ago:

Is there any way to automate testing for missing RTL css?

So I thought of a solution, similar in goal to localization project (localize.drupal.org) by Gabor. Talked with Gabor about it a little bit, and agreed to write it here to discuss further.