Use this sheet to specify the options.
Specifies what resource items are written to the localized resource files. Possible values are:
|Different||If checked Sisulizer does not write resource items to the localized resource file if the value of the item is the same as the original value. Value is not written even if the user has entered the value in the edit sheet if it equals to the original value.|
|Translated||If checked Sisulizer writes to the localized resource file all those resource items that has a translation (i.e. a translation has been given in the edit sheet).
This is the default value.
|All||If checked Sisulizer writes all resource items to the localized resource file. If no translation is entered in the edit sheet the original value is used. The structure of the localized resource files are identical to the original ones. Only the translated values are different.|
If you keep the default value, Translated, Sisulizer can greatly optimize the size of the resource files. This also will fully enable the build-in language fallback of the platform where you application runs. If you choose All no runtime language fallback is done but fallback is done by Sisulizer on build process. We recommend to use either Translated of Different to enabled optimization and language fallback of the platform. When localizing XAML this options is only used with resource dictionaries. All other XAML resources will always contain all items.
Together Right to left layout radio group and Set reading order property check boxes specify how user interface should be modified when localizing to bi-directional languages such as Arabic, Hebrew and Persian. Depending on your platform you should set the check boxes in a different way.
Check Set reading order property check box to make Sisulizer to add RightToLeft attributes to bi-directional forms. This sets the reading order of all components of the forms. It also mirrors everything (form and its components) except container components (Panel, GroupBox, TabPage). To mirror container you have three choices:
If you choose option #1 you should mirror the forms and controls on run time. You can use Sisulizer.WindowsForms.Translate.FlipControl function to mirror containers.
If you uncheck Set reading order property check box you have to set the RightToLeft property of all forms on runtime if the active language is a bi-directional languages.
|WPF and Silverlight||
Check Set reading order property check box to make Sisulizer to add FlowDirection attribute to bi-directional XAML resources. This sets the reading order and to mirrors the user interface. If you uncheck Set reading order property check box you should to set the FlowDirection property of all forms on runtime if the active language is a bi-directional languages.
Right to left layout radio group is disabled.
If checked Sisulizer adds the resource items alphabetically to the resource string node. If unchecked the items are added in the same order as they appear in the original file. Only used with .resx resources.
If checked Sisulizer normalizes the white spaces in the element contents. This means removing multiple soft white spaces between each words. For example if you have following XAML
<Label>This is a sample text.</Label>
NewTool will extract the value as "This is a sample text." instead of "This is a sample text.".
If checked Sisulizer combines Run, Span and text elements that are sub elements of TextBlock. For example if we have
<TextBlock>This is a <Span>simple</Span> <Run>sample</Run>.</TextBlock>
then what is scanned depends in the value of the check box.
This is a <Span>simple</Span> <Run>sample</Run>..
All sub elements of TextBlock are scanned a single string that contains tag names. You can change the order of each sub element.
This is a
All sub elements of TextBlock are scanned individually using one row per each part. There is no logical connection between each sub elements and you cannot change the order of the elements.
If checked Sisulizer makes resources in satellite assemblies private.
If checked Sisulizer deletes the created .resources files after the build process.
If checked Sisulizer adds language specific part into the names of all localized resources. If unchecked Sisulizer adds culture specific part into the names of those resources that require it. The standard resource types such resources are ResX resources and XAML resources required the language part.
Let's have an example. You have embedded image resource called MyApplication.MyImage.png. When you read the image data on runtime you use "MyApplication.MyImage.png" name. If you check the check box Sisulizer will rename the resource in the localized satellite assembly file. The German assembly file will have MyApplication.MyImage.de.png" and Japanese file will have "MyApplication.MyImage.ja.png". In order to correctly read the image data your code must change the name it uses depending on the active locale. If you do not want this make sure that the check box is unchecked. In that case the satellite assembly files will all have the resource with the same name ("MyApplication.MyImage.png").
This edit field specifies the parameters passed to assembly linker application (AL.exe). AL is used to create the localized satellite assembly files. Type the parameter values that you want to pass to the assembly linker, or right click to choose parameter template from a popup menu. The menu contains following templates:
|Company name||/comp[any]:"text"||Name of the company that wrote the assembly|
|Copyright||/copy[right]:"text"||Copyright message of the assembly|
|Description||/descr[iption]:"text"||Description of the assembly|
|Key file||/keyf[ile]:"filename"||File containing key to sign the assembly|
|Key container||/keyn[ame]:"text"||Key container name of key to sign assembly|
|Product name||/prod[uct]:"text"||Product name|
|Product version||/productv[ersion]:"text"||Version number of the assembly|
Choose Clear to clear the parameters field.
Read more about .NET localization.