Currently ">Tools >Language Settings >Langauge >Default Language For
* 250 options for Western;
* 8 options for CJKV;
* 44 options for Complex Text Layout;
A couple of points to note:
* Of the 100 most spoken languages, 39 do not have a LibO locale;
* ISO 639-1 lists 189 languages;
* Ethnologue (2017) claims 7,097 living languages;
* Wycliffe Global Alliance claims that the Bible has been translated, in
whole, or in part, into 3,350 languages. (^1)
* 401 languages have more than 1,000,000 speakers;
* 1,762 languages have less than 1,000 speakers;
* ISO 15924 lists 248 writing systems;
* Microsoft Windows 8 is available in 109 language locales;
* Microsoft 8.1 enables one to input text in more than 7,000 languages
* Microsoft Office 2016 (Windows) claims 91 languages for the UI;
* Microsoft Offive for the Mac 27 languages for the UI;
* Microsoft Office Online claims 97 langauges for the UI;
All of which is a round about way of saying that real soon now, more
locales will need to be added to LibO.
For all of the above data, I have a document that shows LibO compares.
(Would this document be worth throwing in with LibO Documentation?)
The theoretical worst case scenario, is that LibO has to support every
possible combination of language, writing system, and country, for a
theoretical grand total of 440,014,000 listings.
FWIW, I place the absolute upper boundary of listings at 4,000,000.
The practical upper limit is 16,000 listings;
The likely upper limit is 9,000 listings;
The most probable upper limit is 4,000 listings;
IOW, with barely 300 listings, LibO has a long way to go.
However, even at 300 listings, the UI, is, shall we say, awkward.
I've noted a couple of grumbles in the forums, and mailing lists, about
"too many listings", "why another listing, when nobody uses the ones
that are currently available", etc.
The challenge is to design the language-selection UI that can select
language, country, writing system, that remains as simple to use with
300 listings, as it does with 4,000,000 listings.
I've drawn, and rejected half a dozen possibilites, on the grounds that
they are not as simple to use, as the current method.
^1: For all practical purposes, this figure equals the number of
langauges that have been reduced to a writing system.
Am 27-Dec-18 um 06:59 schrieb jonathon:
> ... The challenge is to design the language-selection UI that can
> select language, country, writing system, that remains as simple to
> use with 300 listings, as it does with 4,000,000 listings.
Some tickets from BZ: "Always list last three used languages" , "UI
Language list not sorted" , "Move Default language entry to the top
of language and user interface list" , "Make 'Default: <Name>' entry
in language settings lists not sorted, possibly separated from other
items" . There are likely many more.
We are proud of supporting as many languages as possible, also the less
frequently spoken, and should not favor one over the others for some
arbitrary reason (number of users, number of speakers, most complete
So my take is to provide autocomplete features with the dropdown (AFAIK
it's called ComboBox then). Right now you click on the expander and have
to scroll through the huge list. That would change into you enter the
search term like "Deut" (...sch) in my case and the list expands when
the number of items is reasonable small (let's say <20). Then you click
on the actual item. This behavior is well-known and easy to discover.
On Friday, 2019-01-04 10:36:57 +0100, Heiko Tietze wrote:
> So my take is to provide autocomplete features with the dropdown (AFAIK it's
> called ComboBox then). Right now you click on the expander and have to
> scroll through the huge list.
That's not true. You can activate the list (by the expander) and then
type the start of the language name and as you type the selection moves
to matching entries. This with the old and the new widgets, there was
just a short time frame with the new widgets where the completion didn't
work. The old implementation had the advantage though that typing in the
edit field of the combobox also advanced to matching entries and
displayed them in the edit field, that seems to be gone.