Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #657588 +++
Description of problem:
The short version of month names in zh_CN starts with a space for January through September. But the space is not actually part of the month name, I'm sure, even if I don't know any Chinese.
Version-Release number of selected component (if applicable):
glibc-2.5-49.el5_5.7
How reproducible:
Every time
Steps to Reproduce:
1. for i in `seq 1 12` ; do LANG=zh_CN.utf8 date -d `printf 2010%02d01 $i` +%b ; done
Actual results:
1月
2月
3月
4月
5月
6月
7月
8月
9月
10月
11月
12月
Expected results:
1月
2月
3月
4月
5月
6月
7月
8月
9月
10月
11月
12月
Additional info:
I guess the reason for the spaces is to make these names have the same length in a display. And when printing, it maybe doesn't cause problems too often. But when reading a date with strptime(), it causes problems if the pattern is space separated.
Using a strptime() pattern like "%Y.%b.%d" can be made to work. It requires that the input really has a space in the month name, so "2010. 1月.26" would be accepted, while "2010.1月.26" would not. It could be surprising for a human entering the time.
If the date is space separated, it gets worse. If the pattern is e.g. "%Y %b %d" there is no way to enter a date in months other than October, November, or December. The space after %Y will match any number of spaces in the input. There will never be any space "left" to become part of the month name.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0763.html