-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Normalization and new metadata for languages (international_name and native_name) #11924
[RFC] Normalization and new metadata for languages (international_name and native_name) #11924
Conversation
should it be "Portugal" instead of "European" ?
If i remember well it should be "Schweiz" |
@jeckodevelopment those are just examples And BTW i'm portuguese ;) |
This would be a new feature. 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: I do not understand what you mean with Note: the German is |
IMO makes life easier for everyone if normalized.
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),
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. |
So, you would get 2 lines in the dropdown for each language? Otherwise I don't see how... |
for instance, |
I am not convinced, except for the native name which can indeed be used in the future. |
closing as it seems no interrest in this |
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:
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:
name
element would get the same value, i.e. the language in english following the language code, in english would be English (en-GB).metadata
->name
element would get the same value as above.name
element would get the same value as above + Language Package, in english would be English (en-GB) Language Package.native_name
andinternational_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:
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.