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.
GUI add multi language
I'll add multi language by use I18N for drupal6.1 plus GUI for add multilanguage
and multiseletion use language in web.
Automatically fetching translations
Hi!
In D5, we introduced Autolocale module, enabling users to import translations after enabling module / during installation. However, this had few caveats, as timeouts on cheap shared hosts, etc.
In D6, Autolocale is built-in core, using batch API and just works very well.
What do you think next step should be? From my point of view:
"Let Drupal automatically fetch translations from a server".
Read more
Creating a Multilanguage Site with D5.x
I'm new to Drupal, I am about to create a multi-language site, I had to go with D5.7 since D6 is not yet compatible with many modules that I want to use.
I've been researching drupal sites for a step-by-step guide , I found some information in drupal handbooks but I still have many questions:
- the locale module allows to translate core drupal modules and strings, does the i18n module allow to translate any newly installed modules ? or is it just about translating content (nodes) ?
node::page strings not being translated?
I was suggested to ask here why there are string not being translated of the page node? The string that are not being translated are page; title and body. Why is that and can I override it?
Read moreDrupal 6 press release needs to be translated into multiple languages
Hello, we would like to release the Drupal press release in multiple languages to show case the internationalization capabilities of Drupal 6.
The press release is available at http://drupal.org/press/drupal-6.0/en
Required/pending translations:
Hindi - http://drupal.org/press/drupal-6.0/hi
Cantonese - http://drupal.org/press/drupal-6.0/yu
Chinese (Mandarin) - http://drupal.org/press/drupal-6.0/zh
Esperanto - http://drupal.org/press/drupal-6.0/eo
Gujarati - http://drupal.org/press/drupal-6.0/gu
Japanese - http://drupal.org/press/drupal-6.0/ja
The battle of the path between i18n and globalredirect
As D6 is getting really close and we all try to test "everyting" I stumbled into an "old friend". This problem started up like a bug/race between the globalredirect and the i18n module. In D6 that part of i18n is moved into the D6 core, so all you need to test/trigger it, is a D6 installation and the globalredirect module. No I'm not so sure anymore, if it is a "D6 problem" and if it should be moved to D6 issues or if it still is a isolated globalredirect bug?
I just want to be sure that the path-handling in D6 is as robust as possible. Is jose also the maintainer for the "core part" of i18n? "nicholasThompson" write that he is fully booked and don't have the time to look into the issue, and that's perfectly OK, but I want to get the i18n people's attention, and everyone else involved in making international sites, and maybe there is an other way to solve it.
--
Stein Magne
http://smbjorklund.no
XLIFF mass export
Hi !
I've written a small module to mass-export nodes into XLIFF files because I needed a complete site-translation.
It exports all nodes to "files/xliff_export" creating sub-folders for each node-language.
Works with i18n and localizer nodes.
It uses XLIFF Tools module.
download here: http://ww1.peak.at/xliff_massexport.tar.gz
Alexander.
Read more
locales and the latest greatest D6 beta 3. am I doing something wrong?
Hi Gabor et. al,
I'm starting to play with the D6 beta 3 and I'm loving it. Hopefully I'll be able to contribute something, even if only use cases and a some patch review.
I am having trouble with a locale/internationalization issue. Is this a good place to post?
Having installed D6 beta 3, I ...
a) created a story node with some text in english,
b) enabled the locale and translation modules
c) enabled imported the D5 french localization of the site (which got the vast majority of interface strings),
d) did my own special ;-) version of a french version of my story node
Factory Joe's Review
Copied from http://factoryjoe.pbwiki.com/FeedbackForDrupal6 so people can comment and act on it.
Please help turn the @TODOs into into tickets and patches!
Installation
- It's awesome that Drupal defaults to install.php if you haven't previously setup the site. That's a much better experience than having to know that you have to hit install.php first. Then again, it also means that you could be intercepted; unlikely but still something to consider.
Show case sites by Geography
Hello, we are trying to get Drupal case studies, from show case sites by Geography. North America, South America, Europe, Asia, Africa - If the sites have a cross geographic element or are internationalized then that would be even better. The goal is to show that Drupal is being effectively used around the world.
Drupal sites by Geography - Internationalization use cases
Top African Sites:
Africa
Read more
Multilingual User Profiles, what are the options?
What options does one has when trying to set up an internationalized or multilingual user profile at multilingual site. When useing the core profile option the i18n module provides the posibility to translate the names of the profile fields, which might be enough for some profiles, but if you want a profile where user writes an introduction of him self, you are in trouble. Exposing the user entered text for translation trough t() function is not a good option.
Read more
Language settings for multilingual users
The language support provided by the i18n modules Drupal 5 and (it seems) from the dev. version of Drupal 6 makes makes it easy to maintain content in multiple language versions, but doesn't seem to handle multilingual users very well.
The menu settings for a multilingual Drupal should be able to choose between:
1. Show only nodes in your default/preferred language (suitable for monolingual users and for sites where all content has been translated) This hides content from languages other than your own.
Simple Localization System
See http://blog.worldwidelexicon.org/2007/05/25/simple-localization-system-sls/
Read moreSLS is, as it suggests, a simple way to localize applications and websites. The system works as follows, and is easy to implement in a wide range of scenarios. Let’s imagine that you have a web user interface that you want to make available in many languages. With SLS, you simply do the following.
Drupal 6 core RTL email support
Updated: June 20, 2007: RTL HTML Email now possible with my patch to the new htmlmail module.
Requirements for Drupal 6 core RTL email support - Request for comments
It has been 8 months since I've implemented a Drupal 4.7 user.module patch to support RTL emails (attached).
My next target is to ask for the RTL/i18n community help to update the code and migrate those proven changes into the Drupal 6 core. This will save tons of later headache.
Here are the basic requirements - I will need your feedback on the concept (implementation is quite straightforward).
Read more
Auto Translate
I just started the Auto Translate project. This module, when complete, will add a button to the node translation tab that will fill in a textarea with a (very rough) translation from a third party automatic translator, such as Babelfish or Google. The module may also be configured to translate the content within a textarea.
Read moreRTL Language switching block demo
Now that the RTL support is in core, here is a test RTL language switching on the fly.
I've installed the Language switcher patch, and activated the block - It works great - even with CSS compression tuned on. Test it now on http://dev.drupal.org.il and try to switch the language from LTR to RTL.
Update, May 31: The bluemarine RTL CSS patch has now been entered into Drupal 6's core. The dev site now displays a beta version of the next RTLised theme - pushbutton - for review (you can still select the bluemarine RTLised theme when you login). I've opened an issue Core RTL pushbutton theme is almost here - your help is needed.
Amnon
Read morePlaying with Drupal 6's multilanguage support
Last updated by David Lesieur on Tue, 2007-05-22 22:21
Here are some issues that have been identified during today's Montreal Drupal Meetup. This document was written collectively by some of the attendees in a Gobby session (so please don't shoot the messenger! ;-)). A wiki page seemed like the next logical step. Maybe some of these points should be posted in the issue queue (if you do so, it could be nice to edit this page and add the link).
Read moreHelp Drupal 6 rock in the multilanguage world!
Last updated by gábor hojtsy on Thu, 2007-07-19 19:37
For Drupal 6 to be able to come out with some fundamental multilanguage support changes, reviews of some modifications and improvements are needed. There is not much time left until the code freeze, but we have a list of important issues and some possibly nice additions for you to look at. Lot of the groundwork material we developed is already in Drupal 6, which makes it possible to provide some cool user facing functionality. Now it is a good time to review the suggested changes, propose corrections and help Drupal 6 to rock in the multilanguage world.
What's already in Drupal 6? A new language subsystem which supports multiple text groups to store translations in (additionaly to the built in interface translation text group available before). There is built in support for language dependent paths and domains, right-to-left written text, with some of the themes already capable of displaying RTL pages out of the box (more to come). Interface translations are automatically imported from the file system when you install Drupal or you enable modules and themes. Posts on the site can have language associated with them, and there is a simple content translation module built into Drupal.
What is left to do? Well, the following:
Translating site settings
http://drupal.org/node/155381 - The absolute minimum to support site settings translations with a contributed module
Translating content types, user profile fields, etc.
http://drupal.org/node/155047 - Minimal object translation wrapper for content type, profile, aggregator, etc. translation
Themes still missing right-to-left display support
http://drupal.org/node/148084 - Pushbutton RTL styles
... - Garland and Minnelli RTL styles
More visible language support
http://drupal.org/node/154151 - Language-aware search
Usability improvements
http://drupal.org/node/52990 - Redoing the locale module translation web interface (see http://groups.drupal.org/node/3916)
... - Define and implement Drupal 6 translation packaging format, redesign interface translation workflow (this is done as part of Google SoC 2007)
Would be nice for multilanguage features, but probably not going to happen in Drupal 6
http://drupal.org/node/147041 or http://drupal.org/node/146033 - Two different approaches for built-in site settings translation
http://drupal.org/node/141461 - Translating any objects in Drupal (it has a good UI, but the performance is not acceptable yet)
http://drupal.org/node/141419 - Rework profile categories (has many advantages, for one being able to translate categories)
http://drupal.org/node/145164#comment-250759 - Refactor variable defaults
... - Eliminate t() from $link parameter of watchdog() calls
Directionality functions & integrating RTL CSS files in core modules
This is an old issue, and I wish to get a clear up-to-date status of the situation in Drupal 6 (or 5). It may have been answered already, so a redirection would be as good as an answer :-)
- RTL CSS files in core: In order to ease the RTLization of themes, and to set a nice example for themers and module developers, core modules should come with and RTL version of CSS. Such a set already exists, and is used in every hebrew Drupal site, and surely in other RTL languages sites as well.
