https://bugs.documentfoundation.org/show_bug.cgi?id=161744
--- Comment #13 from V Stuart Foote <[email protected]> --- (In reply to Heiko Tietze from comment #5) > We list four types of Cyrillic numbers for Bulgarian, Russian, Serbian, and > Ukrainian. While I support adding Mongolian, the list is hard to use right > now. Does our VCL layout even support non-Cyrillic Mongolian? > How about two entries for letters, one "A,B,C (Latin)" the other "A,B,C > (Localized)" which then becomes either Russian Cyrillic or Mongolian, > depending on the chosen language. In reality the Soviet era adoption of Cyrillic based alphabets was quite broad: https://en.wikipedia.org/wiki/Cyrillic_alphabets so not just here. So for any of the Cyrillic using locales we support with an i18n CLDR record we could/should hard code both numeric and alphabetic sequence for each locale, expanding the drop list. Otherwise IIUC, Between Mongolia and the Inner Mongolia (the Autonomous Region of the PRC) we have two different alphabets and multiple 'dialects' of Mongolian. And only the state of Mongolia officially uses the Cyrillic forms. But that is being supplemented now, with Mongolia *officially* adopting the traditional forms (so somehow adopting use of Unicode 1800-18AF) and preparing documents in both renderings mandated by Jan 2025. > > Or, to keep the list more clean, add an option below "[ ] Localize". Regards doing a "[ ] Localize"--wouldn't the CLDR details be found in the LC_COLLATION and LC_INDEX record? Here we don't maintain a mn_MN or mn_CN locale, just the mn_Cyrl_MN.xml. Though I noticed we don't update select CLDR automatically and the locale/lang codes are odd reusing generic 'qlt' "a locale language" for many in addition to the country codes. Meaning we can currently automate? Also, Unicode is struggling with the "Mongolian text model" https://www.unicode.org/reports/tr54/ https://www.unicode.org/mwg/mwg3docs/mwg3-2UnicodeV12MongolianBlockR.pdf Think Eike is going to need to comment/participate here on how/if this could be automated and what would need be done in our i18n CLDR data stores. -- You are receiving this mail because: You are the assignee for the bug.
