Release 2.4.12 OFX Imports work fine in Ubuntu Linux 12.04

[David Carlson]

On 4/8/2013 4:08 PM, David Carlson wrote:
> On 4/8/2013 11:13 AM, Derek Atkins wrote:
>> David Carlson <david.carlson.417 at gmail.com> writes:
>>
>>> Subject says it all.  This is my first try to build Gnucash and it
>>> worked nicely.
>> What version of LibOFX did you use?
>>
>>> David C
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>> -derek
>>
> I was blindly following the instructions on the gnucash website without
> really understanding what I was doing.  I hav found some folders named
> named libofx 0.9.4, so I think that is what I got.  I also noticed that
> libofx 0.9.6 was only released on the 30th of last month, so I am not
> too surprised that I did not get it.  I did something wrong, however,
> because I still have release 2.4.11 available on my 'Launcher' and I
> cannot figure out how to get 2.4.12 to appear there.
>
> David C

Some additional information:

I have not delved into the details of libofx yet, but I have noticed
that there have been issues with line endings in the past, and there is
speculation that this is still true in the Windows build of GnuCash 2.4.12.

According to OFX203 dated May 1 2006 Chapter 2 page 29
"OFX 1.0.3 clients used a mix of LF and CRLF constructs and OFX 1.0.3
servers handled either linefeed (LF) or carriage return/line feed
(CRLF), but not often both. In the future, it is expected that 1.0.3
servers will be upgraded to handle both CRLF and LF."
Thus they may not produce the consistent single linefeeds that OFX 2.0.3
expects XML parsers to produce in compliance with XML 1.0 fifth edition
per paragraph 2.11 in
<http://www.w3.org/TR/2008/REC-xml-20081126/#sec-line-ends>.  Thus
libofx must still tolerate strange mixes as well as the now preferred
line-feeds only construction.  I suspect that libofx qualifies as a
parser, so whatever input it gets, it should output line-feeds only if
my understanding is correct.

So far this is only a rant, but I hope that it may trigger a line of
thought that will lead to resolution of the problem listed in Bug 697133.

David Carlson