Resource options

Use this sheet to specify resource options.

Configuration

Specifies the active configuration. You can add any number of configurations. This makes it possible to create multiple output files with different properties easily.

Localized resources contain

Specifies what resource items are written to the localized resource files. Possible values are:

Value	Description
Different items	If checked, Soluling writes only those resource items where the value of the item is different from the original value. If the edit sheet has a translation, but it is the same as the original, the value is not written. This is the default value.
Translated items	If checked, Soluling writes those resource items that are translated. In other words, a value has been entered into an edit sheet.
All items	If checked, Soluling writes all resource items to the localized resource file. If no translation is entered in the edit sheet, the original value is written.

If you use Different items or Translated items, value Soluling can greatly optimize the localized resource files' size. This will also fully enable the platform's build-in language fallback (e.g., .NET, Android, or Java). If you choose All items, no runtime fallback is done, but Soluling does fallback on the build process.

Reading order properties

Specifies reading order and layout properties. Possible values are:

Value	Used in	Description
Set RightToLeft property	Windows Forms	Check this to make Soluling add RightToLeft attributes on bi-directional languages. This sets the reading order of all components of the forms. It also mirrors everything (form and its components) except container controls (Panel, GroupBox, TabPage).
Set RightToLeftLayout property	Windows Forms	Check this to make Soluling turn RightToLeftLayoyt property true on bi-directional languages during the build process. This mirrors container controls.
Set FlowDirection property	XAML	Check this to make Soluling add FlowDirection attribute to bi-directional XAML resources. This sets the reading order and mirrors the user interface. If you uncheck this, you should set the FlowDirection property of all forms on runtime if the active language is a bi-directional language.

Multiple script languages

This list contains all those languages used in the project that can use more than one script. These languages are so-called multi-script languages. When writing the language id of such language, Soluling, by default, adds a script part to the code. For example, instead of using just zh (Chinese) Soluling writes either zh-Hans (Simplified Chinese) or zh-Hant (Traditional Chinese). Use this list if you want that one of the scripts is the default script and language ids using that script are written without a script. To set a default script, right-click a language a choose the default script. After that, the language with that the script does not use the script part in the language id anymore.

Chinese has an additional option. .NET before 4.0 used a different way to code Chinese scripts than .NET 4.0 or later. The following table contains the codes used:

Language	Before .NET 4.0 Legacy codes	.NET 4.0 or later New codes
Simplified Chinese	zh-CHS	zh-Hans
Traditional Chinese	zh-CHT	zh-Hant

.NET before 4.0 used legacy (CHS/CHT) script codes. However, all .NET versions from .NET 3.0 up to .NET 4.6.1 accept both the legacy and the new codes. .NET 2.0 and earlier only accept the legacy codes. By default, Soluling uses legacy codes with .NET before 4.0, and new codes with .NET 4.0 or later. If you want to use the legacy codes even with .NET 4.0, turn them on. Right-click the Chinese language in the list and choose Use legacy codes. If you want to use the new codes even with .NET 3.x, turn them on. Right-click the Chinese language in the list and choose Use new codes.