Date: Tue, 21 Jun 2016 20:05:33 +0300 From: Andrey Chernov <ache@freebsd.org> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r302026 - in head: share/monetdef share/msgdef share/numericdef share/timedef tools/tools/locale/tools Message-ID: <70f03752-4b50-caf6-48ad-68b41bfd00d2@freebsd.org> In-Reply-To: <20160621071249.coi44qjecd67hz32@ivaldir.etoilebsd.net> References: <201606200645.u5K6jhBr081752@repo.freebsd.org> <0de854da-5914-901a-3d15-41429808ace1@freebsd.org> <20160621071249.coi44qjecd67hz32@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fv6ApRKvpDalSXWfDDgDX2ndMFP9FOFod Content-Type: multipart/mixed; boundary="QwxPkHatLbWuUn544k9i7Bud9wtJLPbfi" From: Andrey Chernov <ache@freebsd.org> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Message-ID: <70f03752-4b50-caf6-48ad-68b41bfd00d2@freebsd.org> Subject: Re: svn commit: r302026 - in head: share/monetdef share/msgdef share/numericdef share/timedef tools/tools/locale/tools References: <201606200645.u5K6jhBr081752@repo.freebsd.org> <0de854da-5914-901a-3d15-41429808ace1@freebsd.org> <20160621071249.coi44qjecd67hz32@ivaldir.etoilebsd.net> In-Reply-To: <20160621071249.coi44qjecd67hz32@ivaldir.etoilebsd.net> --QwxPkHatLbWuUn544k9i7Bud9wtJLPbfi Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 21.06.2016 10:12, Baptiste Daroussin wrote: > On Mon, Jun 20, 2016 at 10:14:04PM +0300, Andrey Chernov wrote: >> On 20.06.2016 9:45, Baptiste Daroussin wrote: >>> Author: bapt >>> Date: Mon Jun 20 06:45:42 2016 >>> New Revision: 302026 >>> URL: https://svnweb.freebsd.org/changeset/base/302026 >>> >>> Log: >>> Fix generation of locales with multiple variants >> >> Thanx. >> Just want to note, even if we stay with RFC 5646 language tags instead= >> of ISO 639 ones with @modifier (per ISO 15897), current tags are >> incorrect because have "_" instead of "-" which makes parsing harder, >> because "_" is territory separator and someone may not expect several >> "_" exists. Per RFC 5646 we need names like >> sr-Cyrl_RS.UTF-8.src >> and not >> sr_Cyrl_RS.UTF-8.src >> > I have a patch that create the @modifier version meaning > for instance: > sr_RS.UTF-8@[modifier] >=20 > it also adds an alias sr_RS.UTF-8 which is the cyrillic version (follow= ing the > what has been done on linux for this locale) >=20 > I am seeking for your opinion on a policy to handle the locales with va= riants. > I am hesitating between 2 options: > 1/ Provide all locales that may have modifier: >=20 > - for sr_RS: > sr_RS.UTF-8@cyrillic > sr_RS.UTF-8@latin >=20 > and sr_RS.UTF-8 (which is actually the same as sr_RS.UTF-8@cyrillic) >=20 > - for zh_TW > zh_TW.UTF-8@hant > and zh_TW.UTF-8 (which is an alias on zh_TW.UTF-8@hant) >=20 > - for mn_MN > mn_MN.UTF-8@cyrillic > mn_MN.UTF-8 (which is an alias on mn_MN.UTF-8@cyrillic) >=20 > 2/ Only provide the @version for the ones for which we have an ambiguit= y >=20 > - for sr_RS: > sr_RS.UTF-8@latin > sr_RS.UTF-8 (would be the cyrillic one) >=20 > - for zh_TW > zh_TW.UTF-8 (no @modifier version) >=20 > - for mn_MN > mn_MN.UTF-8 (no @modifier version) >=20 >=20 > I do like the first (more explicit and simpler to do with our code whil= e still > compatible with the second). Linux only does the second. >=20 > But I understand the first can be confusing for languages with (for now= ) only > one variant supported like users asking themselves: > which one should I choose: mn_MN.UTF-8 or mn_MN.UTF-8@cyrillic? > They might not now they are actually the same >=20 > Any opinion? Since @modifier exists just to avoid ambiguity, we definitely don't need to add f.e. @cyrillic to every cyrillic-based locale and @latin to every latin-based one, and so on. Difference between no @modifier and some @modifier is enough to avoid ambiguity too, so I vote for Linux way. GNU libintl drops any @modifier in any case and use its own default encoding it tries to convert to user one later. --QwxPkHatLbWuUn544k9i7Bud9wtJLPbfi-- --fv6ApRKvpDalSXWfDDgDX2ndMFP9FOFod Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJXaXPdAAoJEKUckv0MjfbKqB8H/RrOZA/ObnY5rfP1I58BL7Qt DZFZTuyBwA5VPiBpF+b42p/x2RNpwurmDLHG+gCGg6Va+wAVok3U9sUsQ2SUVIOi rRfallmQ9jCjekyhfpgN1tEgMI+8FGeICXe3UquZ047icl1h0eawnF4zoUuEOwun HuA2JSFQ0mR2th7MNM8v14tKJ1EH1m4rEXqcYO+auK1ag+ftbPG2vMk3HbvjSroi 914cdlehR4dZK9GUkU1Hz/YWjBTq/YBdlJOUHoVoPBmj/1NIsVVY9QMoFKX7sI8j nKzKJgPKDFYtLAw4NyV2v7O0xA+XWY21nsHPeRGwWPgmCVE34wSUjBH51moISDw= =mzVM -----END PGP SIGNATURE----- --fv6ApRKvpDalSXWfDDgDX2ndMFP9FOFod--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70f03752-4b50-caf6-48ad-68b41bfd00d2>