You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Thanks for the converter. I found it by chance yesterday while I was considering writing my own :-)
A minor suggestion for a fix: some of my accounts use accented letters. There is also apparently somewhere an infinity sign, though I could not find it in the XML file itself.
Nonetheless, when running your tool in Windows Powershell, I am getting
> python3 .\kmymoney2ledgers.py .\test_kmy_xml.xml
Processing transaction 2/8703
Processing transaction 1002/8703
Processing transaction 2002/8703
Processing transaction 3002/8703
Processing transaction 4002/8703
Processing transaction 5002/8703
Processing transaction 6002/8703
Processing transaction 7002/8703
Processing transaction 8002/8703
Processing transaction 8703/8703
Traceback (most recent call last):
File "C:\Users\briot\Desktop\kmymoney2ledgers.py", line 438, in <module>
main(sys.argv)
File "C:\Users\briot\Desktop\kmymoney2ledgers.py", line 430, in main
out_file_id.writelines(
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.11_3.11.2288.0_x64__qbz5n2kfra8p0\Lib\encodings\cp1252.py", line 19, in encode
return codecs.charmap_encode(input,self.errors,encoding_table)[0]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The simple fix I applied was to change line 439 to
It likely isn't the optimal, maybe we should just apply the encoding of the input XML file itself, though I think kmymoney might always be using UTF-8 in any case.
thanks
Emmanuel
The text was updated successfully, but these errors were encountered:
Hello,
Thanks for the converter. I found it by chance yesterday while I was considering writing my own :-)
A minor suggestion for a fix: some of my accounts use accented letters. There is also apparently somewhere an infinity sign, though I could not find it in the XML file itself.
Nonetheless, when running your tool in Windows Powershell, I am getting
The simple fix I applied was to change line 439 to
It likely isn't the optimal, maybe we should just apply the encoding of the input XML file itself, though I think kmymoney might always be using UTF-8 in any case.
thanks
Emmanuel
The text was updated successfully, but these errors were encountered: