On Sunday 28 August 2005 11:39 pm, Thomas Bushnell BSG wrote: > Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > > Attention please to http://bugzilla.gnome.org/show_bug.cgi?id=170444 > > (Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312109). > > > > I believe I have the fix. The problem is that many locales have date > > string formats longer than eleven characters.
As part of my work on QOF to handle UTC times and to output those to XML in an xml-compatible form (that validates with a schema), I'd already upped the length to 31: #define MAX_DATE_LENGTH 31 gnc-date.h I've no problem making it 40 - do some formats produce strings between 31 and 40? > Lol. This is stunning. The bug is freakier than I thought at first. > It is a bug that gnucash only allows 11 character long dates G2 has been using 31 for about 6 months now. > But gnucash correctly fills in "11" for the MAX argument to strftime, > and never passes it a buffer shorter than that. Upping > MAX_DATE_LENGTH doesn't fix anything. The problem indeed has nothing > to do with buffer lengths. Well, at least the 11 limit has been fixed. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
pgpBxKA5RpgpI.pgp
Description: PGP signature
_______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
