Closed codeHorse87 closed 1 month ago
This is certainly a good feature to have for Threat Dragon. We really should not be restricted to Latin1 characters for path and file names. It would be good to get this into version 1.4, and it is now on the 1.4 project board: https://github.com/OWASP/threat-dragon-desktop/projects/2
Transferred to threat dragon repo
This was also reported in #269 'Error on open invalidCharacterError'
This issue is stale because it has been open for 6 months with no activity.
the latest version of Threat Dragon supports extended (non Latin1) character sets
for example a model file ~/ÖVB/test.json
can be opened
As a result of #59 I propose to improve the support for utf-8 and unicode character sets in the file paths and names I'm always frustrated when models can't be saved or opened when the target directory or model name includes non Latin1 characters
Describe the solution you'd like
Support utf-8/unicode based on the default encoding of the operating system
Describe alternatives you've considered Alternatively there can be a warning, or message to the user regarding the unhandled exception in #59 about the problem