Strange behaviour of eng-GB and eng-US

Previous topic

Setup & design

Next topic

Author	Message
Heiner Wurbs	Thursday 28 September 2006 3:50:17 am Hi, I found a very strange behaviour concerning the language codes: In my site.ini I have the following: [RegionalSettings] Locale=eng-GB ContentObjectLocale=eng-GB SiteLanguageList[]=eng-GB TextTranslation=enabled [ContentSettings] TranslationList=eng-GB To use this {"salutation"\|i18n( 'mycontent/texts' )} , the system should search for a share/translations/eng-GB/translation.ts file. But there is nothing like this. Even the system looks neither in the eng-US nor in the untranslated. If I create a eng-GB directory and cop the translation.ts file, then it is working. My question is now, how does this eng-GB is working ? Regards Heiner
Claudia Kosny	Thursday 28 September 2006 12:14:49 pm Hello Heiner eng-GB is thought to be the default language - all the text pieces used in the templates are in eng-GB and then translated into the target language using the i18n operator. That's why there is no eng-GB translation file by default. And if I read the code in i18n.php correctly the text translation is disabled if there is no file for the language or the fallback languages (if any). I am not sure why you think that the eng-US file should be checked - none of the settings in your site.ini suggests so. The untranslated file is, as far as I know. only there to make creating new translations easier. Greetings from Luxembourg Claudia

Author

Message

Heiner Wurbs

Thursday 28 September 2006 3:50:17 am

Hi,

I found a very strange behaviour concerning the language codes:

In my site.ini I have the following:

[RegionalSettings]
Locale=eng-GB
ContentObjectLocale=eng-GB
SiteLanguageList[]=eng-GB
TextTranslation=enabled

[ContentSettings]
TranslationList=eng-GB

To use this

{"salutation"|i18n( 'mycontent/texts' )}

, the system should search for a share/translations/eng-GB/translation.ts file. But there is nothing like this.

Even the system looks neither in the eng-US nor in the untranslated. If I create a eng-GB directory and cop the translation.ts file, then it is working.

My question is now, how does this eng-GB is working ?

Regards
Heiner

Claudia Kosny

Thursday 28 September 2006 12:14:49 pm

Hello Heiner

eng-GB is thought to be the default language - all the text pieces used in the templates are in eng-GB and then translated into the target language using the i18n operator. That's why there is no eng-GB translation file by default. And if I read the code in i18n.php correctly the text translation is disabled if there is no file for the language or the fallback languages (if any).

I am not sure why you think that the eng-US file should be checked - none of the settings in your site.ini suggests so. The untranslated file is, as far as I know. only there to make creating new translations easier.

Greetings from Luxembourg

Claudia