Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Jun 2016 09:12:49 +0200
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        Andrey Chernov <ache@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:  <20160621071249.coi44qjecd67hz32@ivaldir.etoilebsd.net>
In-Reply-To: <0de854da-5914-901a-3d15-41429808ace1@freebsd.org>
References:  <201606200645.u5K6jhBr081752@repo.freebsd.org> <0de854da-5914-901a-3d15-41429808ace1@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--24bdtrqibjdslz6r
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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
> >=20
> > Log:
> >   Fix generation of locales with multiple variants
>=20
> 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
>=20
I have a patch that create the @modifier version meaning
for instance:
sr_RS.UTF-8@[modifier]

it also adds an alias sr_RS.UTF-8 which is the cyrillic version (following =
the
what has been done on linux for this locale)

I am seeking for your opinion on a policy to handle the locales with varian=
ts.
I am hesitating between 2 options:
1/ Provide all locales that may have modifier:

- for sr_RS:
sr_RS.UTF-8@cyrillic
sr_RS.UTF-8@latin

and sr_RS.UTF-8 (which is actually the same as sr_RS.UTF-8@cyrillic)

- for zh_TW
zh_TW.UTF-8@hant
 and zh_TW.UTF-8 (which is an alias on zh_TW.UTF-8@hant)

- for mn_MN
mn_MN.UTF-8@cyrillic
mn_MN.UTF-8 (which is an alias on mn_MN.UTF-8@cyrillic)

2/ Only provide the @version for the ones for which we have an ambiguity

- for sr_RS:
sr_RS.UTF-8@latin
sr_RS.UTF-8 (would be the cyrillic one)

- for zh_TW
zh_TW.UTF-8 (no @modifier version)

- for mn_MN
mn_MN.UTF-8 (no @modifier version)


I do like the first (more explicit and simpler to do with our code while st=
ill
compatible with the second). Linux only does the second.

But I understand the first can be confusing for languages with (for now) on=
ly
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

Any opinion?

Best regards
Bapt

--24bdtrqibjdslz6r
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXaOhZAAoJEGOJi9zxtz5ahX8QALqUh+/49ShThYKudtNNhvxT
C3ROihA1eGSweACBAjJ5iprhZtgg0RmM4Jzdzwv+gsTkt92FrShRgdjcErxKUxRo
qDwByMlA1b5+ZIETDYcURXkzYHDuMBXjWH58a+antv/6QChY+xPPdKiBuxafMJfy
L+/SBKr8eb/WekHF1ZHhZmD6QuGbXtvWIiUPRmAjNlwSCMskn53EfOHOUB+FhD9y
0JSg4/mEVSeurh4aylP/+gEROHybH7X5UNzJMVKf2lYOFBs/b59jluLZhCsQn+Z4
HiI00svmPSisrAQI4ylQsFfxpgkJYvrmwCuxgsdmgiPdYoPJlGsEy9DJBw3bNrcE
o16/4iSso4686X/gHqXtAdSFz/nfEJqRFVMalBoB8F/HNk22PWvXTHk9gnepfZvw
Ht6OWxt+l51BKAntlYeYoOoH6XUjLOOUF8tEo4QxxtAjsTSlMHp2SXQxQb512S6C
Ay+l8J2UhK1Efi10hEJHEmnkHDr4DF2CcAu7g57/Q8meNUuLFcsbjnpxwYph7Fcu
4nYYzQoOQhz2k0fRT3X+YvzR4PqXZVfZArBK+I4BqrREIS8Casbbsr2wCP7z4dxx
lemfRAb454pgA22QEVJ1dEWRcbw/Yvwgjfd+0Y12kGoGDbJ+2gFEnitpCt6VkPOa
rG8xlmii1lSMxZB1Deoc
=VDVy
-----END PGP SIGNATURE-----

--24bdtrqibjdslz6r--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160621071249.coi44qjecd67hz32>