Internationalization

I have some cck content and have an english page. I click the translate button and translate to spanish, the content creates the new node, but will now show no translations in either english or spanish (i.e. it is like 2 separate pieces of content).

Using 6.x

Say we have some sites: uk.example.com, us.example.com and fr.example.com. the last one uses our French pages, the first two use our "English" pages. Is there an easy way to handle the minor but noticeable differences between American English and British English. It seems a pain to create separate nodes for all pages (or even one page) just because of the words "colo(u)r" and "meters"/"metres".

In http://drupal.org/node/367595 the groundwork is being laid for multilingual support in the core fields api.

At a May 21, 2009 IRC meeting to plan translatable fields (see this summary), a consensus emerged that translatable fields should emulate the current Translation module behavior.

With translatable fields we are introducing a second way in which nodes (and other Drupal data objects) can be made translatable, alongside the existing (node-only) one.

The purpose of this wiki page is to begin to map out in detail just how field-based translation will work, taking as our basis the existing node-based translation. For each feature of node-based translation, will there be an equivalent in field-based translation? If so, what will that equivalent look like, and how will it be represented?

Most or all of this will go as follow-up patches to http://drupal.org/node/367595; but it's worth starting to map the work out now.

This page so far has a few preliminary notes and needs a lot of expansion. Please add and edit. What further aspects of the existing node-based translation will we need to emulate in field-based translation? What will we need to consider?

What's the best options(s) to structure our multi-country site. The site probably wants to be managed off one installation, but it will be (in terms of thinking about it) country-based not language-based so for example:

www.example.com/ca/fr/widget/price would be in French with the price in CAN dollars
www.example.com/fr/fr/widget/price would be in French with the price in Euros
www.example.com/us/en/widget/price would be in English with the price in US dollars
www.example.com/gb/en/widget/price would be in English with the price in pounds etc

Meetups !!

As seen it was tough to meet as scheduled physically so here is a call for virtual meeting on

#drupal-in

Just hang on IRC channel on Saturday 16th 2009 and discuss if some people turnup i would be there surely mainly entire day :)

I'm a little confused about something. I have a view called events (http://www.wimaxforum.org/wimaxevents) and I want to have that same page but with a Japanese Primary Link at the top. My boss and I decided to keep the menu items within events in English and then add a new menu item in Japanese for Japan specific events or any events our Japanese office decides to translate.

For my Japanese site i wanted to to auto path aliasing and I had for example the pattern about/[title-raw]
But then that would result in a url like this ja/about/日本オフィスについて. But the thing is, more urls on in foreign languages are still in english. I checked on some japanese websites I found. So what is a good replacement pattern that will work for japanese and still have a meaningful url aliasing. doing a node id might work but I like having the title there. What else could I do?

Thanks,
Becky

Hi,

We have a discussion going on at http://drupal.org/node/446360 on whether it is required/better/advisable... to have separate translations folders for each sub-module of a module (each with their own pot/po files).

I have a news page on my site with a path that goes http://www.mysite.com/news and when I click on the japanese flag on my site the path changes to http://www.mysite.com/ja/news so I was going to make a japanese link to it with the word news in Japanese of course. But I tried to get it to link to mysite.com/ja/news and it wouldn't let me . It said that the path didn't exist or I didn't have permission to. Why is this? Is mysite.com/news a different node then ja/news?

New Translations Released this release contains 250+ new translations

Hindi Translations @ http://drupal.org/project/hindi

Contribute to Hindi Translations @ http://drupalhindi.com or http://drupall10n.com

We request you to contribute to The Translations so that we can have a new release as soon as possible

Current Status

Built-in-Interface = 10.65 % Complete
Google Groups Module = 100% Complete

I have been trying to get another language to work on my server and have had problems with bulk translation. On drupal.org I have posted the details I would appreciate if you could take a look and give some suggestions:

http://drupal.org/node/429822

We are adding Japanese to our website with English as our default language. We want to style our Japanese front page with different graphics that have the text in the graphics in Japanese. So right now, I guess our set up is showing the Japanese front page as http://www.mysite.com/ja . My question is how would be template out a new page for the japanese home page? Can we have a template called front-page-japanese.tpl.php? OR, can you not have different page templates for different languages?

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>

Even though English in not a problem for me, I understand the importance and need to offer a website in other languages, so I really like that the new design have that in mind. Particularly as it also means that the internationalisation support for Drupal is moving up a few notches in priority.

Before I go into the main topic of this post, a little note about the placement of the language select. In the mockup (iteration 11), the select language listbox is placed at the bottom. I think it should actually be placed in the header instead as that will make it much easier to find. Especially those, who's English is not very good tend to leave if they don't find a language quickly without having to scroll to the bottom of a very long page. They could also be shown as flags.

Oki, back to topic. I have one site I am using the Internationalization modules in and it works just fine. The only real issue though is that browsing modules and other add-on stuff and finding information on what languages they are available in is not very easy. In most cases I have to actually download the module and check if it supports translations and if so if it is available in the language(s) I need.

