Translations

You intend to help to translate the Drupal interface to a language? This is the place! Look into the translator's guide in the Drupal Handbook for detailed documentation, as well as get onto the translations mailing list.

The internationalization group might also be interesting, dealing with content translation support issues in and around Drupal.

Where to start translating drupal after new localize is added?

Posted by barnamah on May 23, 2013 at 2:25pm

Hi,
I don't know where to start now.
I clicked on the "add project" but didn't know which options are referring to translations.
I visited this page: http://groups.drupal.org/translations and there is not clear starting points. All it has are the 2 links and comments.
please some one guide me.

thanks

How to translate taxonomy terms displayed in a block as language changes form language switcher block

Posted by gaurav-varshney on December 12, 2012 at 9:39am

i have created a vocabulary with localized multilingual option and translate the term in two language say en,sv next step what i want to do list all taxonomy terms in a black and the term inside block is translated as user changes the current language.

(ALL GOOD!!!!) Call for volunteers to help with multilingual training at BADCamp on November 2nd

Posted by Kristen Pol on October 17, 2012 at 10:34pm

Start:

2012-11-02 09:00 - 17:00 America/Los_Angeles

Organizers:

Kristen Pol

Aimee Degnan

Event url:

http://2012.badcamp.net/program/training-multilingual-drupal-sites

====================================================

THANKS FOR THE AMAZING RESPONSE!!!! WE HAVE A GOOD POOL OF VOLUNTEERS NOW :)

====================================================

If you are going to BADCamp on November 2nd and have an hour or two or more to help out at the free multilingual training:

http://2012.badcamp.net/program/training-multilingual-drupal-sites

please leave a comment! I've attached a draft of the training notes/schedule.

Website Developer | Globalbility

Posted by matsbla on October 7, 2012 at 11:54am

Employment type:

Contract

Telecommute:

Allowed

I need help to make a website to connect volunteers in a collaborative translation work. It is a postcard and translation project, you can see our simple website here to get an idea: www.globalbility.org - It is a non-commercial initiative, it is registered in the Norwegian Voluntary Register as a NGO.

http://www.globalbility.org

Import custom translations from own localization server to clients

Posted by StudioFonkel on August 3, 2012 at 9:53am

Right now we're developing 3 sites in German, Dutch and Swedish.
Each site will have content in different languages (25 in total, but for the Swedish e.g. 10, for the Dutch 17 and for the German 19 language)
Some of the languages are quite exotic and not welknown.

We use for this a 3-letter language-code and have a central localization server to manage the interface and content-translations.

What I want to accomplish is that on each client (Swedish, German and Dutch) the enabled languages are automatically updated from the localization server.

How can this be done?

Tümü büyük harf (uppercase) yazılarda Türkçe karakter sıkıntısı

Posted by Sahin on July 30, 2012 at 10:31am

(Başlangıçta wiki sayfası olarak açılmıştı; buraya taşındı. -Şahin)
Abstract for English-only readers: "Uppercase style causes problems with Turkish characters ğ, ı, i, ş which should be transformed to Ğ, I, İ, Ş respectively but shown as G, İ, I, S wrongly."

Merhaba, Arthemia temasında birincil linkler menü bloğunda Türkçe karakter sıkıntısı yaratıyor.. Örneğin İletişim kelimesi İLETISIM olarak görünüyor.. Drupal 6.x için çözümü nedir?
Yardımlar için şimdiden teşekkürler..

Managing translations in code

Posted by ptmkenny on March 20, 2012 at 3:20pm

I am working on a fairly large site that is being translated into multiple languages and I'm keeping as much configuration as possible in code using features, strongarm, etc. I'd also like to keep translations in code if possible but I can't find any straightforward way of doing this.

Since I have separate dev, staging, and live servers, I'm currently visiting the languages page, exporting each translation manually, and then importing manually to each server... this is time-consuming and error-prone, as it's easy to forget to import or export one of the translations.

Proposal: Loosen rules regarding patches that may be backported during a stable release (7.x+)

Posted by webchick on February 18, 2012 at 10:06pm
Last updated by webchick on Mon, 2012-02-20 23:22

It's great when we get newly injected energy into usability efforts in Drupal, as happened with the Drupal Usability Study at Google last week. However, these patches always run aground of various "freezes" we put in place in the stable release of Drupal:

API freeze: Don't commit patches that break backwards API compatibility within a stable release, for the benefit of contributed module and theme authors.
String freeze: Don't change any user-facing text (e.g. anything in a t() function), for the benefit of translation teams.
UI freeze: Don't commit patches that affect the user interface, for the benefit of the documentation team, as well as to not invalidate tutorials, screencasts, books, etc.
Feature freeze: Don't commit patches that add new features; stick only to bug fixes. Additional functionality gets added in contrib.

