On February 1, 2012 06:47:11 PM Martin Javorek wrote:
> Problematic "one transaction" file can be found as attachment in my original
> post https://mail.kde.org/pipermail/kmymoney-devel/2012-January/007486.html
Ok, this was actually a libofx bug (All XML files were treated as CP1252). The
bug is
gart"
Cc: kmymoney-devel@kde.org, "Martin Javorek" , "Cristian
Oneț"
Sent: Wednesday, February 1, 2012 6:34:49 PM GMT +01:00 Amsterdam / Berlin /
Bern / Rome / Stockholm / Vienna
Subject: Re: [Kmymoney-devel] OFX and UTF-8 problem
On January 23, 2012 02:24:39 PM Thom
On January 23, 2012 02:24:39 PM Thomas Baumgart wrote:
> Hi,
>
> on Monday 23 January 2012 13:52:47 Martin Javorek wrote:
> > > It could be that libofx (ofxdump is part of the project) has a
> > > problem. KMyMoney uses libofx to import OFX data. I think you should
> > > post the above question to
2012/1/23 Martin Javorek :
>> It could be that libofx (ofxdump is part of the project) has a
>> problem. KMyMoney uses libofx to import OFX data. I think you should
>> post the above question to the project's developers [1]. My
>> observation that with the text header it works and without it does n
Hi,
on Monday 23 January 2012 13:52:47 Martin Javorek wrote:
> > It could be that libofx (ofxdump is part of the project) has a
> > problem. KMyMoney uses libofx to import OFX data. I think you should
> > post the above question to the project's developers [1]. My
> > observation that with the te
> It could be that libofx (ofxdump is part of the project) has a
> problem. KMyMoney uses libofx to import OFX data. I think you should
> post the above question to the project's developers [1]. My
> observation that with the text header it works and without it does not
> was empirical :).
I want
2012/1/18 Martin Javorek :
> Cristian,
> thanks a lot for investigation.
>
>> As a side-note the file you've provided needs an extra OFX header to be
>> interpreted with the correct encoding by libofx (used by the plugin to import
>> OFX files) as in the attached version. Without that header the im
Cristian,
thanks a lot for investigation.
> As a side-note the file you've provided needs an extra OFX header to be
> interpreted with the correct encoding by libofx (used by the plugin to import
> OFX files) as in the attached version. Without that header the import won't
> work correctly any
On Monday 16 January 2012 15:51:24 Cristian Oneț wrote:
> 2012/1/16 Martin Javorek :
> > Hi all,
> > regarding this forum post:
> > http://forum.kde.org/viewtopic.php?f=69&t=98633 I'm sending
> > one-transaction OFX file in UTF-8 encoding which I cannot import into
> > KMyMoney without character en
2012/1/16 Martin Javorek :
> Hi all,
> regarding this forum post: http://forum.kde.org/viewtopic.php?f=69&t=98633
> I'm sending one-transaction OFX file in UTF-8 encoding which I cannot import
> into KMyMoney without character encoding issue.
>
> But, please keep in mind - I'm a KmyMoney beginner
Hi all,
regarding this forum post: http://forum.kde.org/viewtopic.php?f=69&t=98633 I'm
sending one-transaction OFX file in UTF-8 encoding which I cannot import into
KMyMoney without character encoding issue.
But, please keep in mind - I'm a KmyMoney beginner, I'm not reporting a bug. It
is pos
11 matches
Mail list logo