I had a customer who wanted to specify a different site language for their events page made with Matukio. His main language was German and he had a single page, which had to be in English. I've wasted more hours than I'm comfortable to admit on this issue and that is why I thought that I'll share the solution with you, in case you need it.

If we were dealing with a standard multilingual site, the solution to this issue would be pretty straight forward. Define a new content language, enable the language filter plugin, create a menu item for our page and set the language to English. If we go this way we run into the problem that once a user lands on the English version of the page, all links on the site will get /en appended to them. But we don't want this. We want that the links stay as they are.

Today I've released CTransifex 1.5. It fixes all reported problem since the last release (problems with the installation of the language packs) and also introduces a new language view, that will give your users more information about the status of the translation:

The "Contribute now" button will lead users directly to the language editor in transifex.

We've just released a new version of the CTransifex extension. (you can download it here)

In this version we now support the generation of language packs for esperanto. We've also updated the default lang map with mappings for sr@latin, tl_PH. We've also removed mappings for few languages that should not be used such as ar (one should use the ar_AA language team). Because our default mappings had this ar: ar-AA, ar_AA: ar-AA we were generating the same language pack twice. You will need to manually update the options to fix this -> first open the component options and clear all the content from the maping field -> click save. Once it refreshes you'll see that the options have been populated with new content -> click save again. Please also make sure that your tx config doesn't have the same mapping. Generally the rule is -> 1 mapping per unique language.