Bug 1326348 - [RFE] PT-BR language date formant in horizon dashboard shows up as yyyy-mm-dd, should be dd-mm-yyyy
Summary: [RFE] PT-BR language date formant in horizon dashboard shows up as yyyy-mm-d...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Upstream M1
: 12.0 (Pike)
Assignee: Jason E. Rist
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks: 1442136
TreeView+ depends on / blocked
 
Reported: 2016-04-12 13:33 UTC by Jeremy
Modified: 2019-10-10 11:50 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-20 12:23:20 UTC
Target Upstream Version:


Attachments (Terms of Use)
screen shot (154.67 KB, image/png)
2016-04-13 13:17 UTC, Jeremy
no flags Details

Description Jeremy 2016-04-12 13:33:34 UTC
Description of problem:
PT-BR language date formant in horizon dashboard shows up as  yyyy-mm-dd, should be dd-mm-yyyy

Version-Release number of selected component (if applicable):
python-django-horizon-2015.1.0-11.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1.Change language to pt-br in horizon settings
2. notice date format
3.

Actual results:
yyyy-mm-dd

Expected results:
dd-mm-yyyy

Additional info:

Comment 1 Itxaka 2016-04-13 10:29:59 UTC
Where are you seeing the date in the wrong format? In project -> overview?

Comment 2 Jeremy 2016-04-13 13:17:25 UTC
Created attachment 1146850 [details]
screen shot

This is where the customer is seeing the date .

Comment 3 Jeremy 2016-04-13 13:19:07 UTC
The package is actually python-django-horizon-2015.1.2-4.el7ost.noarch . sorry for the confusion.

Comment 4 Itxaka 2016-04-13 14:31:31 UTC
Jeremy,

unfortunately this is a design decision as the format needs to be know beforehand in order to parse the date properly. Its hardcoded in that format, no matter what language is chosen.

A change to this will need a change upstream, and probably a big one, so this would be a RFE instead of a bug.

Comment 5 Jeremy 2016-04-14 13:19:40 UTC
Itxaka, 

Thanks for the update, can we make this an RFE?

Comment 8 Jason E. Rist 2016-09-21 15:22:12 UTC
Is this something feasible by Friday 23rd Sept?

Comment 9 Radomir Dopieralski 2016-09-21 15:36:51 UTC
I don't think it's feasible. The date format used is ISO 8601, which is an international standard. As far as I know, usage of dash as a separator is restricted to this particular format, so dd-mm-yyyy would actually violate the ISO standard. A proper format would be probably dd.mm.yyyy or dd/mm/yyyy, however, as far as I know, Horizon currently has no way of changing the date/currency/number formatting depending on the locale. It would need to be added -- first a blueprint proposed, then a solution discussed upstream, and finally implemented.

Comment 11 Beth White 2017-04-20 12:23:20 UTC
The overview panels where this issue is being seen are being re-worked this cycle to use angularjs rather than django. This may well clean up the date formatting because of the way translation works as we can see on other new panels in horizon. If not, however, following upstream discussion, the community will unfortunately not support changing the overal format to dd-mm-yyyy as that causes confusion for the Americans and yyyy-mm-dd is the most universally accepted.


Note You need to log in before you can comment on or make changes to this bug.