From: Florian Weimer <fweimer@redhat.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH v4 06/11] Provide backward compatibility for strftime family (bug 10871).
Date: Wed, 09 Nov 2016 11:00:00 -0000 [thread overview]
Message-ID: <30c831e4-8825-75e4-c81e-7e260054efb1@redhat.com> (raw)
In-Reply-To: <238ab162-7ff7-d90e-9f95-630ac413a064@redhat.com>
On 11/07/2016 03:13 PM, Florian Weimer wrote:
> One example where this matters is German. If POSIX requires that %B
> returns the genitive case, as has been suggested, then all applications
> which currently use %B are broken because I have yet to see a
> mechanically generated German date string which actually needs the
> genitive case. In current usage, they only occur in phrases such âon
> the last Sunday of Novemberâ.
The concern expressed in the paragraph above is not relevant because
it's about month name mangling for inclusion in full date strings, and
not about declension. German does not have an issue with that, but many
Romance languages do because some of them do require such mangling in
full date strings, as explained here:
https://sourceware.org/ml/libc-alpha/2016-11/msg00321.html
To be absolutely clear, I still object to the change to %B (and MON_1
etc.) and moving the old definitions to %OB (ALTMON_1 etc.). The right
way to do this is to leave %B (MON_1 etc.) alone and add %OB (ALTMON_1
etc.) with the new mangled form. This also removes the surprising
change of behavior due to a simple recompilation of unchanged sources.
As there has been some confusion regarding past objections of mine which
were apparently worded in too a conciliatory way, I consider this a
sustained objection under the glibc consensus protocol.
Thanks,
Florian
prev parent reply other threads:[~2016-11-09 11:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 0:49 Rafal Luzynski
2016-11-04 13:40 ` Florian Weimer
2016-11-05 10:53 ` Rafal Luzynski
2016-11-07 14:13 ` Florian Weimer
2016-11-08 11:39 ` Rafal Luzynski
2016-11-09 10:49 ` Florian Weimer
2016-11-10 0:33 ` Rafal Luzynski
2016-11-10 12:41 ` Florian Weimer
2016-11-10 18:42 ` Rafal Luzynski
2016-11-10 19:19 ` Andreas Schwab
2016-11-15 1:21 ` Rafal Luzynski
2016-11-11 3:52 ` Rical Jasan
2016-11-15 1:38 ` Rafal Luzynski
2016-11-15 11:09 ` Rafal Luzynski
2016-11-16 13:06 ` Rical Jasan
2016-11-17 11:18 ` Rafal Luzynski
2016-11-18 9:22 ` Rical Jasan
2016-11-22 23:56 ` Rafal Luzynski
2016-11-09 11:00 ` Florian Weimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30c831e4-8825-75e4-c81e-7e260054efb1@redhat.com \
--to=fweimer@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).