[
https://issues.apache.org/jira/browse/JSPWIKI-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571514#action_12571514
]
Goran Karlic commented on JSPWIKI-196:
--------------------------------------
When using user preferences / browser locale to resolve DateTime formats can
result in different formats appearing in comments / pages. This could be solved
by introducing a new "DateTime format property", which seems a good compromise
to me.
Do you know about any "hard-coded" format strings used in JSPWiki where access
to this new property would not be possible / undesirable?
Do you think ISO8601 is a good default setting for this new property?
Do you think ISO8601 is a good default setting for all template properties?
Janne: ISO8601 can be seen as an internationaly achieved compromise on this
issue; I would even say: "It seems accepted in the scientific comunity, which
currently best represents the human elite, where elite is defined as the upper
quantile of the gaussian distribution of the average fitness function."
> Date and time format accoding to ISO 8601
> -----------------------------------------
>
> Key: JSPWIKI-196
> URL: https://issues.apache.org/jira/browse/JSPWIKI-196
> Project: JSPWiki
> Issue Type: Improvement
> Components: Localization
> Affects Versions: 2.6.1
> Environment: Any
> Reporter: Goran Karlic
> Priority: Trivial
>
> We have multiple occurences of hard-coded or context-unaware DateTime to
> String conversions (page properties, JSPs, templates).
> My proposal is to rely on an international standard instead of using an
> invented default. The current international standard is ISO 8601 (s.
> Wikipedia). My further proposal is to show time with the precision to the
> second, as the SI unit system defines the second as the basic unit of time.
> Furthermore "GMT" is replaced by "UTC" and they might differ up to a second
> (s. Wikipedia).
> I think this will make unlocalized strings more transparent to the users and
> easier to decode correctly (consider 02/03/08 - is it in the future or in the
> past - or might it even be the current time?!).
> Following this proposal java format strings allowed for above cases would be:
> (1) Simple date: "yyyy-MM-dd" ("The daily mail for 2008-02-20 was sent")
> (2) Date and time
> (2.1) Explicit time context: "yyyy-MM-dd hh:mm:ssZ" ("User gkarlic made this
> at 2008-02-20 22:38:10+0100")
> (2.2) Implicit time context: "yyyy-MM-dd hh:mm:ss" ("This server lives on
> CET, here it is 2008-02-20 22:38:10")
> Where (2.1) would be used for strings that might emerge from different
> time-zones.
> If others agree with this proposal, I would gladly make the required changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
