https://bugs.documentfoundation.org/show_bug.cgi?id=145853
--- Comment #2 from Yaroslav Serhieiev <noomo...@gmail.com> ---
Hello, Ming Hua!
Thanks for your reply!
First, I'll address:
> And I think the biggest concern would probably be that you use "sla" now and
> it get assigned to another language by ISO later, causing incompatibility
> issues.
Not exactly. The "sla" ISO code has been already assigned – it is an umbrella
code for all the "Slavic languages".
On the other hand, it seems, your input is valid. I followed your advice, and
indeed I can see my non-standard BCP47 code at the top of the languages list,
i.e.: "✓ {{sla-Latn-x-isv}}".
Now I see it is not a blocker at all. But may I proceed with the "improvement"
part of my question, please?
Honestly, with my code, "sla-Latn-x-isv" I was hoping to see it rendered in a
list as "Slavic languages (Latin) {x-isv}".
Presumably, to satisfy this behavior, there should be two conditions met:
1) LibreOffice source code should have a mapping to interpret "sla" → "Slavic
languages" (and sla-Latn → Slavic languages (Latin), respectively)
2) The language picker rendering (populating) logic should be extended to
handle private BCP47 code extensions (x-...) in the described way: [interpret
primary code] [(interpret script if there is one)] [{print the remaining
x-extension}].
If that makes sense to the contributors as well, I could create another issue
for (2) and see if I can find anyone who can help to resolve this.
Thanks in advance for your time and hard work on LibreOffice itself!
--
You are receiving this mail because:
You are the assignee for the bug.
