Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index


Hi Jwtiyar,

------------------ Original ------------------
From:  "Jwtiyar ali";<jwtiyar@gmail.com>;
Send time: Sunday, Aug 16, 2020 10:02 PM
Subject:  Re: [libreoffice-l10n] Adding ckb to locale setting and win langpack

For locale data we already have in CLDR and glibc. How i can use these to
create new one to LO?

Like Baurzhan said, LO has its own collection of locale specification files:

On Sun, Aug 16, 2020, 11:08 Baurzhan Muftakhidinov <baurthefirst@gmail.com>
wrote:

For Format -> Locale setting, you probably should add ckb version to

https://cgit.freedesktop.org/libreoffice/core/tree/i18npool/source/localedata/data

See bug 127011 (https://bugs.documentfoundation.org/show_bug.cgi?id=127011)
as an example.

 Or LO doesn't import from gnu or cldr?

As LO is cross-platform software, it's probably hard to find anything to rely on for
all three supported platforms (Windows, Linux and macOS), and therefore maintaining
its own locale database is a necessary evil.

Hope this helps,
Ming
-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.