[grisbi-bugs] [Grisbi-0.6.0 0000765]: Problem with entering dates
bugtracker at grisbi.org
bugtracker at grisbi.org
Fri Dec 4 07:15:28 CET 2009
A NOTE has been added to this issue.
======================================================================
http://grisbi.tuxfamily.org/mantis/view.php?id=765
======================================================================
Reported By: kapil
Assigned To:
======================================================================
Project: Grisbi-0.6.0
Issue ID: 765
Category: Main
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Plateforme: Windows
OS: Windows
Version OS: XP SP 2
Unstable Impact: Yes
Version GTK:
======================================================================
Date Submitted: 12-03-2009 08:25 UTC
Last Modified: 12-04-2009 06:15 UTC
======================================================================
Summary: Problem with entering dates
Description:
I recently upgraded from 0.59 to 0.6.0 beta 3.
I noticed that the way data field is handled has changed.
The date format is fixed to MM/DD/YYYY and there is some automatic
conversion. Eg. do the following:
1. Goto transaction/schedule form
2. In the date field, enter 3/12/2009 [as in March 12th 2009]
3. Tab out. Notice that the field automatically gets converted to
12/3/2009 [as in 3rd Dec 2009]
Is there no way to enter a transaction for 12th March now?
The same issue was observed in the date fields of the new archive feature.
======================================================================
----------------------------------------------------------------------
guneeyoufix - 12-03-09 11:52
----------------------------------------------------------------------
The development team is 100% french, and sometimes, we tend to forget about
other cultures that have other ways to deal with dates and numbers. Please
excuse us for that.
We'll look into it ASAP.
----------------------------------------------------------------------
pbiava - 12-04-09 06:15
----------------------------------------------------------------------
The cause of this bug is a localization problem with Windows. we hope to
resolve this problem quickly
Issue History
Date Modified Username Field Change
======================================================================
12-03-09 08:25 kapil New Issue
12-03-09 08:25 kapil Plateforme => Windows
12-03-09 08:25 kapil OS => Windows
12-03-09 08:25 kapil Version OS => XP SP 2
12-03-09 08:25 kapil Unstable Impact => Yes
12-03-09 11:52 guneeyoufix Note Added: 0001388
12-03-09 11:52 guneeyoufix Status new => acknowledged
12-04-09 06:15 pbiava Note Added: 0001390
======================================================================
More information about the bugsreports
mailing list