I think, that better solution rathter than:
Expected results:
File-roller should attempt to detect the encoding of the filename and do the
appropriate conversion (iconv-style) to UTF-8. If it cannot do a conversion, it
should nevertheless make the file accessible. For example, unconverted
characters could be changed to 0xFFFD (Unicode Replacement Character, http://www.fileformat.info/info/unicode/char/fffd/index.htm).
Is to allow user to pick input encoding from combobox (like html input encoding in firefox)
Of course, File-roller can try to detect.
I think, that better solution rathter than: www.fileformat. info/info/ unicode/ char/fffd/ index.htm).
Expected results:
File-roller should attempt to detect the encoding of the filename and do the
appropriate conversion (iconv-style) to UTF-8. If it cannot do a conversion, it
should nevertheless make the file accessible. For example, unconverted
characters could be changed to 0xFFFD (Unicode Replacement Character,
http://
Is to allow user to pick input encoding from combobox (like html input encoding in firefox)
Of course, File-roller can try to detect.