[
https://issues.apache.org/jira/browse/JSPWIKI-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571700#action_12571700
]
Andrew Jaquith commented on JSPWIKI-196:
----------------------------------------
Ok, that's fair comment. I'm not as knowledgeable as you are about how and when
particular JSPs do things like Comment.jsp does.
I may have erred in suggesting something a little to specific for all
situations. However, it seems that we both agree on the core issue: how to
*write* dates to some destination (into page markup, or as page metadata), and
how to *display* dates ("render internal dates"). If you modify your issue 3)
above, you'll see that it makes sense: "...for cases where we *write* the dates
directly on the page content."
I suspect where you and the Goran might disagree is the correct internal format
to use for "write" operations. I don't have an opinion, although on balance I
generally lean towards configurable options, and away from hard-coded ones.
> 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.
