Internationalization

This group works on internationalization issues, like making it possible to translate menus, nodes and taxonomies in Drupal. This includes everything from process and workflows, to actual code issues or optimizations required. The Translations group is where to go if you are working on translating Drupal core or contrib modules.

Translation of field labels and taxonomy terms: interface or content?

Posted by rogerpfaff on November 16, 2011 at 7:53am

This is a problem I described in the entity translation issue queue too: http://drupal.org/node/1342132

Field labels and Taxonomy Terms are seen as interface by drupal and entity translation. That is ok if you create content but brings up errors in some constellation as I described in the issue above.

Support?

Posted by sfsilks63 on November 14, 2011 at 1:53pm

Hi I can not work out where you can get some help in this group, so I have posted in the hope it finds the right place!

I am presently building a site in Spanish, but the back end is in English and Spanish, all is going well so far and I am impressed with the internationalization, even though I am new to Drupal and do not understand to much but learning with trial and error.

Conversion of D6 site to D7 and from node translation to field translation

Posted by slucas on November 9, 2011 at 3:05pm

Hello,

I've developed a d6 site and trying to complete its internationalization
http://www.archiref.com/

It's a site where the content : images of architecture, projects, are mainly sync between both language (french and english).
Only pure text field could be relevant to node translation and I have got very little on each content type (1 or 2 / 20-20 fields)

The other fields are taxonomy in closed vocabulary (that I set as localizable)

Roadmap, client management, and how we could help

Posted by arianek on November 2, 2011 at 7:49pm

Hi all -

We have a project on the go at Affinity Bridge that has as the next phase of our plan to implement multilanguage so that we can bring a German client into the project (which is currently English-only). I've been working on scoping and estimates for this phase of work, and I'm finding the more I learn the less I know. ;)

Drupal 8 Multilingual Initiative meeting on Nov 2, 2011

Posted by gábor hojtsy on October 28, 2011 at 8:51am

Start:

2011-11-02 16:00 - 17:00 UTC

Event type:

Online meeting (eg. IRC meeting)

It is that time again! If you don't find you way through the maze of the Drupal 8 Multilingual Initiative issues, wondering where to contribute this is your place! If you are actively contributing and need some timely feedback, make sure to be there too. We'll review current issues and shorter term plans to focus on, but we'll probably also touch on longer term todo items (still confined to Drupal 8). The meeting is in the #drupal-i18n channel on IRC. See http://drupal.org/irc for more information.

(Note time above is marked with UTC - check in your own timezone).

D7 version of MultiLink is available

Posted by andy inman on October 10, 2011 at 11:40pm

MultiLink for D7 is available, with no reported issues so far.

Dynamic default language for translation

Posted by igalmal on September 30, 2011 at 4:07am

Hello,

I am new here and also new to Drupal. Need your advice.

We have multilingual a site. The default language is English and most of the languages will be translated from English. However, we have language like Ukrainian which make sense to translate from Russian, so not translated pages will still remain in Russian. Most of Ukrainians can read Russian better than English; That may be also true for some Arabic languages with French as a second language.

Let me know if you know how to do Dynamic default language for translation.
Thank you.

Taming the locale module monster in Drupal 8

Posted by gábor hojtsy on September 29, 2011 at 10:49am

Drupal's locale module is a monster! It does lots of things to enable language support, including the following:

Configure/maintain a list of languages supported on the site
Configure the selection method for these languages, provide language switcher UIs
Translate the Drupal software to the configured languages
Provide language assignment user interface to path module and node module
Provide translatable date formats
Import and export Gettext translation files for UI translation
Provide database space for configuration translation (UI implemented in contributed i18n.module)
Provide hooks for entity field translation (UI implemented in contributed entity_translation.module)

