This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Build-Translate-Plan
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Languages to build

Languages for the first build

We do not need to support or test all OOo languages with our first build. But in order to ensure that it works correct we should include a localization test as well:

Suggestion : build 5 or 6 locales representing 90% of the downloads ? Add de, fr, it, and you are done.

Languages for developer milstones

When it comes to frequently published developer milestones we should think about which languages to include to avoid to build the full set of languages to save build time and mirror space.

The past

The following table shows the set of languages that were chosen in the old OOo project:



Arabic (ar)

to test the behavior of these characters and test RTL writing

English (en-US)

master language

French (fr)

due to historical reasons and to see long strings are fitting to the UI

German (de)

due to historical reasons, there were the most testers, too

Japanese (ja)

to test the behavior of CJK characters and test BIDI writing

Russian (ru)

to test the behavior of Cyrillic characters

The future

For a new list we first have to look for volunteers before choosing the appropriate languages:



English (en-US)

master language

Chinese (zh-CN)

this language has the most users

Khmer (km)

to test the behavior of complex text layout (CTL) scripts

  • No labels