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
Hi Wiktor, 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----- From: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org]On Behalf Of Wiktor Wodecki Sent: dinsdag 30 december 2003 11:30 To: dev@otrs.org 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 _______________________________________________ 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
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: dev@otrs.org 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!
Martin Edenhofer wrote:
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?
Yes, the date/time format should be configurable to a user, I mean each user should have their own preference of how time and date is represented in teh system Imagine an american and a Swede working on the same system but at different places in the world, the american in america, and the swede in sweden. using the same otrs somplace on the net. they both have different locales but the system locale ( as now ) defines the date/time format .Thus this is an issue which should be configurable as a user property. Regards Greger
-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: dev@otrs.org 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
Bob Smith wrote:
Martin Edenhofer wrote:
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?
Yes, the date/time format should be configurable to a user, I mean each user should have their own preference of how time and date is represented in teh system Imagine an american and a Swede working on the same system but at different places in the world, the american in america, and the swede in sweden. using the same otrs somplace on the net. they both have different locales but the system locale ( as now ) defines the date/time format .Thus this is an issue which should be configurable as a user property.
Which raises a new question:if the date/time property is a property of the user, then the language is too. Suggestion:make locale a property of the user, not the system. Regards Greger
Regards Greger
-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: dev@otrs.org 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
_______________________________________________ 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
Hi Bob, Bob Smith wrote:
Yes, the date/time format should be configurable to a user, I mean each
user
should have their own preference of how time and date is represented in teh system Imagine an american and a Swede working on the same system but at different places in the world, the american in america, and the swede in sweden. using the same otrs somplace on the net. they both have different locales but the system locale ( as now ) defines the date/time format .Thus this is an issue which should be configurable as a user property.
Which raises a new question:if the date/time property is a property of the user, then the language is too. Suggestion:make locale a property of the user, not the system.
Maybe I do not understand you correctly but the language is a property of the user (can be set in the user's Preferences screen) and hence is the date/time format as it is part of the language translation. I would expect that the Swedish agent wants to use the Swedish layout; of course if he or she want to work in the Swedish language but with an American date/time format then it becomes a different issue. Whether settings like the date/time format should be part of the language translation is of course debatable but then you get into a far more principle discussion. I think for the time being the developers made the right choice by making it part of the translation. Regards, Tom
Tom Hesp wrote: Hello tom, yes! I agree with you that it is the right desition for time being, and this issue can be debated I was just spawning ideas:-) It all depends where teh developers want to take otrs in the future, so I think the matter of locallizing could be discussed. I like the idea of otrs( it is great software), but I think it needs some refinement, but that is a different subject. Regards Greger
Hi Bob, Bob Smith wrote:
Yes, the date/time format should be configurable to a user, I mean each
user
should have their own preference of how time and date is represented in teh system Imagine an american and a Swede working on the same system but at different places in the world, the american in america, and the swede in sweden. using the same otrs somplace on the net. they both have different locales but the system locale ( as now ) defines the date/time format .Thus this is an issue which should be configurable as a user property.
Which raises a new question:if the date/time property is a property of the user, then the language is too. Suggestion:make locale a property of the user, not the system.
Maybe I do not understand you correctly but the language is a property of the user (can be set in the user's Preferences screen) and hence is the date/time format as it is part of the language translation. I would expect that the Swedish agent wants to use the Swedish layout; of course if he or she want to work in the Swedish language but with an American date/time format then it becomes a different issue. Whether settings like the date/time format should be part of the language translation is of course debatable but then you get into a far more principle discussion. I think for the time being the developers made the right choice by making it part of the translation. Regards, Tom
_______________________________________________ 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
Hi Bob, I fully agree (especially that it is great software!). Regards, Tom
On Tue, Jan 06, 2004 at 11:50:06AM +0100, Tom Hesp wrote:
I fully agree (especially that it is great software!).
Thanks! Thanks to the community. :-)
Regards, Tom
-Martin -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
On Mon, Jan 05, 2004 at 11:43:16AM +0100, Martin Edenhofer wrote:
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.
well, that's okay, but then OTRS doesn't use it across all places. I will have a look at it tomorrow and comment again :-) -- Regards, Wiktor Wodecki net mobile AG - 40470 Duesseldorf - Germany 923B DCF8 070C 9FDD 5E05 9AE3 E923 5A35 182C 9783
On Tue, Jan 06, 2004 at 06:31:04PM +0100, Wiktor Wodecki wrote:
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.
well, that's okay, but then OTRS doesn't use it across all places. I will have a look at it tomorrow and comment again :-)
That could be. But in the CVS version it should. :)
Regards,
Wiktor Wodecki
net mobile AG - 40470 Duesseldorf - Germany
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
participants (4)
-
Bob Smith -
Martin Edenhofer -
Tom Hesp -
Wiktor Wodecki