problem with qif-parse.scm in trunk
David Reiser
dbreiser at earthlink.net
Mon Sep 22 23:38:36 EDT 2008
On Sep 22, 2008, at 12:42 PM, Charles Day wrote:
> On Mon, Sep 22, 2008 at 9:41 AM, Charles Day <cedayiv at gmail.com>
> wrote:
> On Mon, Sep 22, 2008 at 8:13 AM, Derek Atkins <warlord at mit.edu> wrote:
> Quoting David Reiser <dbreiser at earthlink.net>:
>
> >
> > On Sep 22, 2008, at 10:17 AM, Derek Atkins wrote:
> >
> >> David Reiser <dbreiser at earthlink.net> writes:
> >>
> >>> As it exists currently, qif-parse.scm does not work, even with the
> >>> escaped version of a3. However, if I change \xa3 to \\xa3, gnucash
> >>> will run. That looks like a escaping/quoting inconsistency among
> >>> systems. Is that any easier to solve than the base encoding
> problem?
> >>
> >> If you change it to \\xa3 then does it properly deal with the £ in
> >> the QIF?
> >>
> >>>
> >> -derek
> >
> >
> > I don't know. Is there a sample qif file I can test? What will I be
> > looking for?
>
> See http://bugzilla.gnome.org/show_bug.cgi?id=141003
>
> Doubling up the backslashes should break the fix, as then the
> backslash loses its special regex expression meaning.
>
> Sorry, wrong attachment on the previous message. I've now attached
> the correct one. -Charles
>
>
> Please see the simple QIF file attached. It contains the British
> Pound symbol in ISO 8859-1 (0xA3). This is what the QIF importer
> needs to be able to handle. Here is the output of 'od':
> $ od -c 141003a.qif
> 0000000 ! A c c o u n t \n N M y C
> r e
> 0000020 d i t C a r d \n T C C a r d
> \n
> 0000040 ^ \n ! T y p e : C C a r d \n
> D 2
> 0000060 2 / 0 9 / 2 0 0 8 \n P T e s t
> 0000100 p a y e e \n T 243 3 8 . 4 6 \n ^
> \n
> 0000120
>
> -Charles
Correct. Doubling the backslash breaks the fix.
With LANG=en_US.UTF-8, my system even complains "some characters have
been discarded" during the import when I make the .scm file UTF-8
while the qif is latin-1. (Though I haven't changed the other two
files in the changeset...).
I need that LANG setting because that's the only way to get gtkprint
to use US-letter paper parameters while printing checks. (Unless
someone wants to add a gnumeric-style default page setup to gnucash.)
Dave
--
David Reiser
dbreiser at earthlink.net
More information about the gnucash-devel
mailing list