Admin.XMLTranslationConfiguration.xml

The Admin.XMLTranslationConfiguration.xml file contains the configuration for the metadata that is applied when generating target languages and defining source and pivot languages.

Changelog

File versionContent Manager versionNotes
1.010.0.0n/a
2.012.0.0

The XML schema has been significantly re-worked.

Parameters deletedElements, chgAttribute and objectInfoOnRoot are no longer supported.

The ComparisonElements section and the isNumericRegExp parameter are moved to the pretranslation extension configuration.

The InfoshareTranslationMgmts section is replaced by the translationobject section.

The GenerationScheme section is replaced by the languagepaths section.

2.113.0.0

The XML schema supports the translationstatuses element allowing to configure statuses used by Translation Management and Translation Organizer.

Overview

To access this configuration file in Organize Space, select the Settings tab, then the XML Settings subtab, and then the Translation Settings subsubtab.

XML elements

<parameters>
The <parameters> element contains the ResolutionRestriction parameter. When Translation Management is enabled on illustrations, you can use this parameter to limit the resolutions that Translation Management must create. The standard configuration specifies no resolutions. This means that when Translation Management is enabled on illustrations, all resolutions in the source language images are also created by Translation Management in the target language images. By setting the parameter, you restrict which resolutions are created for target language images.
<parameters>
  <parameter name="ResolutionRestriction">
    <!--
    <resolution ishvaluetype="element">VRESLOW</resolution>
    <resolution>High</resolution>
    -->
  </parameter>
</parameters>
<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:

TypeDescription
InitialThe 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.
InTranslationThe status is used to indicate that the object was sent to a translation management system for translation.
TranslationInReviewThe 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.
TranslationApprovedThe status is used to indicate that the object translation was approved.
TranslationRejectedThe 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.

Your configuration must minimally list all language-level metadata fields that are defined as mandatory, otherwise Content Manager's Translation Management will fail 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, the ishcondition attribute 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 nameDescription
ISHTypeThe type of the object: ISHMasterDoc, ISHModule, ISHIllustration, ISHTemplate or ISHLibrary.
FMAPIDThe unique identifier of the logical level (= LogicalId).
VERSIONThe 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.

EDTThe element name of the EDT (e.g. EDTXML)
ISHUserGroupThe element names of the user groups that have write access to the object (e.g. VUSERGROUPSYSTEMMANAGEMENT)
<languagepaths>

Provides allowed translation paths.

Each <languagepath> element defines the source language - target language combination that is allowed in the system. If there are multiple <languagepath> elements with the same to attribute value, the order of those elements matters, because it defines the priority of the language combination. For example, imagine you define a nl-to-fr combination before an en-to-fr combination. In that case, when creating a target language object in French, the system will prefer to use the Dutch object as a source, when 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>