© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I'll have to look into the specifics here, but we follow glib's behavior in validating names.
There are three main encodings in play: internal (UTF-8), system and filesystem. The OS settings can affect the latter. To work without problems, the filesystem encoding needs to be set to match that of the filesystem. Modern Linux config set these to be UTF-8. If the filesystem encoding glib is using has been set to UTF-8, then all byte sequences must be valid UTF-8.
If random bytes are desired, then the OS needs to be set to report a different filesystem encoding - one that allows random byte sequences. ISO-8859-1 might be suitable.
Bottom line is that for code and user safety, Inkscape enforces what the system has been configured to. If one needs sequences that are illegall UTF-8, then one needs to configure to not report UTF-8 as the filesystem encoding.