Re: AUDIT: r15327 - gnucash/trunk/src/gnome - Translate expenses in mortgage/loan druid. Fix #393436.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Looks good to me. Andreas Köhler schrieb: > Author: andi5 > Date: 2007-01-07 10:42:22 -0500 (Sun, 07 Jan 2007) > New Revision: 15327 > Trac: http://svn.gnucash.org/trac/changeset/15327 > > Modified: >gnucash/trunk/src/gnome/druid-loan.c > Log: >

Re: AUDIT: r15325 - gnucash/trunk/src/gnome - Actually translate "Remove Splits".

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Looks good to me as well. Thanks for spotting this one. Andreas Köhler schrieb: > Author: andi5 > Date: 2007-01-07 09:17:55 -0500 (Sun, 07 Jan 2007) > New Revision: 15325 > Trac: http://svn.gnucash.org/trac/changeset/15325 > > Modified: >gnucash/

Is anyone writing a book on GnuCash and writing Reports?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 HI I am thinking of writing a boot on gnu cash and righting reports for it. Does this seem cycrocramic (crack pot)? Has it been done? I have put out no energy into this project so If this is a BAD idea, feel free to say so. Pat - -- Patrick C. McKe

Gnucash book

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -- Patrick C. McKelvey PE (License E-45489 expires 12/31/2006) 3315 Ashwood Dr. Cincinnati, OH 45213 [EMAIL PROTECTED] GnuPG - DSA - 9b7e48b3 at pgp.mit.edu 19DC C758 DB34 4AE0 98EE 99E4 A983 6CCE 9B7E 48B3 -BEGIN PGP SIGNATURE- Version: Gn

Re: Is anyone writing a book on GnuCash and writing Reports?

Hi, I've heard of nobody working on a GnuCash book in any form, neither "how use use gnucash" nor "how to write a report". -derek Quoting Pat McKelvey <[EMAIL PROTECTED]>: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > HI > I am thinking of writing a boot on gnu cash and righting reports

Re: Slightly smarter date parsing?

Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote: >> I was putting my receipts in for the last half month or so recently >> and noticed that I had to be careful to notice the year that the >> receipts were in. When putting in 12/23 or similar, I d

Re: Slightly smarter date parsing?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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

Re: Slightly smarter date parsing?

I'd think this would need to be a preference; I might be entering future dates for budgeting purposes, for example, and wouldn't want GC "correcting" me. That's a feature I hate the most (ok, second most after clippy) in MS Word: auto"correct". I'm not annoyed by the current behaviour, FWIW. Dan

gda-dev does not compile.

Compiling the latest gda-dev failed as follows: gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../.. -I../../.. -I.. -I../.. -DLOCALE_DIR=\"/opt/gnucash-svn15330/share/locale\" -I../../../src/backend -I../../../src/engine -I../../../src/core-utils -I../../../lib/libc -I../../../lib/lib

Re: Slightly smarter date parsing?

On Sun, Jan 07, 2007 at 03:09:34PM -0800, Thomas Bushnell BSG wrote: > On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote: > > I was putting my receipts in for the last half month or so recently > > and noticed that I had to be careful to notice the year that the > > receipts were in. When putting i

Re: Slightly smarter date parsing?

The current behavior has long annoyed me too. My vote is for change. regards- Derek Atkins wrote: > Thomas Bushnell BSG <[EMAIL PROTECTED]> writes: > > >> On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote: >> >>> I was putting my receipts in for the last half month or so recently >>> and n

RE: Slightly smarter date parsing?

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. I asked on #gnucash and it was suggested that I bring it here since there may be some debate. i

Re: Slightly smarter date parsing?

On Mon, 2007-01-08 at 08:26 -0800, Andrew Sackville-West wrote: > On Sun, Jan 07, 2007 at 03:09:34PM -0800, Thomas Bushnell BSG wrote: > > On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote: > > > I was putting my receipts in for the last half month or so recently > > > and noticed that I had to be c

Re: Slightly smarter date parsing?

On Mon, Jan 08, 2007 at 06:04:12PM -0500, David Hampton wrote: > On Mon, 2007-01-08 at 08:26 -0800, Andrew Sackville-West wrote: > > On Sun, Jan 07, 2007 at 03:09:34PM -0800, Thomas Bushnell BSG wrote: > > > On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote: > > > > I was putting my receipts in for

Re: Slightly smarter date parsing?

On 1/8/07, David Hampton <[EMAIL PROTECTED]> wrote: > On Mon, 2007-01-08 at 08:26 -0800, Andrew Sackville-West wrote: > > On Sun, Jan 07, 2007 at 03:09:34PM -0800, Thomas Bushnell BSG > > me too! > > but it only crops up once a year. How long after 1/1 are > > people still entering 12/xx items? Gr

Re: Slightly smarter date parsing?

Anderw Sackville-West wrote: > me too! but it only crops up once a year. How long after 1/1 are > people still entering 12/xx items? Granted, I routinely enter 50+ > items from the previous month, so its been particularly annoying. But > I think, in terms of gnucash doing exactly what is expected,

Re: Slightly smarter date parsing?

On Mon, 8 Jan 2007 08:26:40 -0800 Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Sun, Jan 07, 2007 at 03:09:34PM -0800, Thomas Bushnell BSG wrote: > > On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote: > > > I was putting my receipts in for the last half month or so recently > > > and notice