Admin.XMLTranslationConfiguration.xml
The file Admin.XMLTranslationConfiguration.xml contains the configuration for the metadata that is applied when auto-generating targeted languages, defining source and pivot languages, and defining elements used for pre-translating content.
Changelog
| File version | SDL LiveContent Architect version | Notes |
|---|---|---|
| 1.0 | 10.0.0 | n/a |
Overview
This configuration file is accessible from the SDL LiveContent Architect 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 deletedElements - During the comparison of the current version with the previous version, the parameter
deletedElementsis used to specify whether the deleted elements should be removed from the compare result or not. - If the value of the parameter
deletedElementsisno, the deleted elements are removed from the compare result and are not be present in the pre-translated file. - The default value is
no
chgAttribute - The parameter
chgAttributeis used during the compare to specify whether the compare result should contain change attributes. The change attributes indicate for each element the type of changes that occurred between the two (2) versions. - If the value of the parameter
chgAttributeisno, the elements of the pre-translated file do not contain any change attributes. - The default value is
no
ResolutionRestriction - When Translation Management is enable on illustrations, the parameter
ResolutionRestrictioncan be used to limit the resolutions which must be created by Translation Management. - In the standard configuration, there are no resolutions specified. This means whenTranslation Management is enable on illustrations, all resolutions in the source language are also created by Translation Management in the target languages.
isNumericRegExp - The parameter
isNumericRegExpcan contain a regular expression (e.g. [0-9,\.,\,]+) which is used during the compare of two (2) numbers. - The standard configuration contains no regular expression to compare numbers.
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.
objectInfoOnRoot - The parameter
objectInfoOnRootis used for backwards compatibility. When the parameter isyes, the object information is added to the root node of the document in the following attributes:- id
- version
- lang
- srclang
- The default value is
no
<parameters> <parameter name="deletedElements">no</parameter> <parameter name="chgAttribute">no</parameter> <parameter name="ResolutionRestriction"> <!-- <Resolution ishvaluetype="element">VRESLOW</Resolution> <Resolution>High</Resolution> --> </parameter> <parameter name="isNumericRegExp"></parameter> <parameter name="MaxInheritedLanguageDepth">2</parameter> <parameter name="objectInfoOnRoot">no</parameter> </parameters> - During the comparison of the current version with the previous version, the parameter
- <GenerationScheme>
-
Contains all source and / or pivot languages.
The <FromLanguage> element defines the source language. In most case, you only have one source language and thus only one <FromLanguage> element. To define pivot languages (you have multiple source languages) configure multiple <FromLanguage> elements. If a specific language is specified in multiple <FromLanguage> elements, the configuration of the first <FromLanguage> element that is encountered is used for creating target language object.
The <ToLanguage> element defines the target language. Make sure to configure all target languages for each source language. Languages that are not configured are not generated by Translation Management.
<InfoShareTranslations> ... <GenerationScheme> <FromLanguage ref="en"> <ToLanguage ref="de"/> <ToLanguage ref="es"/> <ToLanguage ref="fr"/> <ToLanguage ref="it"/> <ToLanguage ref="ja"/> <ToLanguage ref="nl"/> </FromLanguage> </GenerationScheme> ... </InfoShareTranslations>
- <ComparisonElements>
-
Contains XPath expressions that indicate the elements that must be pre-translated.
The elements are compared in the order that they are specified. As a best practice, configure top-level elements first. For example, when a complete <section> element is identical, you want to pre-translate the entire element rather than all child elements separately.
<InfoShareTranslations> ... <ComparisonElements> <xPath>//*[contains(@class,' topic/section ')]</xPath> <xPath>//*[contains(@class,' topic/example ')]</xPath> <xPath>//*[contains(@class,' topic/shortdesc ')]</xPath> <xPath>//*[contains(@class,' topic/table ')]</xPath> <xPath>//*[contains(@class,' topic/row ')]</xPath> <xPath>//*[contains(@class,' topic/ol ')]</xPath> <xPath>//*[contains(@class,' topic/ul ')]</xPath> <xPath>//*[contains(@class,' topic/li ')]</xPath> <xPath>//*[contains(@class,' topic/sli ')]</xPath> <xPath>//*[contains(@class,' topic/title ')]</xPath> <xPath>//*[contains(@class,' topic/navtitle ')]</xPath> <xPath>//*[contains(@class,' topic/alt ')]</xPath> <xPath>//*[contains(@class,' topic/indexterm ')]</xPath> <xPath>//*[contains(@class,' topic/term ')]</xPath> <xPath>//*[contains(@class,' topic/tm ')]</xPath> <xPath>//*[contains(@class,' topic/fn ')]</xPath> <xPath>//*[contains(@class,' topic/xref ')]</xPath> </ComparisonElements> </InfoShareTranslations>