Translation Manifest view
A translation manifest has several important features that distinguish it from its language manifest children.
First, a translation manifest recognizes the source language as its default. That means that if the content is in English, the language identified in the translation manifest is also English.
Second, a translation manifest takes into account the complexity of tracking multiple languages and the multiplication of objects based on the number of required languages. Use the view to see all map dependencies: submaps, topics, images, resources, and ditavals referenced with ditavalref. Treat it as a spreadsheet of your original snapshot. You can add, remove, reorder, or filter grid columns. You can create a custom view or sort grid column content.
Column item |
Cycle |
Description |
---|---|---|
Title |
Authoring |
Object's title at time of snapshot, such as Tools |
Original status |
Authoring |
Object's status at time of snapshot, such as |
Type |
Authoring |
Object's type, such as task |
Original Revision |
Authoring |
Object's revision number at time of snapshot, which appends to the filename, such as 2 |
Managed By |
Translation |
Object's related language manifest (LM) and its related translation manifest (TM) that is the primary manager of that object, even if the object is part of and sent with multiple LMs. The 3 possible value types are:
|
Localization Initial Status |
Translation |
Virtual status of corresponding object in Translation at time of initial
snapshot, such as Note: While this status column is not included by
default, you can add it.
|
ID |
Authoring |
Object's identifier, such as abc0123456789012 |
Filename |
Authoring |
Object's filename, followed by a semicolon and its revision number, such as abc0123456789012.dita;2 |
Filepath |
Authoring |
Object's filepath, such as /content/authoring/abc0123456789012.dita |