Christian,
On Friday 23 September 2016 16:58:25 Christian Stimming wrote:
> Dear Thomas, how do you currently do the ofx import in kmymoney? Do you
> still use libofx as it is on source forge (or now GitHub) or do you have
> your own fork?
We use libofx as provided by the distros
Dear Thomas, how do you currently do the ofx import in kmymoney? Do you still
use libofx as it is on source forge (or now GitHub) or do you have your own
fork?
If there is any alternative available, it would be better to switch, because
libofx has an extremely bad architecture. However
John et al.
On Friday 23 September 2016 06:17:04 John Ralls wrote:
> Devs,
>
> LibOFX seems to be no longer actively developed. This is a problem because
> the OFX specification is approaching the second minor release (2.2) after
> LibOFX's target version as well as becau
Devs,
LibOFX seems to be no longer actively developed. This is a problem because the
OFX specification is approaching the second minor release (2.2) after LibOFX's
target version as well as because there is at least one bug (relating to date
handling) that affects GnuCash.
There is a
Changes:
Benoit Grégoire
- Workaround OFX files specifying invalid encoding values
(specifically: UNICODE and CP1252). This should fix most
encoding
problems reported.
- Look for DTD in source directory (simplifies d
On zondag 12 juni 2011, John Ralls wrote:
> On Jun 11, 2011, at 3:18 AM, Geert Janssens wrote:
> > John,
> >
> > I'm reviewing some open gnucash bugs at the moment. There's
> > https://bugzilla.gnome.org/show_bug.cgi?id=576163 regarding a bug in the
> >
On Jun 11, 2011, at 3:18 AM, Geert Janssens wrote:
> John,
>
> I'm reviewing some open gnucash bugs at the moment. There's
> https://bugzilla.gnome.org/show_bug.cgi?id=576163 regarding a bug in the
> external libofx library that has been fixed in libofx 0.9.3.
>
&
John,
I'm reviewing some open gnucash bugs at the moment. There's
https://bugzilla.gnome.org/show_bug.cgi?id=576163 regarding a bug in the
external libofx library that has been fixed in libofx 0.9.3.
According to the gnucash-on-osx git repo, GnuCash on OS X is still using
0.9.1. Ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Benoit,
I hope I can shade a little bit light on the situation of libofx in Debian.
Am 20.04.2011 18:53, schrieb Benoit Grégoire:
> Debian:
> - As far as I know, all their patches are upstream or obsolete
Good to know. :)
> - I
Benoit,
Benoit Grégoire writes:
[snip]
> For everyone's general information:
> -I DO still read libofx-devel regularly
> -I DO read the bug tracker at
> https://sourceforge.net/tracker/?group_id=61170&atid=496353 and review every
> patch (if with a pretty long lag tim
Running libofx and Gnucash from source, I didn't realise that the
dirtributions were generally years out of date, so most users were having
numerous crashes still with OFX imports (brigning down the entire client
application, not just libofx), as well as international caracter i
LibOFX 0.9.4:
- Patch to fix segfault on some malformed date formats. Inspired by Zach's
patch on launchpad.
- Packages-oriented changes:
- LibOFX will now look for DTDs in env variable OFX_DTD_PATH (if
present).
- Better handling of paths (tolerates trailing
LibOFX 0.9.3:
- Fix segfault on some files containing missing closing tags (bug
#2969817)
- Note to packagers: Upstream has moved to git at
git://libofx.git.sourceforge.net/gitroot/libofx/libofx
--
Benoit Grégoire, ing., PMP, PSM
Am Sonntag, 3. April 2011 schrieb Derek Atkins:
> Okay, I just ran:
>
> rm -rf /c/soft/libofx
This seems to have solved the issue. Thanks!
Christian
>
> FWIW, when I took a look there was a build hung after the scp. I wonder
> if there's a missing 'exit
Okay, I just ran:
rm -rf /c/soft/libofx
FWIW, when I took a look there was a build hung after the scp. I wonder
if there's a missing 'exit' or something? Unfortunately I clicked away
the svchost window and didn't copy it all, but there might still be a bug
in the build scri
I can look at it when I get home tonight, unless you get to it first Geert.
-derek
- Reply message -
From: "Christian Stimming"
Date: Sat, Apr 2, 2011 4:26 pm
Subject: win32 daily trunk build failing: Weird libofx linker flags?
To: "gnucash-devel"
The current win
t-2.0 -lgmodule-2.0 -
lglib-2.0 -lintl -Lc:/soft/libofx/lib -lofx -lm -lm
grep: /mingw/lib/gcc/mingw32/4.5.2/libstdc++.la: No such file or directory
/bin/sed: can't read /mingw/lib/gcc/mingw32/4.5.2/libstdc++.la: No such file
or directory
libtool: link: `/mingw/lib/gcc/mingw32/4.5.2/li
On zondag 13 februari 2011, Benoit Grégoire wrote:
> Ok, since LibOFX 0.9.2 has been released (thanks Christian), here's a
> proper release note:
>
> LibOFX 0.9.2:
> - Win32: Add gnucash patch that looks up the dtd installation directory
> from the curren
Ok, since LibOFX 0.9.2 has been released (thanks Christian), here's a proper
release note:
LibOFX 0.9.2:
- Win32: Add gnucash patch that looks up the dtd installation directory
from the current executable's location.
- Apply patch by Geert Janssens to fix a crash on in
I have received helpful assurances from the OFX consortium about the
interpretation of the license on the OFX DTDs, and with that included,
the Debian ftpmasters have agreed that the result is indeed a free
software license.
That returns us to the status quo ante.
Thomas
___
There is good news. Things are not yet certainly happy, but they are
much happier than I earlier thought they would be. I'm awaiting some
guidance from the Debian FTP masters on the question, but I have
received guidance from the OFX group which clarifies the license in such
a way that it seems (
Quoting Martin Preuss <[EMAIL PROTECTED]>:
> Hi,
>
> On Dienstag, 15. Januar 2008, Derek Atkins wrote:
> [...]
>> Martin Preuss <[EMAIL PROTECTED]> writes:
>> > Just for clarification: I do have sample OFX files, but none of them
>> > contains commodity/security transactions.
>>
>> I've just sent
Hi,
On Dienstag, 15. Januar 2008, Derek Atkins wrote:
[...]
> Martin Preuss <[EMAIL PROTECTED]> writes:
> > Just for clarification: I do have sample OFX files, but none of them
> > contains commodity/security transactions.
>
> I've just sent one (source: vanguard.com) via private email.
[...]
AqB
Hi,
On Dienstag, 15. Januar 2008, David Reiser wrote:
[...]
> And it turns out that mostly the only ones I have saved are the ones
> with only investment/security (and dividend...) transactions. They
> tend to have a lot of items that libofx doesn't handle (account
>
Hi,
On Dienstag, 15. Januar 2008, Derek Atkins wrote:
> Martin Preuss <[EMAIL PROTECTED]> writes:
> > Just for clarification: I do have sample OFX files, but none of them
> > contains commodity/security transactions.
>
> I've just sent one (source: vanguard.com) via private email.
[...]
Thanks, go
but none of them
> contains
> commodity/security transactions.
>
>
> Regards
> Martin
And it turns out that mostly the only ones I have saved are the ones
with only investment/security (and dividend...) transactions. They
tend to have a lot of items that libofx doesn'
Hi,
Martin Preuss <[EMAIL PROTECTED]> writes:
> Just for clarification: I do have sample OFX files, but none of them contains
> commodity/security transactions.
I've just sent one (source: vanguard.com) via private email.
> Regards
> Martin
-derek
--
Derek Atkins, SB '93 MIT EE, SM '
Hi,
On Dienstag, 15. Januar 2008, Derek Atkins wrote:
[...]
> > I guess those have to be supported in the long run, but as of this moment
> > I didn't receive a single request on this matter, so it isn't a priority,
> > yet.
>
> I know that's not completely true because I asked about it as soon
>
Martin Preuss <[EMAIL PROTECTED]> writes:
>> Are there any plans to extend AqBanking to support commodity/security
>> transactions?
> [...]
>
> I guess those have to be supported in the long run, but as of this moment I
> didn't receive a single request on this matter, so it isn't a priority, yet
Hi,
On Montag, 14. Januar 2008, Dave Reiser wrote:
> Martin Preuss wrote:
[...]
> > However, this will change when I receive requests from people who
> > actually want to help with testing those transaction imports (e.g. by
> > providing example files etc since I don't have any).
[...]
> I have do
Am Montag, 14. Januar 2008 16:55 schrieb Thomas Bushnell BSG:
> On Mon, 2008-01-14 at 15:52 +0100, Christian Stimming wrote:
> > In fact, after thinking about it for a while, your idea with packaging
> > libofx without the OFX DTDs sounds even worse for me. I mean, the
> > who
Hi,
On Montag, 14. Januar 2008, Dave Reiser wrote:
[...]
> I have dozens of sample files (though I'd have to spend some time
> sanitizing them).
[...]
That would be nice. What I absolutely don't have are files with
commodity/security transactions, so that would be fantastic if someone could
me
Martin Preuss wrote:
> Hi,
>
> On Montag, 14. Januar 2008, Derek Atkins wrote:
>> Martin Preuss <[EMAIL PROTECTED]> writes:
>>> But I wouldn't recommend it yet, since AqBanking's OFX parser only
>>> provides a subset of the LibOFX features (only
Hi,
On Montag, 14. Januar 2008, Derek Atkins wrote:
> Martin Preuss <[EMAIL PROTECTED]> writes:
> > But I wouldn't recommend it yet, since AqBanking's OFX parser only
> > provides a subset of the LibOFX features (only those functions currently
> > needed
On Mon, 2008-01-14 at 15:52 +0100, Christian Stimming wrote:
> In fact, after thinking about it for a while, your idea with packaging
> libofx without the OFX DTDs sounds even worse for me. I mean, the
> whole point of libofx is processing OFX. Shipping it without that
> fea
Quoting Thomas Bushnell BSG <[EMAIL PROTECTED]>:
>> GnuCash has a built-in importer for OFX files in the src/import-export/ofx
>> module. This importer requires libofx.
>
> What happens if libofx is available, but the important functionality
> reports an error inste
Martin,
Martin Preuss <[EMAIL PROTECTED]> writes:
> But I wouldn't recommend it yet, since AqBanking's OFX parser only provides a
> subset of the LibOFX features (only those functions currently needed my
> AqBanking: transaction statements, account balance and acco
Hi,
On Sonntag, 13. Januar 2008, Christian Stimming wrote:
> Am Samstag, 12. Januar 2008 19:04 schrieb Thomas Bushnell BSG:
[...]
> For importing OFX files into gnucash, libofx is required and it is going to
> be this way until someone rewrites the "Import OFX file" to use a
On Sun, 2008-01-13 at 22:27 +0100, Christian Stimming wrote:
> GnuCash has a built-in importer for OFX files in the src/import-export/ofx
> module. This importer requires libofx. If libofx is not available,
> the "Import OFX file" is no longer available. There are no pla
Just to clarify the libofx and aqbanking dependency of gnucash:
Am Samstag, 12. Januar 2008 19:04 schrieb Thomas Bushnell BSG:
> I have been told that the new aqbanking stuff supports OFX and does not
> use the problematic DTD files.
> (...)
> Also, this amps up the urgency on gnucas
So the DTD files I previously mentioned for libofx are, as I also
previously mentioned, available for use in libofx, but are not actually
free software.
Importantly, the license from the ofx specification permits their use
only in software which conforms to the specification, and doesn't p
Hi,
On Dienstag, 8. Januar 2008, Thomas Bushnell BSG wrote:
> Two of the DTD files in libofx are of uncertain license status.
[...]
> Does anyone on this list know by what right libofx is distributing these
> files?
[...]
I can't say anthing about that, however...
[...]
> What
On Tue, 2008-01-08 at 13:31 -0500, Thomas Bushnell BSG wrote:
> Two of the DTD files in libofx are of uncertain license status.
>
> ofx160.dtd has the following copyright notice:
>
> Open Financial Exchange DTD
> Copyright 1997, 1998, 1999 CheckFree Corp., Intuit Inc.
Two of the DTD files in libofx are of uncertain license status.
ofx160.dtd has the following copyright notice:
Open Financial Exchange DTD
Copyright 1997, 1998, 1999 CheckFree Corp., Intuit Inc., Microsoft
Corp.
All rights reserved
and ofx201.dtd has this:
* Copyright 1997, 1998, 1999
Hi,
this is to inform you about the release of LibOFX 0.9.0.
Changes are as follows:
--X8
This release now exports version information thus allowing depending
applications to
Hi,
On Samstag, 27. Oktober 2007, Christian Stimming wrote:
[...]
> As I said: We added a manual patch to libofx, which indeed does exactly
> what you mention here. See
> http://svn.gnucash.org/trac/browser/gnucash/trunk/packaging/win32/libofx-0.
>8.3-patch.diff courtesy of andi5,
Am Samstag, 27. Oktober 2007 14:52 schrieb Martin Preuss:
> > Just for the record: The current gnucash windows binary already contains
> > libofx and OFX DirectConnect. The build script for the windows binary
> > does this by compiling and installing opensp-1.5.2 and libofx-0
Hi,
On Samstag, 27. Oktober 2007, Christian Stimming wrote:
[...]
> Just for the record: The current gnucash windows binary already contains
> libofx and OFX DirectConnect. The build script for the windows binary does
> this by compiling and installing opensp-1.5.2 and libofx-0.8.3,
Hi Martin,
this is very nice - thanks a lot. I hope these changes will also make it into
a new libofx release - 0.8.4 or something like that. (0.8.3 came out January
2007.)
Am Samstag, 27. Oktober 2007 13:40 schrieb Martin Preuss:
> With these changes I was able to compile LibOFX for WIN32,
Hi,
I have just checked in some changes to the CVS repository of LibOFX:
* libofx.h, ofx_utilities.cpp: replaced some char* with "const char*" to make
GCC happy, wrapped arithmetic calculations in macro definitions in brackets
to avoid problems
* libofx.h: Removed this file, replac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been trying to build libofx on windows/mingw and it seems I've been
mostly successful.
OpenSP is OpenSP-1.5.2.tar.gz from
http://sourceforge.net/project/showfiles.php?group_id=2115&package_id=2869
; it seems the package is not
m.
>
> -derek
>
It's coming from ofxconnect, an extra utility to test OFXDirectConnect.
If I'm reading the libofx CVS diffs correctly, it was added last July.
(And made optional a few days later...)
It probably isn't even all that useful at this point for gnucash, so
at will be required is libxml++1. I
>>
>> EH? Who depends on libxml-1? I wouldn't expect that to build on windows,
>> but are you sure you need it?
>
> That's libxml++, not libxml. Libofx needs it. (Or at least configure
> fails without it on my mac. I obviously
Derek Atkins wrote:
> Quoting Dave Reiser <[EMAIL PROTECTED]>:
>
>> >As a next
>> > step, someone (hint, hint) needs to check whether the opensp-win32
>> > binary package is enough to build libofx on win32.
>>
>> Not unless there's a way to
Quoting Dave Reiser <[EMAIL PROTECTED]>:
> >As a next
> > step, someone (hint, hint) needs to check whether the opensp-win32
> > binary package is enough to build libofx on win32.
>
> Not unless there's a way to extract the headers from the binaries...
We
>As a next
> step, someone (hint, hint) needs to check whether the opensp-win32
> binary package is enough to build libofx on win32.
Not unless there's a way to extract the headers from the binaries...
Being foolish, I decided to try compiling the tarball in msys --
straigh
t;> when I left school this evening). But I noticed that aqbanking hadn't
>> found libofx.
>>
>> Is libofx not included yet because no one has had the time to try it,
>> or are there known issues?
>
> Libofx is not yet included because I haven't seen or tri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Reiser schrieb:
> I tried both the binary win32 install (it opened and seemed to
> work...) and the install-from-svn via install.sh (still compiling
> when I left school this evening). But I noticed that aqbanking hadn't
I tried both the binary win32 install (it opened and seemed to
work...) and the install-from-svn via install.sh (still compiling
when I left school this evening). But I noticed that aqbanking hadn't
found libofx.
Is libofx not included yet because no one has had the time to try it,
o
On 12/4/06, Hubert Bahr <[EMAIL PROTECTED]> wrote:
>
>No luck with your suggestion. ofxdump generates fields that have the
>values. It may be a problem with the import function of GnuCash. Since
> the
>problem exists with an ofx import I will look there first although the
>ulti
three cases use different paths
> into GNUcash. However, both Direct connect and OFX import use libofx.
> I do see some additional differences in Direct Connect and OFX import.
> But they both lose the quantity and value of the commodity.
>
> Thanks
> Hubert
>
>
> --
available. It just isn't being used. I am willing to work on this,
however I could use some help determining where to start. I can provide
a test case. To date I see that all three cases use different paths
into GNUcash. However, both Direct connect and OFX import use l
- bug fixes for GCC4.x and 64-bit compatibility
- fix to enable OFXDirectConnect in Aqbanking
- improvements to ofxpartner functionality
- minor build system modifications
- new fields for fees, commissions and stock split data
- fix a memory leak and a potential crashing bug
Addition
The patch is attached to the bug report http://bugzilla.gnome.org/
show_bug.cgi?id=164645
gnc-ofx-import.c treats OFX_REINVEST (a transaction combining the
payment of a dividend with the reinvestment of that dividend) and
OFX_INCOME (a transaction of a security paying a dividend, resulting
Hi David,
thanks for pointing out this build problem.
David Reiser schrieb:
(gwenhywfar won't build, so I can't even try getting aqbanking up)
gwenhywfar doesn't build? Not even the most recent gwenhywfar-1.19.1?
I and Martin Preuss would happily try to fix this.
Making all in test
if gc
> '<' character. If I delete the ofx file preamble so that the file
> starts with '', then it complains of a premature end of file at
> ''.
Probably a problem that should be discussed on the libofx developer list...
> The reason for the subject line
le so that the file
starts with '', then it complains of a premature end of file at
''.
The reason for the subject line is that I have the fink version of
libofx 0.7.0 installed in the normal location in the /sw tree. I also
built the CVS version of libofx 0.8.0 in
recompiling.
regards
Martin
--
"Things are only impossible until they're not"
LibChipcard - http://www.libchipcard.de/
AqBanking - http://www.aquamaniac.de/aqbanking/
OpenHBCI - http://www.openhbci.de/
libofx-0.7.99.diff.bz2
Description: BZip2
Christian Stimming <[EMAIL PROTECTED]> writes:
> Thanks for this information. The libofx version will now work with this, too,
> in HEAD and 1-8-branch. Should I also merge this change into the gnome2
> branch?
Nah. David will pull the change up in his next g2 merge.
>
Am Freitag, 31. Dezember 2004 18:21 schrieb Derek Atkins:
> You are right, that's not the problem. It appears that the --version
> output changed:
>
> --> /opt/libofx-cvs/bin/ofxdump --version
> libofx version: 0.6.4
>
> --> /opt/libofx-0.7.0/bin/ofxdump --versi
Christian Stimming <[EMAIL PROTECTED]> writes:
> That's unfortunate. However, I explicitly added code so that if an OFXPREFIX
> is specified by --with-ofx-prefix, then "ofxdump" is used as
> ${OFXPREFIX}/bin/ofxdump . But you have libofx-0.7 installed? Okay, surel
On Thu, 2004-12-30 at 17:43 -0500, Derek Atkins wrote:
> I got this:
>
> checking for libofx version >= 0.7.0... ./configure: line 13411: test:
> version:: integer expression expected
> configure: error: Libofx 0.7.0 or newer needed for ofx support
> make: *** [config.s
Am Donnerstag, 30. Dezember 2004 23:43 schrieb Derek Atkins:
> I got this:
>
> checking for libofx version >= 0.7.0... ./configure: line 13411: test:
> version:: integer expression expected configure: error: Libofx 0.7.0 or
> newer needed for ofx support
> make: *** [config.
Derek Atkins wrote:
Irrelevant in my case.
Whatever.
I apologise for getting threads mixed up.
John
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
John Ellson <[EMAIL PROTECTED]> writes:
> Derek Atkins wrote:
>
>>I got this:
>>
>>checking for libofx version >= 0.7.0... ./configure: line 13411: test:
>>version:: integer expression expected
>>configure: error: Libofx 0.7.0 or newer needed for of
Derek Atkins wrote:
I got this:
checking for libofx version >= 0.7.0... ./configure: line 13411: test:
version:: integer expression expected
configure: error: Libofx 0.7.0 or newer needed for ofx support
make: *** [config.status] Error 1
I suspect the problem is that "ofxdump" is n
I got this:
checking for libofx version >= 0.7.0... ./configure: line 13411: test:
version:: integer expression expected
configure: error: Libofx 0.7.0 or newer needed for ofx support
make: *** [config.status] Error 1
I suspect the problem is that "ofxdump" is not in my PATH, but
77 matches
Mail list logo
