[#11924] - [RFC] Normalization and new metadata for languages (international_name and native_name)
- Closed
- 5 Sep 2016
- Medium
- Build: staging
- # 11924
- Diff
- andrepereiradasilva:new-metadata-for-languages
- Success continuous-integration/drone the build was successful Details
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Summary of Changes
While dealing with #11867 it became clear to me the names of the languages extensions/packages need some normallization.
If you install all language packages you will notice there isn't really little normallization of this, which difficults any automation process needed to done in the core and also IMHO is not good for UX.
A language have a lot of xml files, and all of this have names for the language, example for english:
- Installation Language MetaFile
- Site Language MetaFile
- Site Language Manifest
- Admin Language MetaFile
- Admin Language Manifest
- Language Package Manifest
So this proposal is to start normalizing all language packages (starting with english en-GB here).
Keep in mind this is an effort to normalize and only a proposal, and i could be missign something, any contribution to this discussion is appreciated.
So what are the changes proposed?
What i propose is the following:
All xx-XX.xml and install.xml xml
nameelement would get the same value, i.e. the language in english following the language code, in english would be English (en-GB).The installation/site/admin xx-XX.xml
metadata->nameelement would get the same value as above.The pkg_xx-XX.xml
nameelement would get the same value as above + Language Package, in english would be English (en-GB) Language Package.-
Two new metadata elements would be created in the xx-XX.xml files:
native_nameandinternational_name-
international_name: in english would be English (United Kingdom) -
native_name: in english would be English (United Kingdom)
-
So we would have 3 names for each language, some examples:
| Name | International Name | Native Name |
|---|---|---|
| English (en-GB) | English (United Kingdom) | English (United Kingdom) |
| Portuguese (pt-PT) | Portuguese (Portugal) | Português Europeu |
| Portuguese (pt-BR) | Portuguese (Brazilian) | Português do Brasil |
| Arabic (ar-AA) | Arabic (Unitag) | اللغة العربية بالكود الموحد |
| German (de-DE) | German (Germany) | don't know native german :) |
| German (de-CH) | German (Switzerland) | don't know native german :) |
| Sinhala (si-LK) | Sinhala (Sri Lanka) | සිංහල (ශ්රී ලංකාව) |
Testing Instructions
Code review.
Documentation Changes Required
The documentation on creating language packages would need to be updated.
Translation Coordenation Team would have to agree and transmit this normalization and new metada to language package translation coordenation.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Language & Strings Administration Installation |
| Labels |
Added:
?
?
|
||
| Labels |
Added:
?
|
||
@jeckodevelopment those are just examples
And BTW i'm portuguese ;)
This would be a new feature.
Some thoughts:
The name used in the install.xml is never used and is indifferent. No absolute need to normalize.
The name used in the Installation xx-XX.xml can include the native translation because it is easier for people speaking only this language to choose it in the dropdown when installing. This is why we have for example:
<name>Arabic Unitag (العربية الموحدة)</name> or <name>Bulgarian (Български)</name> or <name>Japanese 日本語 (Japan)</name> or <name>Khmer ភាសាខ្មែរ (Cambodia)</name>
This was decided already some time ago and I see no reason to change this.
I do not understand what you mean with international_name. I think adding the pure native name in the future is a good idea.
Note: the German is Deutsch
from
INSTL_DEFAULTLANGUAGE_NATIVE_LANGUAGE_NAME="Deutsch"
The name used in the install.xml is never used and is indifferent. No absolute need to normalize.
IMO makes life easier for everyone if normalized.
The name used in the Installation xx-XX.xml can include the native translation because it is easier for people speaking only this language to choose it in the dropdown when installing. This is why we have for example:
That can easily be done by programming with the metadata i proposed and mainting the consistency of the metadata files across clients (installation/site/admin),
I do not understand what you mean with international_name. I think adding the pure native name in the future is a good idea.
The international name is a long name without language tags, more easy to understand for regular users. This could be used as title for the content languages when autommaticly created.
That can easily be done by programming with the metadata i proposed and mainting the consistency of the metadata files across clients (installation/site/admin),
So, you would get 2 lines in the dropdown for each language? Otherwise I don't see how...
for instance, $metadata->international_name . ' | ' . $metadata->native_name or something like this
I am not convinced, except for the native name which can indeed be used in the future.
after dealing with the PR to create the content languages to me is clear that this should be normalized.
made a gif (click it to view in full screen) to show the lack of consistency in the languages. Just installed all languages and went to the backend languages menus
for instance, $metadata->international_name . ' | ' . $metadata->native_name or something like this
As I said, all languages would now be displayed with 2 lines in Joomla installation: here just changed for en-GB
This does not make sense imho.
closing as it seems no interrest in this
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-09-05 21:35:27 |
| Closed_By | ⇒ | andrepereiradasilva |
should it be "Portugal" instead of "European" ?
If i remember well it should be "Schweiz"