As far as I can tell, these guidelines are not actually written down anywhere, but simply passed down word-of-mouth from core generation to core generation. I want to do two things in this thread:

1) Create documentation around these guidelines.
2) Propose that we change these guidelines to make them looser and allow more classes of patches to be backported, particularly minor UI tweaks and string improvements.

Here's a proposal (co-developed by Dries, Moshe, Alex, and I), with the items in bold being ones that we propose to change, the rest being documented to the best of my current understanding. My hope is that this can both help is iterate faster on the core product, and also provide additional incentive for people helping with Drupal 8 core development, as there'd be a chance of them seeing their changes in a version of Drupal sooner than 18+ months away.

Drupal 7 Internationalization and Localization Book: Advanced Topics Request

Posted by Kristen Pol on January 17, 2012 at 4:18am

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!

Installation of a website in two options

Posted by shenagarg on January 3, 2012 at 4:30pm

Hi all

I have developed few websites in Drupal. I have the knowledge of blocks, menus, views etc. Recently I got a project from client asking for installing a website in two languages English and Spanish. I tried to do it but somehow I could not get it.

It was strict deadline project so I could not do translation properly. Rest all was done.

I would like to learn how I can make a website in two languages. Are there any kind of options available like:

Beginner help on translating string in different contexts

Posted by alberto56 on October 9, 2011 at 12:31am

Hi all,

I'm pretty new at translation and localization, but I can't seem to find the answer to this one: I've come across the string Testing in Drupal 8.x (possibly the same in 7.x), which is used in two contexts: (1) as in "The testing module" and (2) as in "Now testing". The distinction does not seem to be made in Drupal core.

In English, "Testing" works for both, but the French translation, "Test en cours", only works in context (2).

Please Help on Saving Contents in Non-English language!

Posted by adams950 on September 23, 2011 at 7:40am

Hi!

I have posted this question on Drupal forum few days before. But I no one replies... So I want your help!

I'm using Drupal 7, works pretty on English.

But If I try to save an article or basic page in Non-English languages (like Sinhalese, Tamil, Arab, Hindi), it shows an error message and does not save.

I'm using Drupal's languages, and have tried language packs (.po) which downloaded from Drupal site.

I have installed Language and Translation modules (which come with drupal).

And the user interface works fine in that languages. But saving does not work.

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.

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.

Approve all

Posted by Hadi Farnoud on July 9, 2011 at 2:31pm

Approving translations are really time consuming. I know for a fact that some translators in my group know what they're doing. It would be great if I could approve all suggestions from a particular user.

Using fields (and maybe entities) for configuration in Drupal 8

Posted by Gábor Hojtsy on June 8, 2011 at 4:05pm

Judging by the low number of comments (zero AKA nil) on my post on how custom user editable data in Drupal 7 modules are now localized and my commentary and Drupal 8 proposal there, I've decided to reformulate the basics of the ideas explained there with more of a focus on high level architecture questions.

Move interface strings entirely out of Drupal code files?

Posted by Gábor Hojtsy on June 8, 2011 at 1:56pm

This was suggested several times: one, two (see dropcube's comment, not hotlinkable), and most importantly a whole discussion thread started by Jose Reyero at http://groups.drupal.org/node/151169#comment-507464.

Let's talk about string freeze, bay-bee!

Posted by webchick on June 8, 2011 at 3:40am

Back in D5 or D6, we introduced a rule of "string freeze", meaning we would not change/add any strings in a stable release of Drupal that was not clearly a bug fix (and a critical bug fix, at that, iirc) lest poor, hapless end users do a minor update of core and be slapped in the face with English in their French/German/Swahili site.

I wanted to open this up for discussion up again now that we're in the age of localize.drupal.org. Is this formally hard-and-fast rule something we can look at loosening a bit? It would certainly put a lot more options on the table in terms of incrementally improving D7's UX, and also in terms of backporting non-backwards-compatibility breaking features (which is on the table for the first time in D7, thanks to the testing framework).

Here are a few specific examples that have come up recently:

Drupal 7 Translation Campaign

Posted by good_man on May 20, 2011 at 12:57pm

In case you didn't notice, we began a huge campaign to make the process of the translation faster, more efficient, and more open.

I got the privileges to maintain the current translation, I published an introduction blog post on my blog, and followed it by the summary of everyday's status, news, and discussions.

Fixing translation errors with @placeholders

Posted by Spudley on May 16, 2011 at 10:36am

Hi.

I have a problem with a few translations that have been done for our Drupal site.

A number of the translatable strings in our system contain @placeholders for inserting variables into a string at run-time. These are generally fine, but a few of them are breaking when the site is translated.

The problem appears to be due to punctuation on either the original or translated strings.

For example, an original English string may look like this:

@user's picture

But when it's translated (in this case to Danish), it comes out looking like this:

@users billede

Subscribe with RSS