It's a very old anoying bug and it's still here!
If you have characters with accents in the name of a file (éàä...ect) you can save the factory file without any error message.
But when you try to load your factory file again you get a file parse error, so you loose all your setting.
this is an old bug and it relates to any non-ascii file names.
there are other posts on encoding / character sets...
ascii can be used only in the US and a few other countries. All other countries and regions like Canada, Mexico, France, Germany, all countries in Europe, Russia, all countries in Asia either use extended\adapted ascii or long ago swiched to UTF
why this nice product is so outdated we may just guess. somehow developers just ignore it....
I know about non-ascii filename, I know it's the source of this bug, yes I have to rename my file, but sometimes I forgot, and later when I think I just have to load the factory file to print it again, that failed!
We are on 2019 and there is a lot of softwares supporting this kind of characters.
If they don't want to spend time for this, at least that could be better to get an understandable error, not just a parse error !
Please fix awful bugs before ask to upgrade to version 5
This problem does not only happen in case of filenames. I used to comment some lines in the scripts, where i used localized ascii characters or just a comma (,). In this case I get a parsing error at next application start.
Why not switch to UCS and get rid of such problems?
gcodestat integrates with Simplify3D and allow you to
Calculate print time accurately (acceleration, max speed, junction deviation all taken into consideration)
Embed M117 codes into G-Code
Upload your G-Code directly to Octoprint
open source and unlicence