https://bugs.documentfoundation.org/show_bug.cgi?id=145853
--- Comment #8 from Eike Rathke <[email protected]> --- (In reply to Yaroslav Serhieiev from comment #7) > So, is there anything you think can be improved on the LibreOffice source > code side, in regards to the third-party dictionary extensions? Or, the > other way around, is there any naming convention that an extension can > leverage to be rendered as "<unrecognized-iso-code> (Latin) > {<private-subtag>}"? I'm trying to understand the next action items from our > discussions. I don't quite get what you're asking here. Not predefined tags are rendered as I lined out, asking ICU for a display string and appending the " {language-tag}" for clarity. Whatever ICU gives there. The only thing we could do is adding yet two other tags to the predefined languages list to have proper "Slavic auxiliary (whatever)" language list entries, that almost no one will use and the list is already overpopulated. But that will need to agree on the final tag anyway, so either 'sla-Latn-x-isv' or 'art-Latn-x-interslv' or whatever. > > The first mentions Glottolog inte1263 and as IETF code art-x-interslv, so > > that should probably be art-Latn-x-interslv and art-Cyrl-x-interslv instead? > > Hmm, I don't find the ConLang Code Registry's > (https://www.kreativekorp.com/clcr/) to be the most authoritative source > here, because they nowhere on their site distinguish between constructed and > planned (semi-natural) languages here, although they might be right. Of course they are not an authoritative source, but it seems to be some agreement there in using art-x-interslv, I don't know. So using such seems better to me than sla-x-isv that no other application would understand. > I am > not sure, and this doubt made me post this question today on SO: > https://stackoverflow.com/questions/70134064/are-bcp-47-collective-language- > code-more-suitable-for-zonal-auxiliary-languages Let's see if that leads anywhere.. > Getting back to the technical side of the question, won't it be the same? > Using "art" or "sla" language code, we'll anyway (probably) be getting the > data strings from here: > > > > https://github.com/unicode-org/icu/blob/ > 49dda34fb175240a7724c7e039a270126ff7d900/icu4c/source/data/lang/en.txt Yes, but if LibreOffice defines the language list entries we can name the display strings anything we like, independent of ICU. Just that there needs to be a decision which language tag to use. (that even more applies to when using only the generated entries from the dictionary extension because once in the wild for documents it needs to stick). -- You are receiving this mail because: You are the assignee for the bug.
