encoding bug in 3.0

[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.

Op 6 april 2018 23:05:37 +02:00, schreef Colin Law <clanlaw at gmail.com>:

> On 6 April 2018 at 17:52, René Romijn <<rene at romijnfotografie.nl>> 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 opening the file it cannot find any custom reports anymore.
> > 
> 
> As a work around you could rename the folder of course. Then you
> would have to use File > Open to open it, or double click the file.
> 
> Colin
>