Translation and Quotation Logs and Manifests
Translation Package Logs
When a translation package is prepared, a log file is included with it. The log contains information about:
• Translation package details about its organization, creator, timestamp, and source and target languages.
• Translation package contents list of the XLIFF and translatable files.
• Translation package information about each file, including its source and target identification, and security labels if present.
• If a dynamic document has a security label assigned to it, the security label displays under the document that was included in the translation package.
In the ZIP file, the log file name is constructed from an optional prefix, the package ID, the source and target languages, and the source revision. For example:
TRAN_0000000161_en_is_A.log
The manifest is also included in the translation package ZIP. The manifest is an XML file that manages the exchange of content with the vendors. It follows the same file naming method as the log file but appends the baseline ID. For example:
TRAN_0000000161_en_is_A_0000000543.xml
For information on the translation package naming convention, see
Creating a Translation Package.
When a translation package is created, the log file describes what was included, and possibly what was excluded, in the translation ZIP package. For example, it might contain a list of files that were skipped because they are already out for translation as part of another translation package, or not in the correct Preparation State, or documents contain out of date translation. In the following log file example, the exclusions are categorized and explained:
Translation package creation failed.
--------------------------------------------------------------------------------
Creation Time: 2014-05-09 15:05:43 GMT
Contact Person: Translation Coordinator
Package ID: TRAN_0000000161_en_is_A_0000000543
Organization: Company Organization
Context: 4WD Loader
Product
Export Folder: d:\translation\tobetranslated\Vendor-a
Source Language: en
Target Language: is
Number of Files: 3
--------------------------------------------------------------------------------
Content excluded from translation package (6):
Content already in translation (1):
Source Name: Doc 1.1 (task)
Source Number: 0000000770
Source Version: A.1, Released
Source Type: Publication Source
Package ID: TRAN_0000000770_en_is_A_0000000515
Content not in correct condition (5):
Source Name: Doc 5 (task)
Source Number: 0000000761
Source Version: A.1, In Work
Source Type: Publication Source
Reason: Object is not in preparation state
Source Name: Doc 3 (task)
Source Number: 0000000765
Source Version: A.1, Released
Source Type: Publication Source
Reason: Related object is checked out,
Related object is not in preparation state
Source Name: Doc 3.1 (task)
Source Number: 0000000766
Source Version: A.1, In Work
Source Type: Publication Source
Reason: Object is checked out, Object is not in preparation state
Source Name: Doc 2 (task)
Source Number: 0000000767
Source Version: A.1, Released
Source Type: Publication Source
Reason: Related object is checked out
Content has out of translation (1):
Source Name: Doc 2.1 (task)
Source Number: 0000000768
Source Version: A.2, Released
Source Type: Publication Source
Package ID: TRAN_0000000161_en_is_A_0000000543
--------------------------------------------------------------------------------
Content included in translation package (3):
Translation Name: Doc 5_is.1 (task)
Translation Number: 0000000860
Translation Version: A.1, In Work
Source Number: 0000000762
Source Version: A.1, Released
Source Type: Publication Source
Translation Name: Doc 1 (task)_is
Translation Number: 0000000859
Translation Version: A.1, In Work
Source Number: 0000000769
Source Version: A.1, Released
Source Type: Publication Source
Translation Name: PS1 (xliff)_is
Translation Number: 0000000861
Translation Version: A.1, In Work
Source Number: 0000000772
Source Version: A.4, Released
Source Type: Publication Source
You can also set up an email notification for the Core Translation Process if you wish to be notified when the packages are finished and available. The email notification includes information similar to the log file, such as organization, creator, timestamp, source language, target language, translation package ID, and the list of files that were included. If content has been excluded from the translation ZIP package, such as files that are already out for translation as part of another translation package, or not in the correct Preparation State, or documents contain out of date translation, those files are categorized and explained in the notification email.
For more information on setting up email notification, refer to
Workflow Email Notifications.
Translation Package Error Logs
If the translation package can't be created, a message is displayed on the Windchill confirmation banner with a link to the log file. The log file is placed in the folder where the ZIP would have been placed (specified by the Supported Vendors preference). The error log contains information about:
• Translation package organization, creator, timestamp, and target language.
• Reason for failure to create a translation package.
For example, in the following error log, the security level of documents in the structure did not meet the security clearance for the user requesting the translation package:
Translation package creation failed.
--------------------------------------------------------------------------------
Creation Time: 2014-05-09 14:49:59 GMT
Contact Person: Translation Coordinator
Organization: Company Organization
Context: 4WD Loader
Product
Export Folder: d:\translation\tobetranslated\Vendor-a
Source Language: en
Target Language: hu
--------------------------------------------------------------------------------
Errors (1):
Translation package failed; secure documents not permitted.
If you set up email notifications, the email will contain information similar to what is in the error log if the translation package can’t be created.
Import Package Logs
When a translation zip is returned from the vendor, it is placed in the folder specified by the External Import Folder preference. If there is a problem during the import process, a log file is placed in the External Import Folder containing the translation package ID and the reason for the failure.
Translation Dictionary Import Error Logs
When a translation package is imported for a service structure, the translated text values in a translation dictionary are populated with the associated translated XLIFF values. If there is an import error for a translation dictionary XLIFF, the import will fail and the error log will contain the errors.
Some of the more common errors are:
• The XLIFF has a parser error, such as invalid markup, or characters that are not Unicode.
• A type or attribute name is not defined in Type and Attribute Management in Windchill.
• An attribute name is defined in localizable_attset.xml, but it does not have an associated translated text attribute defined for an associated translation dictionary.
A type or attribute name is defined in localizable_attset.xml but is not set up as a translated text attribute with a translation dictionary.
• The source or target language is invalid.
For example, the following log entry reports invalid XML markup:
Import to Translation dictionary Error Summary.
---------------------------------------------------------------------------
Creation Time: 2015-10-26 09:26:46 GMT
Source Object: PS_Test_en (xliff)_zh-TW
Source Language: Unknown
Target Language: Unknown
---------------------------------------------------------------------------
'0000001425 - PS_Test_en (xliff)_zh-TW, A' has the following errors:
'PS_Test_en (xliff)_zh-TW' cannot be parsed; error at line 12, column 27
Element type "trans-unit" must be followed by either attribute
specifications, ">" or "/>".
For example, the following log entry reports an invalid language:
Import to Translation dictionary Error Summary.
--------------------------------------------------------------------------------
Creation Time: 2015-10-27 11:26:46 GMT
Source Object: PS_Test_en (xliff)_ko
Source Language: en1
Target Language: ko
--------------------------------------------------------------------------------
'0000001451 - PS_Test_en (xliff)_ko, A' has the following errors:
Custom language tag 'en1' does not have corresponding canonical language tag.
For example, the following log entry reports that an attribute is not defined:
Import to Translation dictionary Error Summary.
---------------------------------------------------------------------------
Creation Time: 2015-10-26 09:21:48 GMT
Source Object: PS_Test_en (xliff)_ar
Source Language: en
Target Language: ar
---------------------------------------------------------------------------
'0000001422 - PS_Test_en (xliff)_ar, A' has the following errors:
Unable to find logical attribute: "name2" with context:
"WCTYPE|wt.part.WTPart|com.ptc.sis.Base|com.ptc.sis.BaseDiv|
com.ptc.sis.PsSection|com.ptc.sis.PsRoot"
For example, the following log entry reports that an attribute does not have an associated translated text attribute defined in Type and Attribute Management.
Import to Translation dictionary Error Summary.
---------------------------------------------------------------------------
Creation Time: 2015-10-26 09:23:46 GMT
Source Object: PS_Test_en (xliff)_bg
Source Language: en
Target Language: bg
---------------------------------------------------------------------------
'0000001423 - PS_Test_en (xliff)_bg, A' has the following errors:
Attribute is not localizable: Type='wt.part.WTPart|com.ptc.sis.Base|
com.ptc.sis.BaseDiv|com.ptc.sis.PsSection|com.ptc.sis.PsRoot',
Attribute='number'
The error log uses the same naming convention as the XLIFF file followed by the date and time stamp for uniqueness; no logs are overwritten.
An attribute that appears in an exlude statement in the localizable_attset.xml configuration file, but is not defined, is not considered an error. If an attribute is specified in an exclude statement, and the attribute does not exist on the type being translated, then a warning is generated.
|
|
Use Generate Translation Document on the service structure or the parts list to generate an XLIFF for testing when you are setting up attributes in localizable_attset.xml for translation. The generated XLIFF contains only attributes that are correctly configured, so you can detect missing or undefined attributes.
|
The error logs are located at:
WT_HOME\logs\translation
You can decide how to handle the XLIFF causing errors:
• Make the corrections yourself.
Set the state of the translated XLIFF to the value of the In Translation State preference. Make the corrections the XLIFF entries, and then set the state to the value of the Translated State preference.
• Send the XLIFF out for translation again.
Set the state of the translated XLIFF to the value of the Pending State preference. Then you can generate the translation of the source XLIFF individually using the Create Translation Package option from the Action menu.
For more information, refer to:
Quotation Package Logs
When a quotation package is prepared, a log file is included with it. The log contains information about:
• Quotation package details about its organization, creator, timestamp, and source and target languages.
• Quotation package contents list of the XLIFF and translatable files.
• Quotation package information about each file, including its source identification and type.
In the ZIP file, file names are constructed using the same method as the translation package, except there is no baseline ID.
