encoding bug in 3.0

Fri Apr 6 17:05:37 EDT 2018

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