Translate default language
| Project: | Localization client |
| Version: | 6.x-1.3 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hi,
I would know if there is a plan to provide the ability to translate the default english language too.
The language standard for all drupal modules etc... is english, this module is so usefull when you have another language installed and you want to translate it, but, sometime, the "core" language translation don't fill your need.
There is the string override that allow to change the core english language, but it provide a new configuration page etc.... so, when you have i18n, localization client, locale, string override.... it begin to make a lot of confusing administration page for, finally, the same thing...
So is there a plan to update this module to allow to override all string you want (english included) by merging with string override or other... or do we have to deal with so many different administration page to translate your strings ?
thanks
zmove
#1
The recipe for your issue is to add an "English customized" language and just use that to customize the English interface whenever you want.
#2
Automatically closed -- issue fixed for two weeks with no activity.
#3
I have one of these 'english customized' languages. So the localization client shows up on this (and all other) languages offcourse. Is there a way to 'disable' the localization client for these customized languages?
#4
This solution (creating "customized english") does not seem to really work when one needs to change e.g. content type name.
1) I create new language, e.g. en-US
2) I translate content type name "uggly content type" to "beautiful content type"
Now users who have language as en-US will see e.g. "Create beautifull content type" instead of "Create uggly content type". But in order for all users to actually see this I must..
3) change default language to en-US
..and then what happens is that "uggly content type" will be actually still seen by all users, since translating defualt language is not possible. What am I missing here? There has to be way around this surely?
#5
#6
You can change content type names via the content types editing user interface. No need to create a whole new language just to change those names.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.