I don't think we should add en_GB and en_US to the list of supported languages or split the translations. We should use the convention just when making decisions on the correctness of words. Also I don't think there are so many differences that it would justify the split. Thanks, Caty On Mon, Dec 4, 2017 at 9:29 PM, Vincent Massol <[email protected]> wrote:
Thanks to all who answered.
I’ve now documented it at: * http://dev.xwiki.org/xwiki/bin/view/Community/ DevelopmentPractices#HGeneral * http://www.xwiki.org/xwiki/bin/view/Documentation/ UserGuide/Features/I18N
@Thomas: I’ve tried to add a new language by following http://l10n.xwiki.org/xwiki/bin/view/L10N/AddALanguage but I couldn’t find the page referenced by "Edit the main page of the application.”. Do you think you could add en_GB to the list? Also, I think we should mention somewhere that the en_US version is maintained in Git by the XWiki Core dev team and explain how people could contribute to the en_US version. WDYT?
Thanks -Vincent
On 4 Dec 2017, at 13:35, Vincent Massol <[email protected]> wrote:
Hi devs,
By default the xwiki core committers maintain an “en” version of all translations and the other languages are left to the community to maintain on l10n.xwiki.org
This mail is about deciding if our “en” version is “en_US” or “en_GB”.
I propose that we standardize on “en_US”. for example ApplicationResources.properties would correspond to en_US.
I also propose that we add en_GB on l10n so that the community could maintain a UK version if they want (it would fall back to en_US when there are no translations, which is a good thing).
WDYT?
Thanks -Vincent