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


2010.11.11 17:47, Aron Xu rašė:
On Thu, Nov 11, 2010 at 23:40, Rimas Kudelis<rq@akl.lt>  wrote:
Interestingly enough, relevant locales I see in Pootle are: zh_CN, zh_HK,
zh_TW.

Which I guess means that these are the codes that will be used at least for
3.3. ;)

Well, zh_CN and zh_SG shoul fall in Hans's category, but I've never
seen any people translating software to zh_SG, they just use zh_CN
directly.

Which is exactly why zh_Hans is more correct. ;)

zh_HK and zh_TW fall in Hant's category, which should have a solution.
If we define it like zh_HK@hant, the modifier @hant can be omitted,
because there is nothing else could make people puzzled if the
modifier does not present. (In fact @hant could be used to help put
correct files into correct language pack, :D )

I didn't say there *has* to be only one Chinese Traditional language pack. ;) It would make sense to have a "general" Hant language pack if we only had one localization, but if we have two, we can have two language packs too.

I suggest we stop this discussion here, or go off-list in order not to bother people too much... ;)

Rimas

--
E-mail to l10n+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/l10n/
All messages you send to this list will be publicly archived and cannot be deleted

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.