From: "tamuki at linet dot gr.jp" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24471] New: lzh_TW (LC_TIME): Numbers from 32 to 99 can not be represented in Chinese numeral
Date: Mon, 22 Apr 2019 03:52:00 -0000 [thread overview]
Message-ID: <bug-24471-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24471
Bug ID: 24471
Summary: lzh_TW (LC_TIME): Numbers from 32 to 99 can not be
represented in Chinese numeral
Product: glibc
Version: 2.29
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: tamuki at linet dot gr.jp
CC: libc-locales at sourceware dot org
Target Milestone: ---
In Literary Chinese locale for the Republic of China (lzh_TW), numbers
of 32 or more in year, minute, and second can not be represented in
Chinese numeral:
$ LANG=lzh_TW date -d "1931-04-01 09:00:00" +"%Oy年"
卅一年
$ LANG=lzh_TW date -d "1932-04-01 09:00:00" +"%Oy年"
32年
$ LANG=lzh_TW date -d "2019-04-22 12:31:30" +"%OH時%OM分%OS秒"
十二時卅一分卅秒
$ LANG=lzh_TW date -d "2019-04-22 12:32:30" +"%OH時%OM分%OS秒"
十二時32分卅秒
$ LANG=lzh_TW date -d "2019-04-22 12:32:31" +"%OH時%OM分%OS秒"
十二時32分卅一秒
$ LANG=lzh_TW date -d "2019-04-22 12:32:32" +"%OH時%OM分%OS秒"
十二時32分32秒
In other locales that use alt_digits, they are defined up to 99
elements. That should also be followed for lzh_TW locale.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-04-22 3:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 3:52 tamuki at linet dot gr.jp [this message]
2019-04-22 3:55 ` [Bug localedata/24471] " tamuki at linet dot gr.jp
2019-04-22 5:32 ` bluebat at member dot fsf.org
2019-04-23 0:14 ` tamuki at linet dot gr.jp
2019-04-23 5:08 ` bluebat at member dot fsf.org
2019-04-23 7:17 ` tamuki at linet dot gr.jp
2019-04-23 7:58 ` bluebat at member dot fsf.org
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-24471-716@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).