Opening and Saving Documents with Unsupported Characters
When loading documents, Oxygen JSON Editor reads the document prolog to determine the specified encoding type. This encoding is then used to instruct the Java Encoder to load support for and to save the document using the specified code chart. When the encoding type cannot be determined, Oxygen JSON Editor displays the Available Java Encodings dialog box that provides a list of all encodings supported by the Java platform.
Opening Documents with Unsupported Characters
When opening a document in Oxygen JSON Editor, if it contains
characters that are not supported by the specified encoding standard (these unrecognized
characters are rendered as an empty box 
), the
application determines how to handle them based upon the setting specified in the Encoding Errors Handling option in the
Encoding preferences page. The default setting is
REPORT, which means an error message is displayed for characters
that cannot be represented in the specified encoding. If the option is set to
REPLACE, the character is replaced with a standard replacement
character for the particular encoding. If the option is set to
IGNORE, the error is ignored and the character is not rendered.
Saving Documents with Unsupported Characters
When saving a document edited in the Text, Grid, or Design modes, if it contains characters that are not supported by the encoding declared in the document prolog, Oxygen JSON Editor displays a notification that you need to resolve the conflict before saving the document.
When saving a document edited in the Author mode, all characters that fall outside the detected encoding will be automatically converted to hexadecimal character entities.
When saving a document with UTF-16 encoding, the saved document has a Byte Order Mark (BOM) that specifies the byte order of the document content. The default byte order is platform-dependent. That means that a UTF-16 document created on a Windows platform (where the default byte order mark is UnicodeLittle) has a different BOM than one created on a macOS platform (where the byte order mark is UnicodeBig). The byte order and the BOM of an existing document are preserved when the document is edited and saved. This behavior can be changed in Oxygen JSON Editor from the Encoding preferences page.