Bug 1247777

Summary:	fix date-time rendering to use a pre-defined format that will fit all locales
Product:	[Retired] oVirt	Reporter:	Einav Cohen <ecohen>
Component:	ovirt-engine-webadmin	Assignee:	Alexander Wels <awels>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6	CC:	bugs, ecohen, gklein, lsurette, mgoldboi, rbalakri, yeylon, ykaul
Target Milestone:	---
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ux
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-29 11:42:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	UX	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Einav Cohen 2015-07-28 20:43:25 UTC

right now, we are using two hard-coded formats that we defined for rendering date-time values for Japanese, and for non-Japanese locales:

- "yyyy-MM-dd, HH:mm" for Japanese.

- "yyyy-MMM-dd, HH:mm" for all other locales. 

we should not write and maintain our own logic for manipulating date-time formats per locale - we should use a predefined date-time format that will take care of the manipulation for us. 

following Alexander's suggestion in https://gerrit.ovirt.org/#/c/42875/: I recommend going over all pre-defined date-time formats in [1], looking for the one that renders "yyyy-MMM-dd, HH:mm" (or something very close to it) in the 'en-US' locale, and go with that format for all locales - and, IIUC, the format will adjust itself properly for every locale. 

[1] http://www.gwtproject.org/javadoc/latest/com/google/gwt/i18n/client/DateTimeFormat.PredefinedFormat.html

Comment 1 Einav Cohen 2015-07-29 11:42:47 UTC


*** This bug has been marked as a duplicate of bug 1247776 ***