Re: [GNC] encoding bug in 3.0

2018-04-11 Thread René Romijn
Hi Geert, I allready reverted back to 2.6.20, but i can try again. The problem is that my username contains é and gnucash 3.0 seems that it cannot handle that. Where exactly are the trace files located? Regards, René. > Op zaterdag 7 april 2018 07:29:34 CEST schreef René Romijn: >

Re: [GNC] encoding bug in 3.0

2018-04-10 Thread René Romijn
d the trace file snippet in the report. > > Thanks! > > Geert > > [1] Refer to <http://wiki.gnucash.org/wiki/Bugzilla> to learn how to use > bugzilla > > Op dinsdag 10 april 2018 18:28:05 CEST schreef René Romijn: > > > Hi Geert, > > > > T

Re: [GNC] encoding bug in 3.0

2018-04-10 Thread René Romijn
\Boekhouding\InstInkt.gnucash not found * 17:24:15 CRIT Cannot open file C:\Users\RENROM~1\AppData\Local\Temp\René Romijn\GnuCash\expressions-2.0: No such file or directory Its getting confused with the é sign and because it cannot decode it, its translatet to é Result is that my old .gnucash

encoding bug in 3.0

2018-04-06 Thread René Romijn
After upgrade to 3.0 i cannot open my file. Im on Windows 10 and the default location is on a directory with a é . its is trying to translate that to ã©. So it looks like its not using UTF-8 encoding. result also after opening the file it cannot find any custom reports anymore.