Hi Wiktor, hi Tom,
in OTRS 1.1 and higher the time format is configurable in the
translation file.
[Kernel/Language/de.pm]
# date formats (%A=WeekDay;%B=LongMonth;%T=Time;%D=Day;%M=Month;%Y=Jear;)
$Self->{DateFormat} = '%D.%M.%Y %T';
$Self->{DateFormatLong} = '%A %D %B %T %Y';
$Self->{DateInputFormat} = '%D.%M.%Y - %T';
[...]
[Kernel/Language/en.pm]
$Self->{DateFormat} = '%M/%D/%Y %T';
$Self->{DateFormatLong} = '%A %B %D %T %Y';
$Self->{DateInputFormat} = '%M/%D/%Y - %T';
[...]
So it should be shown in the selected frontend language format.
Just the database time format should be "yyyy-mm-dd hh:mm:ss". And shown
is the time format from the translation file format.
Any better ideas?
-Martin
On Tue, Dec 30, 2003 at 09:34:29PM +0100, Tom Hesp wrote:
> I would vote for a configurable format. As far as I know OTRS is used in a
> lot of different countries using their own date format so it is kind of
> strange to enforce one format upon all users.
>
> Kind regards,
> Tom Hesp
>
> -----Original Message-----
> Sent: dinsdag 30 december 2003 11:30
> To: [EMAIL PROTECTED]
> Subject: [dev] Time Layout Question
>
> Hello,
>
> I noted that time is represented in very different formats across the
> OTRS. Once we have YYYY/MM/DD, the other time YYYY/DD/MM and then we
> have classical DD.MM.YYYY and so on. I think this needs some
> harmonization. What do we vote for? Configurable or not?
> My favourite (I'm not an american, so...) is DD.MM.YYYY
>
> --
> Regards,
>
> Wiktor Wodecki
>
> net mobile AG - 40470 Duesseldorf - Germany
> 923B DCF8 070C 9FDD 5E05 9AE3 E923 5A35 182C 9783
Martin Edenhofer
--
((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg
http://www.otrs.de/ :: Manage your communication!
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
