Re: [GNC] encoding bug in 3.0

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: > > > Hi

Re: [GNC] encoding bug in 3.0

Done! Op 10 april 2018 19:05:48 +02:00, schreef Geert Janssens : > Thanks, > > That shows two locations that handle this improperly. > > Can I ask you to file this as a bug report [1] so it won't get lost and can be > fixed. Please also add the trace file snippet

Re: [GNC] encoding bug in 3.0

Thanks, That shows two locations that handle this improperly. Can I ask you to file this as a bug report [1] so it won't get lost and can be fixed. Please also add the trace file snippet in the report. Thanks! Geert [1] Refer to http://wiki.gnucash.org/wiki/Bugzilla to learn how to use

Re: [GNC] encoding bug in 3.0

Hi Geert, This is what the trace is saying after the first start of 3.0: * 17:23:16 WARN Could not spawn perl: Uitvoeren van dochterproces is mislukt (No such file or directory) * 17:23:16 WARN [GncDbiBackend::session_begin()] Sqlite3 file C:\Users\René

Re: [GNC] encoding bug in 3.0

Please make sure to keep the conversations on the mailing list unless explicitly asked to send private mails. Additionally, that one person you reply to may not have all the answers. You have more chances for a complete answer by keeping the conversation on the list. You can do so by using the

Re: [GNC] encoding bug in 3.0

Op zaterdag 7 april 2018 07:29:34 CEST schreef René Romijn: > Hi Colin, > > That won't work entirly because gnucash is looking for the reports at the > Documents .gnucash directory, because it cannot find them gnucash is using > the Temp directory for the custom reports. That's not completely

Re: encoding bug in 3.0

On 6 April 2018 at 17:52, René Romijn wrote: > 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

encoding bug in 3.0

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.