Setting Up Dynamic Documents

Additional Capabilities > Service Information Management > Configuration Guide > Setting Up Translation > Setting Up Dynamic Documents

Dynamic Document Requirements

Dynamic documents need two attributes to work with translation. The values for the Translate Attribute and Document Language Attribute translation preferences are set by default to the reusable attributes PTC_DD_TRANSLATE and PTC_DD_LANGUAGE respectively. Dynamic documents, including graphic dynamic documents, need to have these reusable attributes for translation.

Attribute	Description	Value
PTC_DD_TRANSLATE	Determines whether a dynamic document should be translated. The Translate Attribute preference identifies this internal attribute name.	Set to Yes to translate. Other conditions, such as state, must also be met to include the document in a translation package. Set to No to exclude the document from translation. A missing attribute or empty value is presumed to mean No.
PTC_DD_LANGUAGE	Defines the language of the content. The Document Language Attribute preference identifies this internal attribute name.	Set to the abbreviation for the source language, such as the language or locale code. The attribute must use a code that can be mapped to one defined by the Source Languages enumeration. For more information, see Source Languages.

Dynamic Document Notes

• We recommend you use PTC_DD_TRANSLATE and PTC_DD_LANGUAGE as the attributes for Translate Attribute and Document Language Attribute preferences.

• WTDocument types of documents are not supported for translation.

• You must use autonumbering when you create or burst dynamic documents for translation to work properly. See Dynamic Document Numbering for information.

• If a compound dynamic document has PTC_DD_TRANSLATE set to Yes and it’s in the Preparation State, all the child documents must also have PTC_DD_TRANSLATE set to Yes and be set to the Preparation State to include the entire compound document in the translation package.

If any child documents of a compound document have the PTC_DD_TRANSLATE attribute set to No, then those child dynamic documents will be excluded from the set.

• Inserting, copying and pasting, or dragging a translated dynamic document, including an XLIFF, into a service structure is not permitted.

• Copying and pasting a dynamic document into a service structure for a different language other than the current locale is permitted provided it is a source document in a service structure.

Setting Up Bursting Rules

You can put dynamic documents into Windchill from Arbortext Editor using the PTC Server connection. Bursting configuration files need to be stored in Windchill to ensure that they are assigned the proper type. The .bcf file should have the same base name as the document type to maintain the association with the dynamic documents for that type. For more information, see Specifying the Burst Configuration Location in the Arbortext Help Center.

You can set the PTC_DD_TRANSLATE and PTC_DD_LANGUAGE attribute values in bursting rules when putting dynamic documents into Windchill.

The following example looks for a translate attribute on topic.

The next example looks for an xml:lang attribute on topic.

For more information, refer to Assigning PTC Server Properties in the Arbortext Help Center.

Metadata rules are processed for translated dynamic documents when they are imported from the translation vendor into Windchill. Only metadatarule and twowaymetadatarule elements are supported; all other rules in a burst configuration file are ignored, including object type, naming, and location rules.

For instance, consider the following example rule for axdocbook.bcf:

If the type attribute of the source dynamic document has the value installation, then the InformationType attribute on the source dynamic document will also be set to installation when the document is burst into Windchill. If the document is translated to Spanish, the type attribute value on the book element would be translated to instalación. When the translated Spanish document is imported from the vendor into Windchill, the InformationType attribute value will also be set to instalación.

When you are creating bursting rules, be aware of the following:

• If you want the dynamic document name to display its translated value, then use the value WC_NAME_ATTR for the metadata attribute, in either metadatarule or twowaymetadatarule.

For more information, refer to Assigning PTC Server Properties in the Arbortext Help Center.

• If atidefaults.bcf disables two-way metadata rules, translated attribute values will not be applied to translated dynamic documents when they are imported from the translation vendor.

• If you use a text entity in an XML attribute that is mapped to a Windchill property, the text entity needs to be declared in the document's internal subset (rather than the document type).

When dynamic document translations are imported, you can choose to turn off updating their metadata (for example, in cases where you want metadata in the source language only). The com.ptc.tml.updateMetadataOnTranslatedDocuments property controls the metadata import behavior by setting Yes (the default) to permit updates or No to suppress updates. Add the com.ptc.tml.updateMetadataOnTranslatedDocuments property into the codebase\wt.properties file.

Metadata rules must already exist in burst configuration files for metadata updates to succeed.

Translated attribute values for dynamic document can be viewed from the information page in Windchill and in Arbortext Editor using Object > Properties.

For more information on setting up translation, see Translation Configuration Process.

Publishing Dynamic Documents

If you intend to publish translated documents, you will need to set up WVS and an APE Worker. For information on setting up dynamic document publishing, refer to Configuring Publishing for Arbortext Authored Dynamic Documents.

When publishing from a service structure, the Publish Representation dialog box offers a choice of languages from the Language Pairs translation preference. This does not apply to dynamic documents.

Was this helpful?