The native language name should be shown in the description.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | i18n-DRUPAL-6--1_i18ntaxonomy_trans_desc.patch | 1.04 KB | dboulet |
| i18n-DRUPAL-6--1_i18ntaxonomy_native_desc.patch | 1.04 KB | dboulet |
The native language name should be shown in the description.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | i18n-DRUPAL-6--1_i18ntaxonomy_trans_desc.patch | 1.04 KB | dboulet |
| i18n-DRUPAL-6--1_i18ntaxonomy_native_desc.patch | 1.04 KB | dboulet |
Comments
Comment #1
dboulet commentedJust realized that the last patch doesn't make sense, the language name should instead be displayed in the current language.
What is the proper way to do this? Can we wrap
language_default('name')in thet()function?Comment #2
dboulet commentedComment #3
hass commentedlanguage_default('name') is not t'ified by core on "admin/settings/language/overview" and i18n on "de/node/11/translate"!? Therefore I give this a won't fix.
Comment #4
hass commentedSetting back to CNW... maybe the native name makes sense... but I'm not sure why it shouldn't.
Comment #5
dboulet commentedI see the point brought up in #3, but I think that this case is different since the language name is inserted into a sentence. If this sentence is translated into another language, the inserted language name remains in English. In French, for example, this gives the equivalent of the awkward sentence:
"This is a localizable vocabulary, so only terms in Français are allowed here."
To me, it would make more sense to translate the language name to give the sentence:
"This is a localizable vocabulary, so only terms in French are allowed here."
Comment #6
jose reyero commented#1303518: Clean up the issue tracker. Close old issues without follow up.