This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 0/1] ru_UA locale: use copy "ru_RU" in LC_TIME (bug 25044)
- From: Mikhail Gribanov <mikhail dot gribanov at gmail dot com>
- To: Rafal Luzynski <digitalfreak at lingonborough dot com>
- Cc: libc-alpha at sourceware dot org, Keld Simonsen <keld at keldix dot com>
- Date: Tue, 26 Nov 2019 10:12:07 +0200
- Subject: Re: [PATCH 0/1] ru_UA locale: use copy "ru_RU" in LC_TIME (bug 25044)
- References: <1668126095.858583.1569961824450@poczta.nazwa.pl> <1764554794.684539.1574724583364@poczta.nazwa.pl>
As the one who reported the bug and just a citizen of Ukraine:
[1] - Correct. Does exactly what is needed (ru_UA must be identical
ru_RU excluding government differences, such as currency, phone
numbers, etc.).
>Note that there may be a misunderstanding caused by the ambiguous
>term "copy" which may mean:
My mistake. I am not too familiar with the internal structure of the
glibc and C (programming language). If there is a possibility instead
of copy-paste just write
LC_TIME
copy "ru_RU"
END LC_TIME
it will be the best solution in terms of reusing code (and will help
to avoid problems with datetime differences in the future).
вт, 26 нояб. 2019 г. в 01:29, Rafal Luzynski <digitalfreak@lingonborough.com>:
>
> Ping
>
> (also see below)
>
> 1.10.2019 22:30 Rafal Luzynski <digitalfreak@lingonborough.com> wrote:
> > Since the solution is controversial I would like to hear
> > feedback from Mikhail and/or Keld (CC). This patch does not
> > determine whether lower or uppercase is correct, just says
> > that ru_RU and ru_UA should be the same.
> >
> > Regards,
> >
> > Rafal
>
> As Keld opposed I'd like to hear at least one OK about the patch
> which was posted here: [0] [1].
>
> The defense of my patch is that:
>
> * it does not say whether the weekday names and/or month names
> should be capitalized or not,
> * it only states that in ru_UA they should be the same as in ru_RU,
> * it leaves the question of capitalization open for future changes.
>
> There were some disputes about the issue, whole thread starts
> here: [2]
>
> Note that there may be a misunderstanding caused by the ambiguous
> term "copy" which may mean:
>
> * copy and paste a piece of text using an editor,
> * use the "copy" keyword.
>
> Regards,
>
> Rafal
>
>
> [0] https://sourceware.org/ml/libc-alpha/2019-10/msg00021.html
> [1] https://sourceware.org/ml/libc-alpha/2019-10/msg00022.html
> [2] https://sourceware.org/ml/libc-alpha/2019-09/msg00480.html