Bug 356870

Summary:	Okteta doesn't support table files/custom character encodings.
Product:	[Applications] okteta	Reporter:	Jeremy Andrews <athenian200>
Component:	Structures Tool	Assignee:	Alex Richardson <arichardson.kde>
Status:	REPORTED ---
Severity:	wishlist	CC:	kossebau
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jeremy Andrews 2015-12-18 14:14:32 UTC

I work with a lot of custom/unusual encodings, and it would be really helpful to be able to define my own encoding tables for the right-hand pane. For instance, instead of having to use a preset like ASCII or EBCDIC, I would be able to create a file with definitions like:

B0 = "A"
CA = "a"
FF = "/"

And so on, and the hex editor would interpret the bytes as being those characters you listed in the custom table rather than ASCII characters or EBCDIC characters. So if you enter a character on the right-hand side, it interprets it as the byte you defined, and vice-versa. The ability to switch between encodings is very close to what I want already, it's just that they're all hard-coded and not user-definable.

If it's not too much trouble, I'd appreciate someone taking a look at adding this functionality.

Comment 1 Alex Richardson 2015-12-21 08:33:30 UTC

Are these all 1byte = 1 character encodings? 
Do you want them displayed in the main view next to the hex bytes? Or would a workaround using the structures tool be acceptable?

Comment 2 Jeremy Andrews 2015-12-24 21:20:54 UTC

Yes, these are all one byte / one char encodings.  I could probably make it work for my personal use by modifying the EBCDIC encoding file, and playing with the arrays and recompiling every time I wanted to use a new encoding. I was just thinking that a table file system could be useful for a lot of people if someone that knew enough to implement it correctly did it. Currently, I'm using a Windows-based hex editor in WINE because no Linux hex editor supports what I want to do. 

Well, if the structures tool view can be used to display text in different encodings, then it would be fine. But it mostly seems to put labels on various blocks of bytes instead. I'm not sure if there's another mode that does what I'm wanting, though.