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.
Break date formatting? Quite the contrary, it will fix date formatting.
When our application does the equivalent of
date +%d.%b.%Y
and gets spaces in the output, then I'm pretty sure almost everybody would agree the output is incorrect. There should be no spaces there.
The only case I can imagine where things would break is if an application writes dates with abbreviated months in some kind of table in a context with a fixed-width font, and the application makes the assumption that all short versions of month names are of equal width. That table would not line up.
But that assumption the application makes is incorrect. It is incorrect in the sense that no standard says it should be that way. And it is incorrect in the sense that several locales don't look that way, Greek, French, Welsh, and Thai to take a few examples.
Any such application, if there is any, needs to be fixed. It should not be a reason to include spaces in the names of months in the locale definition. The names of the months do not contain spaces.
As discussed with Andreas Schwab and Marko Myllynen, this needs to go through the Finnish National Localization Steering Group as to decide whether these trailing spaces are necessary then upstream glibc if they approve of the change. As part of the group, Marko will raise that point and update this Bugzilla with the result. This is likely to take several months.
> As part of the group, Marko will raise that point and update this Bugzilla with
> the result. This is likely to take several months.
I've now filed an upstream report which, among other things, proposes to drop the trailing spaces and thus to follow other locales like Greek and French:
http://sourceware.org/bugzilla/show_bug.cgi?id=12962
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