- I'm building a bilingual English/Welsh site, except only some of the content will bilingual. When viewing the site in Welsh, if there is a page that doesn't yet have a translated version, the menu needs to offer the English version instead.

- The following patch (http://drupal.org/node/76631) makes the URLs on the menu point to the correct language (it changes the URL of the menu items depending on which language you are viewing the site in; if you are viewing the site in Welsh and there is no translation, the menu item for that page points at the English one - this is how it needs to behave).

- But, the actual menu item names don't switch languages. This can be acheived (in a less than ideal way) by translating menu items with the localisation module. I say less than ideal, because as soon as you actually translate a category (which is necessary, so that when you click a cateogry it displays a translated version of the category node), the Welsh pages jump out of the English menu hierarchy. This makes it impossible to deliver an English version for untranslated pages.

- I think what's needed is something like taxonomy translation (http://drupal.org/node/67830), for containers and categories, so that each category's two languages are actually tied to each other. Then, when you select a category for the English version of the page, the Welsh page inherits the same category automatically. The lanugage the actual name of the container or category is displayed in will then simply change depending on which language the website is set to display. I realise this might be tricky, since containers and categories are actually nodes!

- I've found this dificult to explain, feel free to contact me via https://wiki.ubuntu.com/SteveSmith if you want me to clarify anything!

Thank you!
Steve

Comments

venkat-rk’s picture

venkat-rk commented

Just tracking this as I will be doing multilingual sites with category in the not too distant future.

stevesmith’s picture

stevesmith commented

Keep in touch with me about it Ramdak, we can probably learn a lot from each other!
Steve

rkerr’s picture

rkerr commented

*bump* :)

Just finishing up the feature set of a bilingual site, and ran into this snag. Translating a container doesn't actually play along with i18n for whatever reason.

i.e. en/node/4 and fr/node/4 both give the same result. Even if there is a translation for node/4.

Has there been any work on this?

mathieu’s picture

mathieu commented

Tracking this issue as well...

There seems to be some issues with translating a container, category, cck-categorised-types ... anything-category by using "created node" under the "translations" tab. Menu items are definitely broken in very hard to track ways (which make the breadcrumb not appear in the new translation).