[grisbi-bugs] [Grisbi 0001935]: In .gsb file / Financial_year, dates do not comply with General / Date_format
Grisbi Bug Tracker
bugtracker at grisbi.org
Mer 10 Avr 20:12:13 CEST 2019
The following issue has been CLOSED
======================================================================
http://www.grisbi.org/bugsreports/view.php?id=1935
======================================================================
Reported By: ebo
Assigned To: LudovicRousseau
======================================================================
Project: Grisbi
Issue ID: 1935
Category: Main
Reproducibility: have not tried
Severity: minor
Priority: normal
Status: closed
OS: Ubuntu
Unstable Impact: No
Version OS:
Version GTK:
Resolution: no change required
Fixed in Version:
======================================================================
Date Submitted: 2019-04-08 00:10 CEST
Last Modified: 2019-04-10 20:12 CEST
======================================================================
Summary: In .gsb file / Financial_year, dates do not comply
with General / Date_format
Description:
I my `.gsb` file I have specified:
```
<?xml version="1.0"?>
<Grisbi>
<General
File_version="1.2.1"
Grisbi_version="1.2.0"
…
Date_format="%d/%m/%Y"
```
However, later in the file, my financial years entry are specified as following:
```
<Financial_year Nb="1" Na="2017" Bdte="01/01/2017" Edte="12/31/2017" Sho="1" />
```
I.e., it uses the `%m/%d/%Y` date format instead.
I think it would be better, should all dates comply to the `Date_format`
specified in the `General` field.
======================================================================
----------------------------------------------------------------------
(0004953) ebo (reporter) - 2019-04-08 00:12
http://www.grisbi.org/bugsreports/view.php?id=1935#c4953
----------------------------------------------------------------------
The issue is the same in `Reconcile` fields
----------------------------------------------------------------------
(0004954) ebo (reporter) - 2019-04-08 00:15
http://www.grisbi.org/bugsreports/view.php?id=1935#c4954
----------------------------------------------------------------------
ok, my bad… I've just realised that _all_ date fields are using the `%m/%d/%Y`
date format in the `.gsb` file.
? can close the issue… however, the sensible thing to do would be to use the
ISO format instead (-;
(mandatory xkcd: https://xkcd.com/1179/)
----------------------------------------------------------------------
(0004959) LudovicRousseau (developer) - 2019-04-10 13:17
http://www.grisbi.org/bugsreports/view.php?id=1935#c4959
----------------------------------------------------------------------
Why do you want to read the .gsb file directly?
----------------------------------------------------------------------
(0004960) ebo (reporter) - 2019-04-10 13:27
http://www.grisbi.org/bugsreports/view.php?id=1935#c4960
----------------------------------------------------------------------
yes, I'm designing my own "data viz" project (i.e. creating graphs of my
finances using plot.ly/dash) based on Grisbi. (I'll send you the link to the
repo once the project is somehow mature.)
For that, I'm parsing the .gsb file, and then need to cast the relevant strings
as timestamps.
Anyway, the most important thing is to be consistent within the .gsb file
(what's the case now).
Using the ISO (sensible) format instead of the US (wicked) one would be a (not
so opinionated) plus.
----------------------------------------------------------------------
(0004961) LudovicRousseau (developer) - 2019-04-10 18:48
http://www.grisbi.org/bugsreports/view.php?id=1935#c4961
----------------------------------------------------------------------
Maybe you should export from Grisbi and use a QIF or CSV format.
I don't think the .gsb format is documented and/or supported. I propose to close
this issue.
----------------------------------------------------------------------
(0004962) ebo (reporter) - 2019-04-10 19:57
http://www.grisbi.org/bugsreports/view.php?id=1935#c4962
----------------------------------------------------------------------
Thanks, I'll give it a thought.
Of course, you can close the issue.
Issue History
Date Modified Username Field Change
======================================================================
2019-04-08 00:10 ebo New Issue
2019-04-08 00:12 ebo Note Added: 0004953
2019-04-08 00:15 ebo Note Added: 0004954
2019-04-10 13:17 LudovicRousseauNote Added: 0004959
2019-04-10 13:27 ebo Note Added: 0004960
2019-04-10 18:48 LudovicRousseauNote Added: 0004961
2019-04-10 19:57 ebo Note Added: 0004962
2019-04-10 20:12 LudovicRousseauAssigned To => LudovicRousseau
2019-04-10 20:12 LudovicRousseauStatus new => closed
2019-04-10 20:12 LudovicRousseauResolution open => no change
required
======================================================================
Plus d'informations sur la liste de diffusion bugsreports