Update of bug #18884 (project mypaint):
Severity: 5 - Blocker => 4 - Important
_______________________________________________________
Follow-up Comment #5:
Can you try to reproduce with the current git at all? I'm marking it as not a
Blocker, given that it only affects Windows.
Thinking for this one we should at least introduce some debugging output so
that when it happens again we at least dump out the user's
sys.getfilesystemencoding(). In this case, I'm guessing something like UTF-16
for Korean, noting that u"ub0aduc7d1ubafb" looks plausible ("낭쟑뫻"), but
I'm not seeing any BOM on it (which is what .encode would normally put there).
Guessing a bit here.
I'll see if I can force a non-UTF8 filename encoding on my system here.
Internally, MyPaint has been using the proper Unicode strings. All the way up
to trying to write files, it seems. Perhaps it's time to get Python to open()
the output stream and pass the file handle/descriptor/whatever on to the C
code somehow?
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?18884>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