So it got me thinking a bit about how this can be improved on drupal.org and I came up with the following. I will use modules as example, but I believe similar features can be applied on other areas as well, such as themes.

A report back from the virtual code sprint on internationalization in Drupal core

What if the new Fields API in Drupal core could be used in multiple languages, so that any object type could be internationalized just by adding fields?

That's exactly what the "multilingual fields" patch currently being developed would make possible.

Multilingual fields is one of two major improvements to Drupal core's multilingual support to come out of the recent code sprint on internationalization.

Currently when new content is entered the language setting defaults to "Language Neutral".

This tends to cause problems in our translation assistant module when it comes to sending content for translation. Translations wont happen if the content is "Language Neutral" and this causes confusion for users.

Over the past two weeks at the core internationalization virtual sprint, we've been working on translatable fields. This would allow any core field attached to a node, user, taxonomy term etc. to be multilingual.

Core already allows for translating one entire node into another node, but you can't for example have translatable user profile fields, or taxonomy descriptions - and we're hoping this patch would be an enabler for that (and also make node translation more flexible).

My name is Amir Helzer and I'm responsible for ICanLocalize Translator - a new module that automates the translation process for Drupal (6) sites.

It complements i18n module by allowing to send new or updated contents to translation storing the translation back in the Drupal system.

In our first i18n sprint scoping session we identified two basic goals to make Drupal fully multilingual:

• Object translation. Make object names and labels translatable. I.e. content type names and descriptions, field titles and descriptions, etc..
• Content translation. Make user created content translatable.

I posted an update on our first day of the sprint here (so it would get to Drupal planet):

http://civicactions.com/blog/2009/feb/03/internationalization_core_code_...

Want to join in the sprint? Please do! Join us in #drupal-i18n any time on Wednesday Feb. 4. If you're looking for a way to contribute, look through http://drupal.org/project/issues/3060/term/301 and choose an issue you want to take on. Then come into #drupal-i18n and talk talk through the issue.

Never contributed to Drupal core before? Don't worry--we'll help you get started.

See you there!

I've just released the first alpha of a new module called i18n_access. This module aims to fill a gap in access control for sites using i18n.

The module adds a list of checkboxes for each available language to the user add/edit form (only visible to users with 'administer users' permission). These language permissions are combined with the normal user permissions to give more fine-grained access control.

Currently in Drupal core we have no general solution for making fields translatable.

There are several emerging options. Here are some. If you know of others, please add them in, and also add more information on those already listed.

Choosing between these approaches is the key challenge as we implement translation of user-defined strings in Drupal 6.

1. Extend the locale system to support translatable objects
   • Summary: This option would extend the
   • Issue: http://drupal.org/node/141461.
   • Pros
     • Existing UI and storage.

I just noticed that the 1.0 version of i18n has been released for Drupal 6. Congratulations to Jose and all others involved!

Agenda

Day 1, Feb. 3: Scope and queue clearing

• Introductions
• Set goals for sprint: identify development priorities
• Discuss and plan each of the selected new development focuses
• Divide up patch responsibility

Core committer session with Angie after 03:00 GMT, 1 hr.

• Review bug fixes in patch queue, work through remaining issues with fixes.

Day 2, Feb. 4:

• Continue work in small teams on major development priorities.
• Fix identified issues in bug fixes and tweaks.

Core committer session, 2 hrs

Hello,

I’m building with Drupal 6.9 a multilingual (English, Hebrew, Arab, Greek & Turkish) site for a Middle Eastern NGO (http://b1.mideastpan.org).

Setting of a multilingual site with I18 pack was, for a non-programmer ‘Drupal newbie’, pretty straightforward. It seems that content translation and switching between interface & menu languages are working fine (Bravo).

After setting a forum, the following ‘strange’ problems appear:

Hello Drupal folk,

I've been looking to build a multilingual (and localized) site for a client. (Please tell me if I'm in the wrong area to be asking/discussing this stuff).

I've been researching all the options and starting to confuse myself as the best method to use.

Country Set-up

