incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Holeczek (JIRA)" <>
Subject [jira] Commented: (JSPWIKI-196) Consistent date and time formats
Date Thu, 10 Apr 2008 09:38:05 GMT


Florian Holeczek commented on JSPWIKI-196:

Mhh not much time for this at the moment, sorry... Just found this one
coincidentally while browsing for l10n issues.
Maybe the original reporter wants to do this?


Urspr√ľngliche Nachricht vom 10.04.2008 um 11:23:
> Hi Florian,
> Could you break the JSPWIKI-196 up in piecese, cause there are several
> issues: new DATE plugin (may need some further elaboration), bugfixes
> on current plugins which are not yet using the user-prefs date/time
> format.
> dirk
> On Thu, Apr 10, 2008 at 10:15 AM, Florian Holeczek <> wrote:
>> This one goes to Dirk: You've modified 2.7 regarding date formats.
>>  I've seen that there has already been a discussion about this in
>>  JSPWIKI-196. Could you have a look at it?
>>  Regards,
>>   Florian

> Consistent date and time formats
> --------------------------------
>                 Key: JSPWIKI-196
>                 URL:
>             Project: JSPWiki
>          Issue Type: Improvement
>          Components: Localization
>    Affects Versions: 2.6.1
>         Environment: Any
>            Reporter: Goran Karlic
>            Priority: Trivial
> +This issue was changed to better reflect the initiated discussion+
> Focus is on:
> * How DateTimes are *stored* internally, for example as page content or metadata (comments
> * How they are *rendered* to end-users in their browsers
> {quote}
> The original issue name was:  _Date and time formats according to ISO 8601_. 
> 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
> (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.
> {quote}

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message