The principal goal of the multilingual initiative for Drupal 8 is to spread language support wider, so more and more modules will have language support built-in. The path module language UI already got moved to path module (see http://drupal.org/node/1236680), and node is on its way (see http://drupal.org/node/540294). Also, Drupal 8 does not support use of locale module for configuration translation anymore (see http://drupal.org/node/1188430).

However, locale module still does too much! Not all of its features belong to other existing modules, and to support various foreign language and multilanguage models, we need to break locale module down to smaller pieces to make sense for users. To figure this out, I've opened an issue at http://drupal.org/node/1293304 and included some fancy overview graphs for us to help focus the conversation and figure out which piece makes sense at which area of the Drupal codebase. Your feedback would be very welcome on the issue (comments turned off here)!

Read more

"All galleries" layout settings do not work after installing i18n

Posted by ivalls on September 28, 2011 at 9:55am

Hi,
My "All galleries" layout settings do not work after installing i18n.
I am kinda new to Drupal7 so it may be me, but any ideas?

Thanks
Jan

Wrap-up report from the Montreal Multilingual Drupal sprint

Posted by gábor hojtsy on September 26, 2011 at 2:24pm

We've just had a fantastic sprint with people interested in bringing multilingual support forward in Montreal for almost a week in the middle of September. People (in no particular order) from Evolving Web, Whisky Echo Bravo, Koumbit, OpenConcept, xMac Info, psegno.it, Acquia, etc. all participated in a week of code writing, UX reviews and planning, documentation and architecture discussions.

We marked most of the issues that we've been working on with the D8MI and Montreal tags, and lots of issues were tagged with Montreal in the Entity translation module queue.

While some of this work is still ongoing, all-in-all I think we made progress on lots of important pieces and helped kickstart important work on usability and key underlying API changes at the same time as improving the documentation. I'd like to especially thank the Drupal Association and Acquia for sponsoring the event which made it possible to fly in contributors from Europe too. We had a great gathering of people and matching tasks for everybody to be productive and contribute lots to the effort!

Language Selection Page for I18N in D6

Posted by pol on September 17, 2011 at 7:11am

Hi all,

I'm looking to get feedback on a module I made for Drupal 6.
It allows you to create a custom landing page if no language is found from url.

I know Drupal has mechanisms to automatically detect language, but one of my client absolutely need that Language Selection Page, so I made a configurable module so it can be helpful for other people too.

The module will save the language prefix in a cookie and use it if not found also.

You can configure the module through a setting page, as seen in the attached screenshot.

Let me know what you think !

Sync not working with term references" - Is it resolved? If so, how?

Posted by krug on September 6, 2011 at 8:20pm

When I add content that I want to translate, the synchronization is performed for the Title and Body but not the terms of the vocabulary.

Following adjustments are made:

Multi-language set sr (Serbian) and en (english)
Created the vocabulary with the "Multilingual Options - Translate. Different terms will be allowed for each language and they can be translated".
I added and translated terms. I paired them. In "Translation sets" they are paired, translated.
In the "Content type" I added the "Manage Fields -> Field -> Term reference", adding the appropriate vocabulary

Drupal 8 Multilingual Initiative status update video, sprint from Sept 14th

Posted by gábor hojtsy on September 6, 2011 at 9:10am

Its been a long time since a discussion or status update was posted for the Drupal 8 Multilingual Initiative, the main reason being that we've been all busy with mapping out the main issues on drupal.org and working on some of them to move forward. Drupalcon London was great in this sense, lots of new contributors came in and seen that there are countless ways to get involved and help. We've discussed and wireframed usability changes, proposed several API cleanup patches and worked on localization update module integration pre-requisites.

Possible bug with Menu.inc in regards to localisation. (Not sure if this is a discussion or I should log it somewhere.)

Posted by antony.lovric on September 1, 2011 at 3:02pm

Ok, here goes, I'm working on a Drupal 6, multilingual site (French and English) and there are two (2) parent menu items have menu item children that point to a child menu item (a view, view_jobs).

Whenever I look a the view in Drupal, it is showing me the wrong translation for the 'parent' breadcrumb. (It always shows the french term.) I think I've tracked the problem down to a query against the menu_links table.

The following query is around line #898, menu.inc, 1.255.2.38. (this is the elaborated query)

Input requested from MultiLink users

Posted by andy inman on August 30, 2011 at 11:06am

This post relates to MultiLink and more specifically to the issue at http://drupal.org/node/796822

As I'm trying to plan a D7 version and would like to finalise functionality, I'd like to get some input from users here (rather than the issue queue, so as to reach a wider audience and maybe use a poll here.)

So, the big issue is to establish the "correct" way sending the user to a suitable page, considering both site language and content language, and trying to choose the "best" combination based on user language preferences.

The big content translation models debate (with video!)

Posted by gábor hojtsy on July 29, 2011 at 7:20pm

Although not planned, the first Drupal 8 Multilingual IRC meeting did drive us into discussing content translation models for Drupal 8 in detail (see the meeting notes). To be able to cotinue that, I've specifically announced the second meeting that it will have a focus on that. And after a little update on the current status, we did return to that topic.

Drupal 8 Multilingual initiative IRC meeting #2

Posted by gábor hojtsy on July 26, 2011 at 12:59pm

Start:

2011-07-29 16:00 - 17:00 Europe/Budapest

Event type:

User group meeting

Building on the success of the first initiative meeting (find meeting notes on groups.drupal.org), we'll hold our second meeting this Friday. I've picked a later time to accommodate more people from the US and Canada, heard some had a hard time getting up so early.

I'd like to use this opportunity to discuss some of the ongoing issues under the D8MI tag and continue the discussion on the core translation module's future, and how can we unify the feature set of that and translatable fields in a way that makes sense for the user cases, with usability and developer experience in mind. It is a tall order, but it can be done. For some background on the use cases and differences between translatable fields and core translation module, please read http://hojtsy.hu/blog/2011-jan-31/drupal-7039s-new-multilingual-systems-.... We'll assume you arrive with this background information to the meeting.

Set default language for new content and UI components

Posted by tsvenson on July 16, 2011 at 6:20pm

One thing that is quite complicated to automate for a site is to be able to set the default language for new content to something else than "Language neutral", especially if the site only has one language.

Not until you add the i18n module you seem to have this option.

Since the language is also used in the markup and will be picket up by search engines, screen readers and other applications, it wold be real nice if there was an option to set the default language when creating new content. "admin/config/regional/language" already have a column for this, but it is not used for this.

Internationalization UX

Posted by Bojhan on July 14, 2011 at 11:37am

There are a lot of challenges in internationalization, after being involved in Drupal 7 trying to streamline some of these experiences. It would be great to expand this in Drupal 8 and make sure that we have a delightful multilingual experience, rather than a "you can actually do it now" kind of thinking.

After a meeting with Gábor Hojtsy, I'd like to give a quick summary what some of our ideas area in terms of focus and outstanding work. Where the biggest problem for me at least, is trying to build a picture what the landscape of multilingual is. Below you can see an illustration made by Gabor about the overarching parts of multilingual and how we wish to unify some of these in the initiative.

Language, langcode, locale, how do I name you? Plans for locale.module in Drupal 8.

Posted by gábor hojtsy on July 12, 2011 at 3:28pm

Locale.module in Drupal 7 does at least these 4 main tasks (besides some smaller ones):

Lets you set up languages and configure them.
Lets you configure how Drupal selects form those languages for certain things (UI, content, etc).
Offers a backend and an interface to translate the UI of code-supplied interface text. (It does provide a half-baked attempt at providing a generic translation storage backend too which is about to be removed in Drupal 8: http://drupal.org/node/1188430)
Lets you import and export Gettext .po files with these translations

Now this is a lot of stuff, and I did not even mention some smaller pieces like supporting node languages and other small bits. One thing locale.module does not actually do is setting up locales. Yeah. If you read up locales at wikipedia (let's say), you'll see that locales in their complete sense are things like string ordering rules, currency formats and decimal separator configuration. Well, Drupal does not do that. In the "industry accepted understanding" of the terminology, Drupal does not support locales, it supports languages and localization (UI translation), but not locales.

Why I'm going into theoretic details is that as part of the Drupal 8 multilingual initiative, we need to take a long hard look at poor old locale.module (even though I did not mention this much yet in my posts, I did work on several issues related to it). Let's see the plans we have issues for so far.

Subscribe with RSS