hi
i would like this gettext to be checked up against the gettext of iso/iec 30112,
which is a full iso/iec standard. i would like that they dont contradict
eachother.
also the i18n of the posix standard should be checked vs 30112, to ensure they
are compatible.
30112 is to some extend followed
please also consider iso 30112, which is a full iso standard,
and written in posix style. it was taken from glibc, after glibc took it from
the iso 14652,
it has a number of categories in eccess of the posix oncs, including lc_paper.
also note that for turkish a 'small i with dot' uppercases to
what is the syncronisation plan between ieee, tog and sc22 ?
keld
On Fri, May 14, 2021 at 11:47:20AM +0100, Andrew Josey via austin-group-l at
The Open Group wrote:
> hi all,
>
> I'm pleased to announce the availability of the second draft of the 202x
> revision of the standard.
> This draft
what is the passcode
keld
iso 30112 has a 10646 i18n locale which is implemented in glibc, and which
should be used.
keld
On Sun, Dec 13, 2020 at 04:35:08AM +, Thorsten Glaser via austin-group-l at
The Open Group wrote:
> Martijn Dekker dixit:
>
> > Datapoint: AT ksh93 has a C.UTF-8 locale built in which it
On Fri, May 18, 2018 at 01:35:03PM -0500, Eric Blake wrote:
> On 05/18/2018 12:24 PM, Wheeler, David A wrote:
> >This conversation seems strange; many locales use digits other than 0-9 to
> >represent numbers.
> >
> >The Eastern Arabic, Perso-Arabic variant, and Urdu variant all have
> >digits,
On Sun, Nov 26, 2017 at 02:09:21AM +, Danny Niu wrote:
>
>
> On 26 Nov 2017, at 3:53 AM, k...@keldix.com<mailto:k...@keldix.com> wrote:
>
> On Wed, Nov 22, 2017 at 05:43:51PM +, Stephane Chazelas wrote:
> 2017-11-22 16:27:15 +0100, Martijn Dekker:
> Op 22-1
