Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different character encodings #129

Open
hping opened this issue Jan 8, 2013 · 1 comment
Open

Different character encodings #129

hping opened this issue Jan 8, 2013 · 1 comment

Comments

@hping
Copy link

hping commented Jan 8, 2013

It would be quite nice to have Autopsy support other character encodings, such as different setups of EBCDIC and also be able to control which encoding is used. For instance 'Latin - Extended', doesn't really say what's used in the background.

@bcarrier
Copy link
Member

bcarrier commented Jan 8, 2013

Can you help scope out this feature? There are two places that Autopsy uses script information. One is with keyword indexing. For files where the format is not known, we run our internal version of 'strings' on it and it knows about things beyond just latin characters. The check boxes in the Keyword search config represent the Unicode spaces. Perhaps we should better note that.

The other place is that once you've selected a file, there is a strings viewer on the bottom right (that uses the same code as the keyword search code). It also allows you to run strings of a single script on the text.

Are you basically saying that you want EBCDIC added as a supported encoding?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants