[COMMITTED] oc_FR locale: Fix spelling of April (bug 25639)
Commit Message
From: =?UTF-8?q?Rafa=C5=82=20Lu=C5=BCy=C5=84ski?=
<digitalfreak@lingonborough.com>
Date: Mon, 6 Apr 2020 23:45:52 +0200
Subject: [PATCH] oc_FR locale: Fix spelling of April (bug 25639)
Confirmed by CLDR and a native speaker: "abril" is more often used even
if "abrial" is also correct. Both nominative (alt_mon) and genitive (mon)
cases are updated.
---
localedata/locales/oc_FR | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Comments
The question is: may I backport this fix [1] and even more important
the previous one [2] [3] to 2.31 so that the distros having their new
releases this quarter will have a chance to apply them? Carlos? Siddhesh?
Regards,
Rafal
[1] https://sourceware.org/pipermail/libc-alpha/2020-April/112592.html
[2] https://sourceware.org/pipermail/libc-alpha/2020-March/111973.html
[3] https://sourceware.org/pipermail/libc-alpha/2020-March/111974.html
7.04.2020 00:48 Rafal Luzynski via Libc-alpha <libc-alpha@sourceware.org>
wrote:
>
> The question is: may I backport this fix [1] and even more important
> the previous one [2] [3] to 2.31 so that the distros having their new
> releases this quarter will have a chance to apply them? Carlos?
> Siddhesh?
>
> Regards,
>
> Rafal
>
>
> [1] https://sourceware.org/pipermail/libc-alpha/2020-April/112592.html
> [2] https://sourceware.org/pipermail/libc-alpha/2020-March/111973.html
> [3] https://sourceware.org/pipermail/libc-alpha/2020-March/111974.html
Ping... "No" is a good answer if that's what you think.
Regards,
Rafal
On 01/05/20 01:23, Rafal Luzynski wrote:
> 7.04.2020 00:48 Rafal Luzynski via Libc-alpha <libc-alpha@sourceware.org>
> wrote:
>>
>> The question is: may I backport this fix [1] and even more important
>> the previous one [2] [3] to 2.31 so that the distros having their new
>> releases this quarter will have a chance to apply them? Carlos?
>> Siddhesh?
>>
>> Regards,
>>
>> Rafal
>>
>>
>> [1] https://sourceware.org/pipermail/libc-alpha/2020-April/112592.html
>> [2] https://sourceware.org/pipermail/libc-alpha/2020-March/111973.html
>> [3] https://sourceware.org/pipermail/libc-alpha/2020-March/111974.html
>
> Ping... "No" is a good answer if that's what you think.
Yes you may backport the fix. In general you may backport fixes without
asking for consensus as long as it does not have an ABI impact and it
fixes a bug.
Siddhesh
1.05.2020 05:06 Siddhesh Poyarekar <siddhesh@sourceware.org> wrote:
> [...]
> Yes you may backport the fix.
Thank you, backported to 2.31 now.
> In general you may backport fixes without
> asking for consensus as long as it does not have an ABI impact and it
> fixes a bug.
I thought the policy was different and actually some of my patches had
been rejected from the backport. Maybe the policy had been different
in the past.
Indeed, it fixes a bug (typo) and does not have an ABI impact and does
not increase the string width.
Regards,
Rafal
* Rafal Luzynski via Libc-alpha:
> 1.05.2020 05:06 Siddhesh Poyarekar <siddhesh@sourceware.org> wrote:
>> [...]
>> Yes you may backport the fix.
>
> Thank you, backported to 2.31 now.
>
>> In general you may backport fixes without
>> asking for consensus as long as it does not have an ABI impact and it
>> fixes a bug.
>
> I thought the policy was different and actually some of my patches had
> been rejected from the backport. Maybe the policy had been different
> in the past.
The policy has not changed.
Some locale updates are more risky, with collation updates that may
cause silent corruption of database indices at the extreme end. I
don't think we should do those in a stable release.
@@ -110,7 +110,7 @@ abmon "gen.";/
alt_mon "geni<U00E8>r";/
"febri<U00E8>r";/
"mar<U00E7>";/
- "abrial";/
+ "abril";/
"mai";/
"junh";/
"julhet";/
@@ -122,7 +122,7 @@ alt_mon "geni<U00E8>r";/
mon "de geni<U00E8>r";/
"de febri<U00E8>r";/
"de mar<U00E7>";/
- "d<U2019>abrial";/
+ "d<U2019>abril";/
"de mai";/
"de junh";/
"de julhet";/