To localize the enumeration values, you have to load into the system the translation strings with the right scope, just like for all the other value types.

For example, to localize the 'archiveObject.priority' attribute in Italian, you have to load the following translations:

<!-- Enumerations captions for priorities -->

<StringDesc Language="it" Scope="EnumCaption" Name="high" Value="Alta" />

<StringDesc Language="it" Scope="EnumCaption" Name="medium" Value="Media" />

<StringDesc Language="it" Scope="EnumCaption" Name="low" Value="Bassa" />

After having loaded these string translations, both the controls and the result list show the localized values ('Alta', 'Media' and 'Bassa').

Note that, in listing, the DirectoryStyle displays the already localized strings.

This can cause unwanted results when using enumeration in a Converter.

For example, look at the following ValueConverter:

<Rectangle Fill="{Binding Path=[archiveObject.priority], Converter={StaticResource ValueConverter},

  ConverterParameter=high?Red:medium?Yellow}"

  Width="15" Height="15" Margin="0 0 4 0" />

This converter won't work, because it receives the value to convert already translated (for example, 'Alta'), which does not match the configured condition ('high').

To configure the Converter in a language-independent way, you have to define the condition using the index of the enumeration as defined into the GN4 schema (starting from 0). This way:

<!-- priority enum: 0=low, 1=medium, 2=high -->

<Rectangle Fill="{Binding Path=[archiveObject.priority], Converter={StaticResource ValueConverter},

  ConverterParameter=2?Red:1?Yellow}"

  Width="15" Height="15" Margin="0 0 4 0" />

For more information about the ValueConverter syntax, see http://tech.teradp.com/tech/html/gn4/docs/VSdoc/index.html#frlrfTeraDPGN4CommonConvertersValueConverterClassTopic.html.