|
Write options |
Use this sheet to specify the options that are used when writing localized ResX files.
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.
Specifies the write options that are used when writing localized resource files.
| Value | Description |
|---|---|
| Add FlowDirection property if needed or Add RightToLeft and RightToLeftLayout properties if needed |
If checked, Soluling adds the flow direction/right to the left property into the localized files if needed. |
| Write stripped white spaces | If checked, the localized resource files' string values will contain the same leading and trailing white spaces as the original resource files. This option is only enabled if you have checked to Remove leading and trailing white spaces in XAML options. |
| Write comments | If checked, the comment values are written into the localized resource files. |
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.
Copyright © 2010-2024 Soluling