https://bugs.documentfoundation.org/show_bug.cgi?id=126157
Eike Rathke <er...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|6.4.0.0.alpha1+ |unspecified
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0 |1
Assignee|libreoffice-b...@lists.free |er...@redhat.com
|desktop.org |
--- Comment #4 from Eike Rathke <er...@redhat.com> ---
We already have a ko-KP mapping with user defined MS-LCID 0x8012.
(@Julien: there is the internal tool i18nlangtag/source/isolang/langid.pl to
find out about known language/locale assignments, mappings and support in
relevant places, the invocation could be, for example,
SRC_ROOT=$(pwd) ./i18nlangtag/source/isolang/langid.pl ko-KP
or invoke without arguments to get help).
Just we do not have an UI entry for the language list as there is no UI
translation and no locale data file or any language tools using it.
(In reply to DaeHyun Sung from comment #2)
> Microsoft products already reserved Korean language code, "ko-KP".
> 3. Language tag: "ko-KP"
> Location (or type): North Korea
> Language ID: "0x1000"
No, they don't. LCID 0x1000 isn't an actual locale code, it's some "do it
yourself, we don't care" code. See
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/926e694f-1797-4418-a922-343d1c5e91a6
(and maybe
http://archives.miloush.net/michkap/archive/2015/03/04/8770668856267196302.html)
LCID 0x1000 specifically is not suitable for document interchange as any
content attributed by that may be treated completely arbitrary, depending on
what the machine the document is processed on thinks 0x1000 might be or not.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
