Andy (Steve) De George
be103da07e
* net-current-v30plus-md.md * net-current-v40plus-md.md * tla2sharptla-ui-md.md * tla2sharptla-uiautomation-md.md * tla2sharptla-winclient-md.md * tla2sharptla-xaml-md.md * tlasharptla-ui-md.md * tlasharptla-uiautomation-md.md * tlasharptla-winclient-md.md * tlasharptla-xaml-md.md * fix warnings
6.1 KiB
title, ms.date, ms.custom, description, helpviewer_keywords, ms.assetid
| title | ms.date | ms.custom | description | helpviewer_keywords | ms.assetid | ||
|---|---|---|---|---|---|---|---|
| Localization Attributes and Comments | 03/30/2017 | devdivchpfy22 | Learn how to use localization attributes and comments. |
|
ead2d9ac-b709-4ec1-a924-39927a29d02f |
Localization Attributes and Comments
WPF Localization API to indicate which resources are to be localized. Free-form comments are any information that the application author wants to include.
Add Localization Comments
If markup application authors have requirements for specific elements in XAML, such as constraints on text length, font family, or font size, they can convey this information to localizers with comments in the XAML code. The process for adding comments to source code is as follows:
-
Application developer adds localization comments to XAML source code.
-
During the build process, you can specify in the .proj file whether to leave the free-form localization comments in the assembly, strip out part of the comments, or strip out all the comments. The stripped-out comments are placed in a separate file. You specify your option using a
LocalizationDirectivesToLocFiletag, eg:<LocalizationDirectivesToLocFile>value</LocalizationDirectivesToLocFile> -
The values that can be assigned are:
-
None - Both comments and attributes stay inside the assembly and no separate file is generated.
-
CommentsOnly - Strips only the comments from the assembly and places them in the separate LocFile.
-
All - Strips both the comments and the attributes from the assembly and places them both in a separate LocFile.
-
-
When localizable resources are extracted from BAML, the localizability attributes are respected by the BAML Localization API.
-
Localization comment files, containing only free-form comments, are incorporated into the localization process at a later time.
The following example shows how to add localization comments to a XAML file.
<TextBlock x:Id = "text01"
FontFamily = "Microsoft Sans Serif"
FontSize = "12"
Localization.Attributes = "$Content (Unmodifiable Readable Text)
FontFamily (Unmodifiable Readable)"
Localization.Comments = "$Content (Trademark)
FontSize (Trademark font size)" >
Microsoft
</TextBlock>
In the previous sample the Localization.Attributes section contains the localization attributes and the Localization.Comments section the free-form comments. The following tables show the attributes and comments and their meaning to the localizer.
| Localization attributes | Meaning |
|---|---|
| $Content (Unmodifiable Readable Text) | Contents of the TextBlock element cannot be modified. Localizers cannot change the word "Microsoft". The content is visible (Readable) to the localizer. The category of the content is text. |
| FontFamily (Unmodifiable Readable) | The font family property of the TextBlock element cannot be changed but it is visible to the localizer. |
| Localization free-form comments | Meaning |
|---|---|
| $Content (Trademark) | The application author tells the localizer that the content in the TextBlock element is a trademark. |
| FontSize (Trademark font size) | The application author indicates that the font size property should follow the standard trademark size. |
Localizability Attributes
The information in Localization.Attributes contains a list of pairs: the targeted value name and the associated localizability values. The target name can be a property name or the special $Content name. If it is a property name, the targeted value is the value of the property. If it is $Content, the target value is the content of the element.
There are three types of attributes:
-
Category. This specifies whether a value should be modifiable from a localizer tool. See xref:System.Windows.LocalizabilityAttribute.Category%2A.
-
Readability. This specifies whether a localizer tool should read (and display) a value. See xref:System.Windows.LocalizabilityAttribute.Readability%2A.
-
Modifiability. This specifies whether a localizer tool allows a value to be modified. See xref:System.Windows.LocalizabilityAttribute.Modifiability%2A.
These attributes can be specified in any order delimited by a space. In case duplicate attributes are specified, the last attribute will override former ones. For example, Localization.Attributes = "Unmodifiable Modifiable" sets Modifiability to Modifiable because it is the last value.
Modifiability and Readability are self-explanatory. The Category attribute provides predefined categories that help the localizer when translating text. Categories, such as, Text, Label, and Title give the localizer information about how to translate the text. There are also special categories: None, Inherit, Ignore, and NeverLocalize.
The following table shows the meaning of the special categories.
| Category | Meaning |
|---|---|
| None | Targeted value has no defined category. |
| Inherit | Targeted value inherits its category from its parent. |
| Ignore | Targeted value is ignored in the localization process. Ignore affects only the current value. It will not affect child nodes. |
| NeverLocalize | Current value cannot be localized. This category is inherited by the children of an element. |
Localization Comments
Localization.Comments contains free-form strings concerning the targeted value. Application developers can add information to give localizers hints about how the applications text should be translated. The format of the comments can be any string surrounded by "()". Use '\' to escape characters.