Multilingual/i18n

Posted by Arnaud HERVE 10 Feb 2005 11:24 GMT-0000 posts: 179 ☆ ☆ ☆

I agree with you about the necessity of having the same language in content and menus.

My idea is that menus must be subordinated to content. Because the person who is able to read content in one language will also be able to read the menu in the same language, hence you have a sort of guarantee that the reader will not have to see a language that is not understood, in Language Exclusion terms. And the person wants to READ the content in priority, and the menu is just there as a convenient tool.

Maybe it is a good idea to see how the European Union's website deals with this feature.

Posted by sylvie greverend 10 Feb 2005 21:20 GMT-0000 posts: 1092 ☆ ☆ ☆

I know a site working like this:
It uses the switch_language module to switch language, and it uses the best_language option and each page has a translation and each link in a page is the link in the same language

Posted by Gary Cunningham-Lee 28 Sep 2005 08:26 GMT-0000 posts: 4656 ☆ ☆ ☆

I'm working on a site that will be in Japanese and English. The site is using a vertical phplayers menu at the top of the left column, called from tiki.tpl. To have the languange-appropriate menu used, I put a statement like this in tiki.tpl:

{if $language == 'ja'}
      {phplayers id=44 type=vert}
{else}
      {phplayers id=43 type=vert}
{/if}

I had to make two menus since the menu items need to point to different pages, depending on the language. I first tried doing this dynamically with just one menu, but the page names (many of them with Japanese characters) can't just be translated but need to be URL encoded.

I'm using the "Multilanguage" feature to set up alternative wiki pages and articles. So far (site isn't public yet) things are working well.

-- Gary