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.
Description of problem:
In our current date field, we can show enough characters to display the current date, 2012-10-09, but then we have room for ~5 more characters.
Assuming numbers take up the same amount of space, irrespective of language, having the ability to display 2012-10-09-2012 doesn't do us a whole lot of good. I'd rather we just cut ~4 characters out of the field and show the date like we currently do, but with a bit of padding on the right edge, and free up some whitespace/extra room for other languages to flex things around.
Doing this will significantly increase the whitespace we have in the middle, from ~40px to ~74px.
Version-Release number of selected component (if applicable):
subscription-manager-1.1.2-1-git
Created attachment 646452[details]
verified that the calendar date field is now 10 chars wide
Verifying Version...
[root@rhsm-accept-rhel6 ~]# rpm -q subscription-manager-gui
subscription-manager-gui-1.1.8-1.el6.x86_64
Note: Originally the calendar date field was localized and the width of the date field was 14 chars for the pleasure of viewing all localized dates. Currently the date field is no longer localized due to hardships. Therefore the 10 char wide field is now a good choice.
For reference, here is the commit to ISO8601 dates:
ea0469db2f2eea176e90f54cf3419a6fd6dc74e9
Use ISO8601 date format in allsubs tab
Previously we were using the localized date
format (ala, strftime('%s')) which is lovely,
but is more or less impossible to parse, even
by the tools that claim to (for ex, strptime('%x')).
We had worked around this in a few cases, by
falling back to en_GB localized date format,
but that was pretty much just a kluge. For
bonus fun, some of the dates would only
fail to parse on double digit months. Or for
some locales, specific months that had
unicode char's the date parser didn't like.
In addition, strptime() is especially broken
on python 2.4 available on RHEL 5 and earlier.
So, enough of that. ISO8601 dates it is.
- remove locale kluge
- remove unit tests specifically for that kluge
- add test cases for widgets.DatePicker
Moving to VERIFIED
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-2013-0350.html