PTC Arbortext Content Delivery Publishing and Loading > Using Publishing and Loading > Running PxTAL > Loading Multilingual Data
  
Loading Multilingual Data
In Windchill Service Information Manager 10.2 M022 CPS10, 10.2 M032 CPS05, or 11.0 F000 CPS05, translated objects such as PDF, IEXML, and Graphics files have two timestamps: one timestamp for the translation, and one timestamp for the source or authoring language. This allows the bundles to be loaded in any order, regardless of locale.
In PTC Arbortext Content Delivery, a new multilingual property named multilingual.bundle.with.source.timestamp.support is introduced to facilitate the loading of the multilingual bundles in any order, regardless of locale, for full or incremental data loading.
To take advantage of this feature, you must use bundles generated from Windchill Service Information Manager 10.2 M022 CPS10, 10.2 M032 CPS05, or 11.0 F000 CPS05, and make sure the value of the multilingual.bundle.with.source.timestamp.support property is set to TRUE (the default value for the property in PTC Arbortext Content Delivery 6.3 M001 and later).
If the property is set to FALSE, then the system behaves as it did for PTC Arbortext Content Delivery 6.2. In this case, bundles must be loaded with the following restrictions, regardless of the Windchill Service Information Manager version used to generate the bundles:
• The authoring language bundles must be loaded first, before any translated bundles are loaded.
• The update or incremental translated multilingual bundles must be loaded with the same translation timestamp value as the most recently loaded authoring language.
• Starting with the PTC Arbortext Content Delivery 7.1.3.0 release, a bundle containing a checksum value will be loaded over a bundle that does not have a checksum. However. a bundle without a checksum value will not be loaded over a bundle that has a checksum value. Bundles with checksum values are published using Windchill Service Information Manager 7.1.3.0 or later.
• The checksum value is used to validate the data version, regardless of the bundle locale. The following table shows how the checksum value is used:
Current
Need To Update
Comment
metaChecksum
Checksum
Collected Date
Source
Metadata
X
X
N/C
No
No
Checksum was not changed so no need for collected date
X
Y
-1
No
No
Only the source was updated
X
Y
0
No
No
X
Y
1
Yes
No
Y
X
-1
No
No
Only metadata was updated
Y
X
0
No
No
Y
X
1
No
Yes
Y
Y
-1
No
No
Both source and metadata were changed
Y
Y
0
No
No
Y
Y
1
Yes
Yes
The table uses the following indications:
• X – The old checksum value
• Y – The new checksum value
• -1 – Older than the previous collected date
• 0 – Same as the previous collected date
• 1 – Newer than the previous collected date
• N/C – No need to check
Additionally, a new property named multilingual.bundle.cleanup.stale.authoring.language.data determines whether authoring language information elements are deleted while loading incremental bundles from a different locale with a more recent authoring timestamp. If the property is set to TRUE (the default value for the property in PTC Arbortext Content Delivery 6.3 F000), then existing authoring language information elements are deleted. If the property is set to FALSE, the authoring language information elements are retained, though they are not current.
The multilingual.bundle.cleanup.stale.authoring.language.data property is honored by the system only when the multilingual.bundle.with.source.timestamp.support property is set to TRUE.
Both properties are found in the TAL.properties file, in the following location: <INS_HOME>/INS_SW/Config/Applications/DataProcess/Config/Common/Templates/TAL