public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "junji.morimitsu at hpe dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24162] ja_JP LC_TIME: era offset for Taisho GanNen and BC direction
Date: Thu, 07 Feb 2019 13:04:00 -0000	[thread overview]
Message-ID: <bug-24162-716-sOHzWNpUlP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24162-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24162

--- Comment #6 from junji morimitsu <junji.morimitsu at hpe dot com> ---
Hello TAMUKI-san,

Thank you very much for checking.

(In reply to TAMUKI Shoichi from comment #5)
> > 2:  The offset of Taisho Gan Nen (1912) is '2', but it should be '1'.
> >     Gan Nen means the 1st year, Taisho started on 1912-07-30.
> 
> Yes, you are right.  Probably, this typo was introduced when creating
> ja_JP localedata, but it has been overlooked so far.  I think it sould
> be corrected.

Thanks.  I hope the update can be checked in before April Fool.  :) 


> > 3:  The direction of BC is '+', but it should be '-'.  

> If you change '+' to '-', it will be as follows:
...
> $ date -d "2018 years ago" +"%EY"
> 西暦01年
> $ date -d "2019 years ago" +"%EY"
> 紀元前01年
> $ date -d "2020 years ago" +"%EY"
> 紀元前00年
> $ date -d "2021 years ago" +"%EY"
> 紀元前-1年

Very good example!  Thank you.  The offset counts are wrong at '-' direction.  
This shows there is a bug in localedef or strftime() using the 'direction'.  
'direction' is the 'era' direction, not 'offset' direction.  
'offset' count (%Ey) should be increasing from 'start_date' to the 'end_date'.  
Please check the LC_TIME definition about this.

So I understand that using '+' for BC era is a workaround for a bug.

>There is no need to change this:

I agree with you as of now.  
1st, to fix the 'direction' bug, then to use '-' for BC era, I think.
And I'm not so interested in BC era this year.  
(Temporary) I want cancel item 3:.

Thank you,
Junji

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-02-07 13:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 10:15 [Bug localedata/24162] New: " junji.morimitsu at hpe dot com
2019-02-04 10:17 ` [Bug localedata/24162] " junji.morimitsu at hpe dot com
2019-02-04 14:47 ` carlos at redhat dot com
2019-02-04 15:25 ` carlos at redhat dot com
2019-02-05 14:09 ` junji.morimitsu at hpe dot com
2019-02-06  4:29 ` carlos at redhat dot com
2019-02-07  6:17 ` tamuki at linet dot gr.jp
2019-02-07 13:04 ` junji.morimitsu at hpe dot com [this message]
2019-02-08  8:49 ` tamuki at linet dot gr.jp
2019-03-02 12:04 ` cvs-commit at gcc dot gnu.org
2019-03-18  5:53 ` tamuki at linet dot gr.jp
2019-03-22  2:01 ` cvs-commit at gcc dot gnu.org
2024-01-09 17:15 ` maiku.fabian at gmail dot com
2024-01-11 14:20 ` maiku.fabian at gmail 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-24162-716-sOHzWNpUlP@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).