From: "felixonmars at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24293] Missing Minguo calendar support for TW locales
Date: Fri, 15 Mar 2019 16:05:00 -0000 [thread overview]
Message-ID: <bug-24293-716-7zyFZ4yC8H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24293-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24293
--- Comment #9 from Felix Yan <felixonmars at gmail dot com> ---
(In reply to Rafal Luzynski from comment #8)
> (In reply to Felix Yan from comment #7)
> > If so I'll submit a patch for ja_JP too.
>
> ja_JP wants the zero padding and that's why it has been introduced in bug
> 23758. That means, ja_JP does not want the patch you suggest. Also please
> read their arguments, maybe you will agree not to remove the zero padding in
> *_TW either.
I see. They want the zero padding for fixed width text, but this is not the
case for Minguo calendar as far as I see. It's already three digits now (108,
just over 100), so I believe it doesn't make sense to pad to 2 digits.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-03-15 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 16:55 [Bug localedata/24293] New: " felixonmars at gmail dot com
2019-03-07 7:47 ` [Bug localedata/24293] " bluebat at member dot fsf.org
2019-03-15 7:11 ` bluebat at member dot fsf.org
2019-03-15 9:13 ` cvs-commit at gcc dot gnu.org
2019-03-15 9:26 ` digitalfreak at lingonborough dot com
2019-03-15 9:56 ` bluebat at member dot fsf.org
2019-03-15 10:20 ` felixonmars at gmail dot com
2019-03-15 10:39 ` felixonmars at gmail dot com
2019-03-15 11:39 ` digitalfreak at lingonborough dot com
2019-03-15 16:05 ` felixonmars at gmail dot com [this message]
2019-03-15 20:32 ` digitalfreak at lingonborough dot com
2019-03-17 1:11 ` bluebat at member dot fsf.org
2019-04-02 7:50 ` cvs-commit at gcc dot gnu.org
2019-04-02 8:56 ` bluebat at member dot fsf.org
2019-04-05 20:45 ` digitalfreak at lingonborough dot com
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=bug-24293-716-7zyFZ4yC8H@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).