The site I want to create has a few countries (i'll try keep out specifics so others can relate to it):

• Country A
• Country B
• Country C
• Country D

Dear group

For days now I am looking for a way to translate the text strings in

http://api.drupal.org/api/function/_user_mail_text

I have one issue regarding the french language integration, i received this message and i don't know how to fix it : the plural formula could not be parsed

What is the best practice for adding a local calender(for example jalali calender or hijri and ...) to drupal?

Hi,

The translation of content and textual strings has much improved in Drupal 6.
However one problem that keeps popping up for most of our clients, is the translation of menus.

Most of the solutions regarding translatable menus involve having multiple menus / blocks (one per language) set up, and show them conditionally based on the current language.
However for most of our clients that's not an ideal solution. For them having to add an item to the menu multiple times is counter-intuitive.

I have created some new fields in profile . I need to translate the content of these fields. I can't find the way on drupal.org.

I'm using drupal 6.

What's mean that 'All languages' in menu item option?
I didn't need to translate the foot link menu, so i chose the 'All languages' option. My understanding is if chose this option, the menu item will be displayed in all page, but the fact is on the contrary.
And I read the document, it said that '/ -- for all languages', but i can't use '' in the link.

Hello:

I have i18n module installed in Drupal 6. Using drupal_execute I have a created a lot of nodes with the info in a database.

I have also the translated data into the database. Therefore I like to create the "translation" of these nodes using the same system.

I Just submitted a patch for the Drupal eCommerce which included a localisation patch for Irish counties - so autocomplete forms work when a customer from the Island of Ireland is selecting their county (state).

This is by no means an official list. It's a list I compiled myself using the county codes from car registration plates as the basis.

If anyone knows of an official county code list for Ireland, please post a reply up here.

I installed Internationalization module. I add another language and translate one page to another language, which works great. The problem is the language switcher shown up near the footer area even though I have already configure the Language Switcher not shown in any block in Site building/blocks. Of course it doesn't shown up when one page only has one language version. Any one has the same experience? Thanks.

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.

I needed to have a graphical view on l10n_server database so I created following simple image. Feel free to correct errors and reuse:

Click to zoom

Also, the scheme has always been available in the commentary http://drupal.org/node/203658
You can see it here: http://drupal.org/files/issues/ls.gif

I am working on a project that uses internationalization for Drupal 6. I found that when a Menu item points to a View or an Aggregator feed, the menu item is not hidden properly for languages it is not set to. For instance, an English menu item shows up in the German and French menus.

I solved this problem for Views (thanks Drupal community) by using the insert_views module to put my views in a Page or Story. If a menu points to a page or story, it works correctly by hiding if the menu item for a language that doesn't meet the language being displayed.

I would like to add a menu item (primary links) the same title could be translated on the menu and be bound by the translation of the page to which it points.

I have the translation turned into a clean installation of Drupal, when I create a page in English and turn a menu item to this page, for example if this node is the node 01 to translate the page he set up the node 02 and consequently the translation translated menu item should point to the node 02 translated.

Doug and I are working on a new internationalization review for coder. The following checks are in the D6 dev version already (thanks to Doug!):

<

ul>

Hi all,
I wanna crosspost here my issue because there's something that i can't understand into drupal translation mechanism or something that could be better.

Here's the topic:
http://drupal.org/node/312216

As said in the first comment I see that someone's having the same issue with D5.

Thanks,
ingo86

What would it look like if we stored information on whether a field should be translated in the schema?

If you could just put

in your field's definition and that would be enough to trigger proper handling when an item is inserted, updated, or prepared for display?

I just posted for review a module that tries to answer this question: http://drupal.org/node/312038. Please have a look and review.

Hello, we are redesigning the Drupal support page. We have moved support in other languages to a dedicated page in the getting started handbook.

http://drupal.org/support-in-other-languages

If you know of a Drupal support site in another language please add a comment.

Thanks,
Kieran

An issue in Drupal 6+ contrib needing some thought is the current misuse of t().

Prior to D6 there was no clear way to provide translation for strings other than ones built into code. So many module authors started resorting to passing variables through t(), e.g.,

There's a number of ongoing issues for various contrib modules where i18n support is being introduced or refined for D6 at the moment. Would be good to consolidate some of these efforts so things work consistently where possible, and hopefully encourage some extra reviews of the various patches. Most of these links via nedjo.

I'll start with a quick list of some of the issues:

• Voting API: Handle multilingual content

Hi people, a quick announcement that I hope will be of interest to Views users on D5.

The problem

In a View (D5) the field labels don't get translated. A similar issue exists with the Page Title of the View - it cannot be translated. You can work around these issues by creating one copy of the View per language, but that makes maintenance really difficult as any changes will have to be made on each copy.

A solution

The Views Translate module - www.drupal.org/project/views_translate - now available.

I'm working on a contract for D6 rewrite of NDP.ca, which presents content in English and French. Since menu translation isn't completed in D6, and because the available workarounds were judged too awkward for our workflow, my co-worker Greg Cameron has written a small but useful patch to i18nmenu, nice_menus, and menu.inc which allows us to have one primary menu with one set of links (set to "all languages") with menu titles and paths (including url aliases) translated.

Hi there,

I've been trying to figure an easy solution which allows images to only be uploaded once but to allow translation of the image title text. Enabling the image type as a translatable content type means when I create a translation for an image I have to upload the image again. This isn't ideal and I'm keen to know how others would approach this.

Cheers
Matt

How do I assign user a permission to edit only one language in D6 multi-language site?

I've posted some documentation on multilingual module development for Drupal 6 http://drupal.org/node/303984. The idea is to pull together what module developers would need to add multilingual support to their module.

Please review and improve!

Hi everyone,

I was just working through some detailed i18n issues and started to wonder - does anyone actually use the language negotiation setting: Path prefix with language fallback? It occurred to me that this option is probably fairly unused (especially in D6 as people tend to leave the default language with no path prefix). However perhaps there is a great reason to use it that I'm not aware of. If someone is using it please let us know why, and why you feel it works best for your site.