Say more about the CLDR as source of QLocale's data

Say where it comes from and that it's a linguistic pragmatist.
That is, it records de facto usage, not de jure.

Prompted by a discussion around the discrepancy between what we use
for Spanish number formats and what the Royal Spanish Academy of
Language mandates, taken up on the CLDR mailing list.

https://groups.google.com/a/unicode.org/g/cldr-users/c/BbpPgNeihOU/m/HPzB-jl8CgAJ
See also: https://unicode-org.atlassian.net/browse/CLDR-15508

Task-number: QTBUG-127966
Change-Id: I487ab9bd9c348a26ab5e63381014202a5be2dd14
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
This commit is contained in:
Edward Welbourne 2024-08-13 10:09:13 +02:00
parent 4a44a8a8a5
commit 287f3097f2

View File

@ -51,8 +51,24 @@
\note For the current keyboard input locale take a look at
QInputMethod::locale().
\section1 Appropriateness of the formats
QLocale's data is based on Common Locale Data Repository v45.
This data is published by The Unicode Consortium, who aim to follow
customary, common use by writers of each language, in each script, in each
territory for which data is given. This may in some cases differ from what
is recognized as official, depending on how widely that official standard is
followed in practice.
For example, although the relevant international standard (from the BIPM)
mandates a thin non-breaking space as the separator between groups of digits
in numbers, when they are split up to aid readability, and many
jurisdictions have adopted this as their official standard for the
formatting of numbers, many locales in fact have a traditional way of
formatting numbers with punctuators separating groups of digits. CLDR, and
thus QLocale, follows this common usage rather than the official standard.
\section1 Matching combinations of language, script and territory
QLocale has data, derived from CLDR, for many combinations of language,