From: Wei-Lun Chao <bluebat@member.fsf.org>
To: TAMUKI Shoichi <tamuki@linet.gr.jp>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] localedata: Updates for Taiwanese locales [BZ #24409]
Date: Fri, 19 Nov 2021 22:47:45 +0800 [thread overview]
Message-ID: <CAP1CgNKWAGi2cBm1Y6JTU-Zy+CCqgPmYr+ZMWKfB_gxP3ddcEQ@mail.gmail.com> (raw)
In-Reply-To: <202105161000.AA00005@tamuki.linet.gr.jp>
Dear Shoichi,
Thanks for your explanation.
I'll drop this part of patch.
TAMUKI Shoichi <tamuki@linet.gr.jp> 於 2021年5月16日 週日 下午6:04寫道:
>
> Hello Wei-Lun-san,
>
> From: Wei-Lun Chao <bluebat@member.fsf.org>
> Subject: Re: [PATCH v2] localedata: Updates for Taiwanese locales [BZ #24409]
> Date: Thu, 13 May 2021 11:53:38 +0800
>
> > > > Rationale:
> > > > * Header cleanup: make the header of localedata files consistent
> > > > * Remove space (abmon): remove the extra prefix space in abmon 1~9
> > >
> > > Why are you trying to remove the extra prefix space in abmon 1..9?
> > > By fixing the display width of abbreviated month names (%b) in the
> > > same way as "Jan", "Feb", "Mar", ..., it has the effect of making the
> > > display width constant, such as system log.
> > > I don't think we should remove the leading space in abmon 1..9.
> >
> > Without this patch, "date +%b" will output with a leading space for month 1..9.
> > And the day number makes the display width inconstant already.
> > So I think single space would be a better separator.
>
> The elements defined in (ab)mon and (ab)day in the current *_TW locale
> are summarized in the attached file mon+day.png. In each locale, the
> display widths of mon (%B) and abday (%A) can change, while the
> display widths of abmon (%b) and abday (%a) are constant.
>
> Date and time notations such as logs and form lists may sometimes be
> in RFC2822 (%a, %d %b %Y %T %z) or ctime (%a %b %d %T %Z %Y) format
> with local locales.
>
> With this patch, these display widths will change in *_TW locale,
> even though the display width of each conversion specification that
> makes up them is intended to be constant. Please see the attached
> file ctime.png.
>
> Regards,
> TAMUKI Shoichi
next prev parent reply other threads:[~2021-11-19 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 5:38 Wei-Lun Chao
2021-05-07 21:23 ` Carlos O'Donell
2021-05-10 3:07 ` Wei-Lun Chao
2021-05-11 11:15 ` TAMUKI Shoichi
2021-05-13 3:53 ` Wei-Lun Chao
2021-05-16 21:46 ` TAMUKI Shoichi
[not found] ` <202105161000.AA00005@tamuki.linet.gr.jp>
2021-11-19 14:47 ` Wei-Lun Chao [this message]
2021-05-11 12:41 ` TAMUKI Shoichi
2021-05-13 5:10 ` Wei-Lun Chao
2021-05-16 21:46 ` TAMUKI Shoichi
[not found] ` <202105161001.AA00006@tamuki.linet.gr.jp>
2021-11-19 14:48 ` Wei-Lun Chao
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=CAP1CgNKWAGi2cBm1Y6JTU-Zy+CCqgPmYr+ZMWKfB_gxP3ddcEQ@mail.gmail.com \
--to=bluebat@member.fsf.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=tamuki@linet.gr.jp \
/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).