Jump to:
| Project: | Internationalization |
| Version: | master |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Jose Reyero |
| Status: | closed (fixed) |
Issue Summary
It's obvious I've started using the i18n module :)
And at the same time I'm creating an Icelandic language translation.
Having translated some of the interface already, I stumbled on something I think needs further thinking.
The Language block gets translated to the selected language at any given time.
Given that I'm Icelandic, the default language of my web is Icelandic, but, since the rest of the world doesn't understand my language, I'm providing English material as well.
But I'm not so sure that the people of the world knows that enska is the Icelandic word for English. Which brings me to the point of this issue:
Maybe the language block should be inverse translated, that is, when I've got the Icelandic version of my web selected, the English link shouldn't show enska but English a version those who need the link understand - and when I've got the English version of my web selected, the Icelandic link should show íslenska rather than Icelandic, also showing a version of the link understandable to those who need it.
Comments
#1
Yes, you are right, current behaviour is not the best one.
It's not that easy to fix as language names are taken from locale module, and the language name provided by that module is the English name of the language, so we need some coordination between both modules.
Right now, I can think of a workaround, that is removing that t() from the language name so it won't go through the localization system. But we need to provide to the locale module the right -local- name for the language where it reads 'English name'
I will do it for the CVS version for now
#2
Won't fix this for 4.5, as it may break translations for existing sites..
I'll change version to cvs
#3
Setting to active, as you seem to want to work on this later...
#4
I'd say it's fixed, though it's kind of a workaround, as you need to define the language in the locale module with the native name... It wont be translated anymore.
I will have to update the documentation..
#5