Encodings

There are a lot of different character encodings that describe how characters of some specific alphabet are encoded in single or multi-byte codes. The editor window text pane is used to display the textual representation of the document. The text it displays may of course be interpreted according to one or another encoding.

Hex Editor Neo allows you to choose the editor window's encoding from a wide set of supported encodings. As long as an encoding is a property of individual editor window, you can set different encoding for each editor window, even if they represent the same document.

Below is a full list of supported encodings.

NOTE: Support for a specific encoding depends on installed Windows code pages and fonts. If required components cannot be found for a selected encoding, the “Encoding not supported” text is displayed instead of document's data. Typing in text pane is also disabled until you select another, supported encoding.

Working with Encodings

The current editor window's encoding is displayed on the status bar:

Text pane displays text data according to selected encoding. When you type new data on the keyboard (with text pane active), typed characters are processed according to selected encoding.

When the editor window is displaying data in Hex Words or Decimal Words view type, the UNICODE (UTF-16) encoding is automatically selected (as the text pane displays UNICODE data in these modes).

To change the current window's encoding, open the shortcut menu, select “Encoding” item and choose an encoding from the list. The list consists of “Default ANSI”, “Default OEM”, 5 recently used encodings and the “Other” item. Selecting the Other item opens a full list of supported encodings.

UTF-8 Support

UTF-8 is the first (and only, for now) multi-byte encoding supported by the editor.

The editor provides the full support for UTF-8 encoding. It not only displays the text encoded in UTF-8, but also allows you to type new data in this encoding. When you type, entered characters are converted on-the-fly and a single entered character may occupy up to 4 bytes.

When a character occupies several bytes, a space character is displayed in all but the last cell (in Text View). The last cell displays the character itself.

UTF-8 encoding defines strict rules for encoding UNICODE characters into single, two, three or four bytes. If these rules are broken and Hex Editor Neo cannot decode the character, it displays the ‘?’ character for each cell that contains invalid data.

All editor features, such as Find, Fill and so on are compatible with current editor window's encoding, and, therefore, are capable of working with UTF-8 as well.

Scripting

All encodings are available for scripts as Encodings enumeration. Use the IDocumentView.encoding property to query or set the editor window's encoding.