Not actually working on multi-lingual sites (at this point), however...
What I want is my 'en' 'translation' to be different from the default.
I have on one site used the localization settings to add a new 'language' (which I called en-GB), however the sole purpose was to just change the default behavior. I didn't want to provide multiple 'translations'. It does work of course, just me being a fussy perfectionist.
How are other people achieving the same thing?
Cheers, Ross.
On Fri, 2005-01-28 at 20:48 +0000, Ross Kendall wrote:
Not actually working on multi-lingual sites (at this point), however...
What I want is my 'en' 'translation' to be different from the default.
I have on one site used the localization settings to add a new 'language' (which I called en-GB), however the sole purpose was to just change the default behavior. I didn't want to provide multiple 'translations'. It does work of course, just me being a fussy perfectionist.
How are other people achieving the same thing?
A) Add the new language (en-GB). B) Check the enable box for the new language and set it as default. C) _Uncheck_ the enable box for the "provided by Drupal" translation (this makes it stop showing up on the user account edit screen). D) Translate the strings that you want to be different than the default.
Cheers, Ross.
Thanks Pontus,
That's what I was doing, and it works fine, I guess it just bothered me that I had to call it something different to 'en', as I didn't want 'en-GB' in the HTML 'language' attribute. I can hack the template to say 'en' all the time, but that is a bit annoying if I really do want to provide multiple translations.
Like I said, just me being fussy.
Pontus Ullgren wrote:
On Fri, 2005-01-28 at 20:48 +0000, Ross Kendall wrote:
Not actually working on multi-lingual sites (at this point), however...
What I want is my 'en' 'translation' to be different from the default.
I have on one site used the localization settings to add a new 'language' (which I called en-GB), however the sole purpose was to just change the default behavior. I didn't want to provide multiple 'translations'. It does work of course, just me being a fussy perfectionist.
How are other people achieving the same thing?
A) Add the new language (en-GB). B) Check the enable box for the new language and set it as default. C) _Uncheck_ the enable box for the "provided by Drupal" translation (this makes it stop showing up on the user account edit screen). D) Translate the strings that you want to be different than the default.
Cheers, Ross.
On Sat, 2005-01-29 at 00:25 +0000, Ross Kendall wrote:
Thanks Pontus,
That's what I was doing, and it works fine, I guess it just bothered me that I had to call it something different to 'en', as I didn't want 'en-GB' in the HTML 'language' attribute. I can hack the template to say 'en' all the time, but that is a bit annoying if I really do want to provide multiple translations.
I actually took a look at the code and the en translation does not allow any transformations of strings, so you need to create a second english translation and disable the default en translation.
Would be nice, however...
"The language /English/ (/en/) is already set up." (error message)
Gordon Heydon wrote:
On Sat, 2005-01-29 at 00:25 +0000, Ross Kendall wrote:
Thanks Pontus,
That's what I was doing, and it works fine, I guess it just bothered me that I had to call it something different to 'en', as I didn't want 'en-GB' in the HTML 'language' attribute. I can hack the template to say 'en' all the time, but that is a bit annoying if I really do want to provide multiple translations.
I actually took a look at the code and the en translation does not allow any transformations of strings, so you need to create a second english translation and disable the default en translation.
Ross Kendall wrote:
Thanks Pontus,
That's what I was doing, and it works fine, I guess it just bothered me that I had to call it something different to 'en', as I didn't want 'en-GB' in the HTML 'language' attribute. I can hack the template to say 'en' all the time, but that is a bit annoying if I really do want to provide multiple translations.
Like I said, just me being fussy.
You can use "en-local" or something like that. See: http://www.faqs.org/rfcs/rfc1766.html
Steven Wittens