Quote:
Originally Posted by Brian
For example, wheh Keka finds a ZIP archive with non-ASCII characteres it tries to guess the encoding and shows a encoding selection dialog box for confirmation unless you set it to always use a predef encoding such as ISO Latin 1. In JD, interaction is unwanted, so a default key would suffice.
|
That's not that easy because we don't get hands on the 'raw' bytes/infos but already processed information by the extraction module, for example zip.