XML Settings

Use this dialog to configure the default settings for XML sources.

Output files

Specifies what kind of output file(s) are created. Possible choices are:

Value	Description
Localized files	Create a new file for each language in the project.
Multilingual file	Create one multilingual file containing all the languages of the project.

Options

Specifies the formatting options when writing the localized XML files. Possible values are:

Value	Description
Keep original format	Retain the XML file original format in localized files.
Remove white spaces	Remove the leading and trailing white spaces from the elements.

Entities to be processed

Specifies how XML entities are processed. Sisulizer always decodes predefined XML entities when reading an XML file. The following table contains the predefined entities:

Character	Name entity	Hex entity	Integer entity
"	"	"	"
&	&	&	&
'	'	'	'
>	>	<	<
<	<	>	>

Sisulizer always decodes any hex or integer entity. For example if the XML file contains * it will be read as "*".

When creating localized XML file Sisulizer always encodes & and <. Encoding of other predefined entities depends on their usage in the original file. If the original file has encoded them then the localized files created by Sisulizer use the same encoding. If the original uses several encoding methods Sisulizer prefers name encoding over hex and integer encoding, and hex encoding over integer encoding.

If original XML files contains hex or integer encoding that do not belong to the above predefined entities Sisulizer does never use any encoding when writing characters to the localized XML file. Plain character is written instead.

String entities

If String entities is checked Sisulizer decodes custom string entities when reading the XML file and encodes them when writing the XML file. A custom string entity is a entity defined either in DOCTYPE element or in the DTD file.

<!ENTITY sportname "Downhill skiing">

Whenever an XML element contains &sportname; it will be expanded to Downhill skiing. For example:

<sample>&sportname; is very fast sport.</sample>

will be expanded to "Downhill skiing is very fast sport".

If String entities is unchecked Sisulizer does not decode the string but leaves it as it is. For example the above sample will be read as "&sportname; is very fast sport".

When writing localized XML file Sisulizer does never use string entities but writes plain characters.

File entities

If File entities is checked Sisulizer decodes custom file entities when reading the XML file and encodes them when writing the XML file. A custom file entity is a file based entity defined either in DOCTYPE element or in the DTD file.

<!ENTITY vehicle SYSTEM "Sports.xml">

The content of Vehicle.xml is:

<?xml version="1.0" encoding="UTF-8"?>
  <sport>Skiing</sport>
  <sport>Cycling</sport>

Whenever an XML element contains &sports; it will be expanded to content of Sports.xml file. For example:

<sample>&sports;</sample>

will be expanded to:

<sample>
  <sport>Skiing</sport>
  <sport>Cycling</sport>
</sample>

If File entities is unchecked Sisulizer does not decode the string but leaves it as it is. For example the above sample will be read as will be read as "&sports;".

When writing localized XML file Sisulizer does never use file entities but writes plain characters.

Use byte order mark

Specifies if Sisulizer includes the byte order mark (BOM) in the beginning of UTF-8 or UTF-16 file when writing files. The following table contains BOM used with each file format:

Format	BOM	Description
UTF-8	0xEF, 0xBB, 0xBF	UTF-8 is byte order insensitive but BOM is used to make difference between code page based text files and UTF-8 based text files.
UTF-16LE	0xFF, 0xFE	Little endian UTF-16 text file.
UTF-16BE	0xFE, 0xFF	Big endian UTF-16 text file.
Code page	N/A	BOM is not used with code page based text files.

Context ids

Contains a list of attributes names that are treated as context attribute.