public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: Jakub Martisko <jamartis@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH][BZ #15527] strftime_l.c: Support lowercase output
Date: Fri, 09 Dec 2016 04:08:00 -0000	[thread overview]
Message-ID: <20161209040755.GU10558@vapier.lan> (raw)
In-Reply-To: <65344612.479215.1481246089816@poczta.nazwa.pl>

[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]

On 09 Dec 2016 02:14, Rafal Luzynski wrote:
> 7.12.2016 16:39 Mike Frysinger wrote:
> > [...] might be good to get wider opinion about new
> > strftime flags though.
> 
> Now I lean a little against this change. As I wrote before,
> I'd love to see a flag to change the first letter to uppercase
> (or to titlecase, if that's more appropriate). A flag to change
> whole string to lowercase would be a workaround for this problem
> if we also converted all months and weekdays names to the
> titlecase in all languages, like in English now.

i don't think changing the locale data or forcing titlecase everywhere
makes sense.  the data is already in the standard format that users
expect for their locale.  having a flag to support that seems like a
good way to get developers to naively enforce their own expectations
onto users.  "my language writes things like 'Dec', therefore every
language out there must use titlecase".

forcing to all uppercase or lowercase seems a bit more reasonable in
certain outputs (everything is upper/lower case beyond the date).

> But in that case, do you guys think that converting to lowercase
> is useful if all letters are either lowercase already or should
> be always as they are now? Can you explain why would any application
> ever need the lowercase which should be provided by a format flag
> rather than converting programmatically? It seems to be useful
> only if some locales want to convert some data to lowercase and
> they don't have it lowercase out of the box.

we already have a flag to force it to uppercase.  makes sense to have
a flag to do the opposite.  your arguments here apply to the uppercase
flag too.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-12-09  4:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15  8:54 Jakub Martisko
2016-06-15  9:09 ` Andreas Schwab
2016-06-29  7:55   ` Jakub Martisko
2016-12-06 23:20     ` Mike Frysinger
2016-12-07 10:18       ` Jakub Martisko
2016-12-07 15:39         ` Mike Frysinger
2016-12-09  1:14           ` Rafal Luzynski
2016-12-09  4:08             ` Mike Frysinger [this message]
2016-12-09 11:00               ` Rafal Luzynski
2016-12-09 16:20                 ` Mike Frysinger
2016-12-09 22:37                   ` Rafal Luzynski
2017-04-07 23:29                     ` Rafal Luzynski
2016-11-29 12:21 ` Jakub Martisko
2016-11-29 12:42   ` Jakub Martisko
2016-12-01 23:29     ` Rafal Luzynski
2016-12-05 14:55       ` Jakub Martisko
2016-12-06 22:47         ` Rafal Luzynski
2016-12-06 23:21 ` Mike Frysinger
  -- strict thread matches above, loose matches on Subject: below --
2016-05-12 15:26 [PATCH][BZ 15527] " Jakub Martisko

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=20161209040755.GU10558@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=digitalfreak@lingonborough.com \
    --cc=jamartis@redhat.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).