Admin.XMLTranslationConfiguration.xml
The Admin.XMLTranslationConfiguration.xml file contains the configuration for the metadata that is applied when auto-generating target languages and defining source and pivot languages.
Changelog
| File version | Content Manager version | Notes |
|---|---|---|
| 1.0 | 10.0.0 | n/a |
| 2.0 | 12.0.0 | The XML schema has been significantly re-worked. Parameters The The The |
| 2.1 | 13.0.0 | The XML schema supports the |
Overview
This configuration file is accessible from the Content Manager Web Client. Select .
XML elements
- <parameters>
-
The
<parameters>element contains a number of parameters used to configure a variety of settings.The following table provides an overview:
Name Description ResolutionRestriction - When Translation Management is enabled on illustrations, the parameter
ResolutionRestrictioncan be used to limit the resolutions that must be created by Translation Management. - In the standard configuration, there are no resolutions specified. This means when Translation Management is enabled on illustrations, all resolutions in the source language are also created by Translation Management in the target languages.
MaxInheritedLanguageDepth - The target languages can be specified in the metadata of the current object but can also be inherited from requested and inherited languages of the parent objects. The code to inherit the languages recursively retrieves the parents objects and adds extra languages. The parameter
MaxInheritedLanguageDepthspecifies how many levels are to be used. - Since a typical object has three (3) levels (map, topic, illustration), the default value is
2.
<parameters> <parameter name="ResolutionRestriction"> <!-- <resolution ishvaluetype="element">VRESLOW</resolution> <resolution>High</resolution> --> </parameter> <parameter name="MaxInheritedLanguageDepth">2</parameter> </parameters> - When Translation Management is enabled on illustrations, the parameter
- <translationstatuses>
-
The
<translationstatuses>element contains references to the statuses that are used by the Translation Management and Translation Organizer.The following table provides an overview:
Type Description Initial The status is used when the Translation Management and Translation Organizer create objects (such as topics or maps) in a new language. Newly created objects are created in this status. The status should exist and be configured as an initial status for the TRANSLATORSERVICE role. InTranslation The status is used to indicate that the object was sent to a translation management system for translation. TranslationInReview The status is used to indicate that the object is translated (translation was retrieved from the Translation Management system). The translation needs to be reviewed and approved. TranslationApproved The status is used to indicate that the object translation was approved. TranslationRejected The status is used to indicate that the object translation is not accepted and the object has to be resent for translation. <translationstatuses ishcondition="ISHType in ('ISHMasterDoc', 'ISHModule')"> <status type="Initial" ishref="VSTATUSTOBETRANSLATED"/> <status type="InTranslation" ishref="VSTATUSINTRANSLATION"/> <status type="TranslationInReview" ishref="VSTATUSTRANSLATIONINREVIEW"/> <status type="TranslationApproved" ishref="VSTATUSTRANSLATED"/> <status type="TranslationRejected" ishref="VSTATUSTRANSLATIONREJECTED"/> </translationstatuses> <translationstatuses ishcondition="ISHType in ('ISHLibrary')"> <status type="Initial" ishref="VSTATUSTOBETRANSLATEDCUSTOM"/> <status type="InTranslation" ishref="VSTATUSINTRANSLATIONCUSTOM"/> <status type="TranslationInReview" ishref="VSTATUSTRANSLATIONINREVIEWCUSTOM"/> <status type="TranslationApproved" ishref="VSTATUSTRANSLATEDCUSTOM"/> <status type="TranslationRejected" ishref="VSTATUSTRANSLATIONREJECTEDCUSTOM"/> </translationstatuses>
- <translationobject>
-
Defines how target languages, that are generated by Content Manager's Translation Management, get the necessary metadata values.
All language-level metadata fields that are defined as mandatory must be configured, otherwise Content Manager's Translation Management fails to generate the target language objects.
The
<ishfields>element specifies the metadata fields that must be copied from source. If this configuration relies on certain conditions, theishconditionattribute can be used to provide them.<translationobject> <copyfromsource> <ishfields ishcondition="ISHType in ('ISHMasterDoc', 'ISHModule', 'ISHLibrary')"> <!-- Copy system fields --> <ishfield name="FISHWORDCOUNT" level="lng"/> <ishfield name="FISHCONDITIONS" level="lng"/> <ishfield name="FISHLINKS" level="lng"/> <ishfield name="FISHHYPERLINKS" level="lng"/> <ishfield name="FISHIMAGELINKS" level="lng"/> <ishfield name="FISHVARINUSE" level="lng"/> <ishfield name="FISHVARASSIGNED" level="lng"/> <ishfield name="FISHFRAGMENTLINKS" level="lng"/> <ishfield name="FISHTARGETS" level="lng"/> <!-- Copy mandatory fields --> <ishfield name="FAUTHOR" level="lng"/> <ishfield name="FREVIEWER" level="lng"/> <ishfield name="FTRANSLATOR" level="lng"/> </ishfields> <ishfields ishcondition="ISHType in ('ISHIllustration', 'ISHTemplate')"> <ishfield name="FAUTHOR" level="lng"/> <ishfield name="FREVIEWER" level="lng"/> <ishfield name="FTRANSLATOR" level="lng"/> </ishfields> </copyfromsource> </translationobject>The following condition names can be used for determining which fields need to be copied from the source:Condition name Description ISHType The type of the object: ISHMasterDoc,ISHModule,ISHIllustration,ISHTemplateandISHLibrary.FMAPID The unique identifier of the logical level (= LogicalId).VERSION The version number of the object. DOC-LANGUAGE The language(s) of the object.
FSOURCELANGUAGE The source language of the object.
FRESOLUTION The resolution of the illustration.
EDT The element name of the EDT (e.g. EDTXML)ISHUserGroup The element names of the user groups that have write access to the object (e.g. VUSERGROUPSYSTEMMANAGEMENT)
- <languagepaths>
-
Provides allowed translation paths.
The
<languagepath>element defines the source language - target language combination that is allowed in the system. The order is important because it defines the priority of the language combination. For instance, if you define a 'nl - fr' combination before a 'en - fr' one, then when creating a target language object in French the system will prefer to use the Dutch object as a source if available. Only if the object is not available in Dutch, the system will use the English object as a source.<languagepaths> <languagepath from='en' to='aa'/> <languagepath from='en' to='ab'/> <languagepath from='en' to='af'/> ... <languagepath from='en' to='yo'/> <languagepath from='en' to='zh'/> <languagepath from='en' to='zu'/> </languagepaths>