Closed GoogleCodeExporter closed 9 years ago
that was supposed to be filed as an enhancement, by the way.
Original comment by mokojum...@gmail.com
on 25 Aug 2007 at 6:10
That does sound like a decent idea.
Original comment by paracel...@gmail.com
on 29 Aug 2007 at 8:13
Speaking of which, I think it could be a tad smarter too. Older, mostly
mac-specific file types such as MacBinary
and BinHex (and perhaps StuffIt) would most likely be using MacRoman encoding
but the default selection
always seems to be something like Western (ISO Latin 1).
Also, if I choose to stop at this point it extracts the file anyway using the
currently selected encoding.
Original comment by andrew...@gmail.com
on 31 Aug 2007 at 12:40
The popup menu now contains the result for each encoding type possible, styled
to try and minimize clutter. It
might need some further tweaking, though.
The encoding picking is marginally smarter in the new engine, too, but could
probably be improved.
Original comment by paracel...@gmail.com
on 3 Jul 2009 at 2:08
Original issue reported on code.google.com by
mokojum...@gmail.com
on 25 Aug 2007 at 6:09