Slightly smarter date parsing?
stimming at tuhh.de
Mon Jan 8 09:58:51 EST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Thomas Bushnell BSG schrieb:
> On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote:
>> When putting in 12/23 or similar, I didn't get
>> December 23, 2006, but December 23, 2007. I thought this should be
>> different, so I dove into the gnucash code and changed qof_scan_date
>> slightly to choose the last year for December if the current month is
>> January. The patch is attached.
> This behavior has also always annoyed me.
For the record, this behaviour does *not* annoy me. Instead, I would
rather be annoyed by gnucash starting to (apparently) guess some year
where I would rather want a clear, precise deterministic rule, easily
described by "the current year" and that's it. I don't know whether this
might be related to different date formats in different locales, but in
German I'd rather type the date plus trailing year instead of having to
guess which year gnucash is going to guess...
In other words, I think any rule that is different from "current year"
will seem too random for too many users, IMHO.
If the majority of users here seem to think otherwise, I have no problem
with being voted down. Just don't think about making this a preference
instead of making a decision :-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v126.96.36.199 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the gnucash-devel