GNOME Bugzilla – Bug 581816
render output filename not in unicode
Last modified: 2010-02-05 22:01:16 UTC
Spaces are replaced by %20 in the render dialog, and so if you go to change the filename again (without actually changing it), this will also have the side effect that you get %20 in the output filename.
Actually, it's not just spaces; if you use accents and such, you'd better render directly and not decide to revisit the file chooser dialog without retyping the filename.
verified still in 0.13.3
Created attachment 143300 [details] [review] complete... if you are on a utf8 system :( This patch makes the filename box show what you expect, and reentering the filename box show what you expect, BUT, as in the gtk docs, we can't _reallly_ be sure what the encoding is. Perhaps it would be better to translate backwards from the URI?
Created attachment 143301 [details] [review] better patch, decoding the url to always get a real utf8 string This one should be much much better. It also fixes the bug in the old patch that got the path setting wrong. however, it imports more libs.
commit edd856016b79879c0e9845fd5b87d631661aabac Author: Karl Palsson <bugs@tweak.net.au> Date: Wed Sep 16 23:39:07 2009 +0000 Fixes bug blah, the filename display with non ascii chars