From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 88605 invoked by alias); 9 Dec 2016 04:08:01 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 88565 invoked by uid 89); 9 Dec 2016 04:08:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=lean, rafal, 7122016, strftime X-HELO: smtp.gentoo.org Date: Fri, 09 Dec 2016 04:08:00 -0000 From: Mike Frysinger To: Rafal Luzynski Cc: Jakub Martisko , libc-alpha@sourceware.org Subject: Re: [PATCH][BZ #15527] strftime_l.c: Support lowercase output Message-ID: <20161209040755.GU10558@vapier.lan> Mail-Followup-To: Rafal Luzynski , Jakub Martisko , libc-alpha@sourceware.org References: <576117B9.5080105@redhat.com> <57737EE8.8070706@redhat.com> <20161206232035.GH10558@vapier.lan> <5847E1D6.5040509@redhat.com> <20161207153904.GL10558@vapier.lan> <65344612.479215.1481246089816@poczta.nazwa.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bxF9Dep5HzwGj9mC" Content-Disposition: inline In-Reply-To: <65344612.479215.1481246089816@poczta.nazwa.pl> X-SW-Source: 2016-12/txt/msg00306.txt.bz2 --bxF9Dep5HzwGj9mC Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1673 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. >=20 > 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 --bxF9Dep5HzwGj9mC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYSi4bAAoJEEFjO5/oN/WBatEP/2xjov/uPxlsLtc9vsM5Fwjs ZbLkxp/E+VBQnBWvteuFNP3W5QteTbOeuJMDXYwLlvTLq4+9HqQ+RPn8BT7Kn21+ Ku191chbiww3YN3EFQ3ufNkorpLPS1FYlnPPhZ0jLtDXYQkxIkEo/N+B5l4+t+C9 rEthEliqxBURBW998BGw8qtaqThuS7Txmc6mJrmxiPo30U6+lSRNq/wWoK+slrV4 exkNDO9CL0rlJV1ZRp1G5TBl1wdYhEYKOFrONWLxWI2uJsdFCedBWUYMbG8urSRv FCGQgJnQZILNqj1p8LTL27lc09uAmF8fcmZVEKdZEoMzKQyxOaJpBgeCuMBpRymz xssDVPIbDgTGTt7fK4dKBgddYtvKl8NAKnfkooGrjkvPM/NX6h/J1/4yhF7IVOuT 7TNbdqTgMQKCTfFYNFxgjAW+Zki1m9HVHNvk7f7TSGvJODqxP77z5ROJ6kXc8WH4 IRi3zn5sYe9tBoc3LaJPhGGEy8jWv2gDG2dNEM1aUfgof0fZa8KRhwM3TEw/hsSL ktmSjUVndz78CRMzFmyCUnVqH64b3sDran+jpBZVFNVI530oHmiY3pvmtmc9eIwK mrfH2NEF1D5KoZjH61gMlQZsJKJuz99F1jlwnT4IweU1bKgk1IUWJA3iihma15OW iV5JI7UuMn6S+uE24jiQ =k9BT -----END PGP SIGNATURE----- --bxF9Dep5HzwGj9mC--