[Fwd: Re: Tax Report - TXF Export Bug fix]

Richard -Gilligan- Uschold uschold@cs.ucf.edu
Tue, 16 Jan 2001 01:16:10 +0000


OK, here it is, against gnucash-1-4-branch

Gilligan

-------- Original Message --------
Subject: Re: Tax Report - TXF Export Bug fix
Date: Sun, 14 Jan 2001 22:28:31 -0800
From: Dave Peticolas <dave@krondo.com>
To: Richard -Gilligan- Uschold <uschold@cs.ucf.edu>

Richard -Gilligan- Uschold writes:
> This is a multi-part message in MIME format.
> --------------AFDF6C6545947A19B4391FE1
> Content-Type: multipart/alternative;
>  boundary="------------D824FFAAE916198BD24E0B26"
> 
> 
> --------------D824FFAAE916198BD24E0B26
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> The TXF import routines in TurboTax 2000 were changed from the 1999
> version.  These changes made it barf on the TXF file exported by
> gnucash.  TurboTax 2000 claims that the file is not a TXF file.
> 
> I must admit that is partly my fault for not including redundant
> information and apparent comments that TurboTax 1999 and TaxCut 1999
> didn't look at or complain weren't there.
> 
> This patch includes the "tax - TXF documentation update" I submitted on
> Jan 4, 2000, for which I have not received an acknowledgment that it was
> included in the cvs tree.  The message for this patch is below:

Hi Richard, sorry I didn't reply to that (I assumed you were subscribed
to gnucash-patches and were receiving the cvs update emails). Anyway, I
put your patch into the stable tree. I tried putting it into the devel
tree, but there were errors -- I figured you were going to create a
separate patch for the devel tree.

Could you resend the stable patch wrt the latest stable tree?
You can check it out using the 'gnucash-1-4-branch' tag.

thanks,
dave