directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <>
Subject [jira] [Commented] (DIRSTUDIO-845) "Friendly" time not displaying correctly
Date Fri, 09 Nov 2012 07:58:12 GMT


Pierre-Arnaud Marcelot commented on DIRSTUDIO-845:

Hi Joel,

Let's be clear.
If the picture in your example has been taken on November 8th 14:42:05 in Australia, it's
Generalized Time value *can't* be 20121108144205Z.
It's not as simple as appending a 'Z' at the end of the time string. By doing so, it is locating
this time in the UTC (GMT+0) timezone.

The whole point of the decorated (friendly) value is to help the user deal with timezones
conversion. That's why we get the timezone used on the local machine and convert the time
to something relative to that.

Can you confirm that the software you're using to insert the date in the directory server
is actually taking the current time in the Australian timezone (using "DateTime.Now()" as
you indicated) and appending a "Z" at the end of this value?

If this is the case, the date isn't correct anymore unfortunately?
> "Friendly" time not displaying correctly
> ----------------------------------------
>                 Key: DIRSTUDIO-845
>                 URL:
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 1.5.3, 2.0.0-M3
>         Environment: WinXP SP2, Apache Directory Studio 1.5.3, 2.0 M3, multiple machines.
>            Reporter: Joel
>            Priority: Minor
> We have a piece of photocapture software that takes a photo and adds it to our eDirectory
tree along with the date the photo was taken. The format it uses to store the date in is the
following: 20121108144205Z (yyyyddmmhhmm??Z). Apache takes this date and converts it to a
more user friendly version but this date is off by +11 hours as below.
> 9/11/2012 1:42:05 (20121108144205Z)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message