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. Important links:
The Translations group is where to go if you are working on translating Drupal core or contrib modules.
Using Key instead of "natural language" for translation
Hi all,
hope this is not a traited point...
I'm french and i used drupal for making an I18n website.
My pb is that one time i make my code (in english) and translate it into languages, if i make a change on english transatable string, i have to retranslate, and upload, corresponding string for all other language.
Exemple:
t("how stupide is that")
---french >>> C'est stupide
---spanich >>> Esto es estúpido
Now let suppose for optimise my english web page i want to change it to "this is stupide"
t("this is stupide")
---french >>> lose
---spanich >>> lose
Views switches to other language on a Default Language page - but OK when Cache Tables cleared
Hello,
I built a website for a client in English - all worked fine. But when we added the multilingual module (i18n) (for Spanish and German translations) and enabled Views Translations we had an unexpected issue- which only affects anonymous users - no problem for authenticated users.
Languages are resolved to unique domain names: English is www."websitename".com, Spanish is es."websitename".com and German is de."websitename".com. The default language is English.
Drupal Developer (Freelance) | Quevin, LLC
The primary issue is with "language fallback" failing when the i18n language configuration is set to "Domain name only." This happens in most A-grade browsers. German is the specific translation we're dealing with...
This topic seems to cover the general problem:" language_from_browser() doesn't parse language tags correctly, has a broken logic"
http://drupal.org/node/221712
Component: language system
Perhaps the patch will work, and I'm trying to find out if there's a release to fix this asap. Can anyone help ($$) in the meantime?
D6 Internationalization: "Domain name only," Boost, multiple servers, and subdomains
There is a separate "primary" site (in another system [NOT Drupal]), and the Drupal site has two servers with one database on one of those servers connected to both Drupal instances. Our problem is with the two Drupal servers and DNS (domain/subdomain) settings to manage them.
One instance has a minute-by-minute CRON job running to keep the other in-synch, with rsync. Only one of those servers is open to login and edit with a subdomain pointing to it directly on the network. The other server has a read-only user setup for the database connection, just as a precaution.
WPML Multilingual CMS in Wordpress
I think we should learn something from WPML Multilingual CMS plugin for wordpress. Yesterday I made site that was too simple for Drupal in Wordpress and at the last moment client asked for multi language support. My hands went cold. Used WPML and was surprised how easy, fast and simple process was comparing to Drupal - most importantly because of KISS aproach to many parts of plugin and how it works.
Override configuration for interface (different ways for different hosts)
Hi all,
I am looking for some advice. I am trying to make a D5 implementation have 2 different behavior depending on the host.
if ($_SERVER['HTTP_HOST'] == 'www.host.org' || $_SERVER['HTTP_HOST'] == 'host.org'){
$conf['i18n_translation_links'] = 0;
}elseif($_SERVER['HTTP_HOST'] == 'admin.host.org'){
$conf['i18n_translation_links'] = 1;
}
Does this make sense? Is there a better way to accomplish this?
Thanks!
Problem in localisation of primary menus when using Active Translation and Select Translation modules
I'm having problems with my multilingual site. The site has two languages. For some content that is in default language and has not been translated into the other language it is important to show it to the user. To solve this I'm using Select Translation module for Views and Active Translation module for the site nodes. For these modules to work I have to select "All content. No language conditions apply." in Multilingual System configuration.
Does anyone know how to i18n the site name?
Hi All,
I got one problem about the site name i18n.
For example, my site has an English name is "My Drupal", and its Chinese name is "我的Drupal". I want the site to display the right site name according to different languages. How can I use i18n module to realize this feature? Many thanks.
Changing the language negotiation
I want to change the "Language negotiation" setting (admin/settings/language/configure) from "Path prefix with language fallback" to "Domain name only" on production site that have thousands of translated nodes.
On a first look it seems that I need some Apache redirects for SEO reasons. For example, for the Italian pages it may need
RedirectRule ^it([/]?)(.*) http://www.mydomain.it$1$2 [L,R=301]I didn't find any related guidelines. What are the side effects? Are there some "best practices"?
Thank you!
Claudiu
Why are URLs available for non-translated content
I've been having a look at the internationalization module for the week or so and a couple of things have put me off using it. Of primary concern is that it generates URLs for untranslated content. For example, if I create an English page with the URL 'A' then the page will automatically be available via the URL 'ja/A'.
This isn't great at all in SEO terms as two URLs are being created which contain the same content. This can get you penalized by goodle. Is there any way of preventing this?
Taxonomy internationalisation
In Drupal 6 you had 2 way to support multilingual taxonomy :
1) a master monolingual taxonomy with internationalization done by i18n module :
example of use : $termslg=tt('taxonomy:term:'.$term->tid.':name',$term->name);
Problem : only one master monolingual repository use in input form and no good environment to check and maintain translation of term for large list
2) a full parallel multilingual taxonomy system with term existing for each language
example of use : $termslg=i18ntaxonomy_translate_terms($terms, $lang);
Creating a dynamic path menu item for translation to current content
I have used the code found here http://drupal.org/node/313814. This code returns a themed link to the translation of the current path.
But this makes theming difficult sometimes - I'm not a CSS expert and I have a hard time when things line up properly in one browser but not in others. In many cases the designers I work with like to display the language switcher as part of a menu. I've messed around with absolute positions for the language link so it sits next to the other menu items, but it always ends up a pixel or two off in one browser compared to another.
default language and string translations
String translation. This works differently to Drupal standard localization system: The strings will be translated from the default language (which may not be English), so changing the default language may cause all these translations to be broken.
(D5) Creating a translations block that is aware of node tranlations
I've currently got a Drupal 5.13 site in development that I have set up to use 3 languages using the Internationalisation module (i18n, v5.x-2.4).
My question is about the Translations block, it currently shows all the enabled languages, but I have a request from the client that if the node being viewed is not available in one of the 3 languages it should not show the link to that language.
Here's an example to better explain...
Site has 3 languages: English, French and German
Show path aliases to nodes in other languages
I'm encountering an issue with URL's to nodes in a different language than the user's current language. Currently, the site is set up with English as the default language, and French in a path prefix of /fr. On the home page, there is a view of all book nodes, some in French and some in English. However, if your current language is English, the French bookURL's are set to fr/node/. If you switch to French, all English books are shown as node/.
I've found out that if I insert the appropriate paths into the url_alias table I can make things work as expected. For example:
Why do translations not work
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
Word substitution rather than translation?
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".
Translatable fields implementation details
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 way to structure a multi-country site (not just multi-language)?
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
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. Important links:
The Translations group is where to go if you are working on translating Drupal core or contrib modules.
