Altova DatabaseSpy 2025 Enterprise Edition

In the Encoding section of the Options dialog box, you can specify several options for file encodings.

dlg_options-gen-encoding

 

Default encoding for new SQL files

Define the default encoding for new files so that each new document includes the encoding-specification that you specify here. If a two- or four-byte encoding is selected as the default encoding (i.e., UTF-16, UCS-2, or UCS-4), you can also choose between little-endian and big-endian byte ordering for the SQL files. The encoding for existing files will, of course, always be retained.

 

Open SQL files with unknown encoding as

You can select the encoding with which to open an SQL file with no encoding specification or where the encoding cannot be detected.

 

Note:SQL files which have no encoding specification are correctly saved with a UTF-8 encoding.

 

BOM (Byte Order Mark)

When a document with two-byte or four-byte character encoding is saved, the document can be saved either with (i) little-endian byte-ordering and a little-endian BOM (Always create BOM if not UTF-8); or (ii) the detected byte-ordering and the detected BOM (Preserve detected BOM on saving).

© 2018-2024 Altova GmbH