Options, .NET binary

Use this sheet to specify the options of the .NET resource file(s).

Linked file localization

Specifies how linked resource items are localized. Possible values are:

Value Description

Localize data The data from the linked file will be scanned, and localized file data will be embedded in the localized .resx files.
This is the default, and it lets you easily localize the data of the linked files.

Localize file name The link file name is scanned, and the translator can enter a language-specific file name.
If you use this, you need to provide localized linked files and make sure that the translation column contains the right file. For example, if the original is "..\Resources\Data.xml" then you create German into "..\Resources" and name it "Data_de.xml". Finally, the translation column would contain "..\Resources\Data_de.xml".

Value	Description
Localize data	The data from the linked file will be scanned, and localized file data will be embedded in the localized .resx files. This is the default, and it lets you easily localize the data of the linked files.
Localize file name	The link file name is scanned, and the translator can enter a language-specific file name. If you use this, you need to provide localized linked files and make sure that the translation column contains the right file. For example, if the original is `"..\Resources\Data.xml"` then you create German into `"..\Resources"` and name it `"Data_de.xml"`. Finally, the translation column would contain `"..\Resources\Data_de.xml"`.

.NET Version

Specifies the .NET type and version that the resource file(s) use. Type specifies the .NET type. Possible values are:

Value	Possible values
.NET	1.0, 1.1, 2.0, 2.1, 2.2, 3.0, 3.1, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0
.NET Framework	2.0, 3.0, 3.5, 4.0, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, 4.8.1
.NET Standard	1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 2.0, 2.1
.NET Compact	3.5, 3.7, 3.9

Version specifies the version of the select .NET type.

Detect string format

Specifies if a resource string format should be detected. Soluling can parse complex resource strings (those that contains XML, JSON, structured strings, etc) using the dedicated parser. Possible values are:

Value	Description
No	No detection. Strings are scanned as plain strings.
Yes, using strict match	Strings formats are detected using a strict match. For example, to detect as XML, the XML data must start with a XML header.
Yes, using loose match	Strings formats are detected using a loose match.

Soluling supports following string formats:

Format	Description
Plain text	String contains plain text.
Segmented text	String contains the segmented text.
Boolean	String contains a boolean value. 1/0, true/false, and yes/no are valid values.
Integer number	String contains an integer number.
Floating point number	String contains a floating-point number. It can be in scientific format (e.g., 1.45E-12). The decimal separator (if any) must be a period (e.g., 1.5).
Color	String contains a color value. Possible formats are [#\|$\|0x][AA]RRGGBB or [#\|$\|0x][A]RGB.
Date and time	String contains a date and time value. ISO 8601 (Wikipedia) must be used.
Expression	String contains a structured string that is defined using an expression. Regular expressions are used to parse the string.
Defined text	String contains the defined text. A text definition (using regular expressions) is used to parse the string.
Script	String contains script data. A script/source code parser is used to parse the string.
XML	String contains XML data. An XML parser is used to parse the string.
JSON	String contains JSON data. A JSON parser is used to parse the string.
YAML	String contains YAML data. A YAML parser is used to parse the string.
INI	String contains INI data. An INI parser is used to parse the string.
HTML	String contains HTML data. An HTML parser is used to parse the string.
SVG	String contains SVG data. An SVG parser is used to parse the string.
Base64 encoded binary data	String contains base64 encoded data. Encoded data is decoded into original binary data and scanned.
Base32 encoded binary data	String contains base32 encoded data. Encoded data is decoded into original binary data and scanned.
Base16/hex encoded binary data	String contains base16/hex encoded data. Encoded data is decoded into original binary data and scanned.
URL encoded binary data	String contains URL encoded data. Encoded data is decoded into original binary data and scanned.

RigthToLeft properties

Specifies how FlowDirection/RightToLeft and RightToLeftLayout properties are localized. Possible values are:

Update FlowDirection/RightToLeft and RightToLeftLayout properties automatically	Right to left properties are automatically updated to match the target language no matter what the scan rules are.
Scan FlowDirection/RightToLeft and RightToLeftLayout properties and let translator to change them	Only those right to left properties matching the scan rules is scanned.
Ignore FlowDirection/RightToLeft and RightToLeftLayout properties	No right to left properties is scanned or updated.

Check Add FlowDirection/RightToLeft and RightToLeftLayout properties if needed checkbox if you want that Soluling adds the right-to-left properties if they are needed but do not exist in the original form.

Input method editor properties

Specifies if IME (input method editor) properties are localized. Possible values are:

Update IME properties automatically	IME properties are automatically updated to match the target language no matter what the scan rules are.
Scan IME properties and let the translator change them	Only those IME properties matching the scan rules are scanned.
Scan IME properties except when the value is NoControl	As above but only those values that are no NoControl (default value) are scanned.
Ignore IME properties	No IME properties are scanned or updated.