Note: This ticket was resolved by adding the page and linking to it from the coverageLevels.txt file.
With seed merged into common in v43, it’s critical that clients make use of coverageLevels.txt to choose their desired available locales. in for example a locale was newly encountered because it wasn’t filtered out by coverageLevels.txt.
add docs (spec?) concerning coverageLevels.txt
add link to docs in the header of the file
make sure it’s prominent in the download page
Some notes/questions
should root be included?
Presumably sublocales are included but not cross script? So mn covers mn_MN but not mn_Mong
I think we should note that presence of a locale (i.e. basic or higher) is somewhat of the equivalent of its inclusion in the common directory previously.
100% Done
Activity
Show:
Mark Davis
February 27, 2023 at 11:52 PM
Can you file a ticket to include sr_Latn in the charts?
Steven R. Loomis
February 27, 2023 at 11:05 PM
(edited)
Sounds like it probably should use the source (sr_Cyrl) coverage level.
We could make regenerating coverageLevels be part of the algorithmic update process.
Mark Davis
February 27, 2023 at 11:01 PM
Ah, we don’t include sr_Latn because it is algorithmically derived from sr (it is one of the few cases where the respective alphabets are nicely defined). And during the development process the sr_Latn always lags until we run that algorithm).
However, we could reverse that if it makes it easier for clients; it’s a very simple change.
(BTW, Steven, I modified the language in Sites — if you look it over I can ‘Publish’.)
Steven R. Loomis
February 27, 2023 at 10:46 PM
I’m not sure. ?
Naoto Sato
February 27, 2023 at 10:39 PM
I was trying to recreate the same list as of v42 (IIUC, common/seed mix starts from v43). Using this chart from v42 ( ) by choosing common locales, I could almost do it, but one locale sr-Latn seems missing. Why is the locale not listed in common in that chart?
Note: This ticket was resolved by adding the page and linking to it from the coverageLevels.txt file.
With seed merged into common in v43, it’s critical that clients make use of
coverageLevels.txtto choose their desired available locales. in for example a locale was newly encountered because it wasn’t filtered out by coverageLevels.txt.add docs (spec?) concerning coverageLevels.txt
add link to docs in the header of the file
make sure it’s prominent in the download page
Some notes/questions
should
rootbe included?Presumably sublocales are included but not cross script? So
mncoversmn_MNbut notmn_MongI think we should note that presence of a locale (i.e.
basicor higher) is somewhat of the equivalent of its inclusion in thecommondirectory previously.