Be able to import and reexport Across XLIFF. The following features of Across XLIFF must be supported:

• Import all internal tags
• Import comments
• Import length restrictions (to be used as specifified in TRANSLATE-822)
• Respect translate="no" attributes and set them to autostatus "blocked" in translate5

See linked Issue for wiki of Across with more information regarding the format.

Import length restrictions (TRANSLATE-822)

Here the specification of the length storage is still missing.

Respect translate="no" attributes

This should work already with the current XLF importer.

Import comments

Across comments are looking like:

<trans-unit id="id">
   <source>Hello World!</source>
   <ax:named-properties>
       <ax:named-property name="Comment">
           <ax:named-value ax:name="Author">Default supervisor</ax:named-value>
           <ax:named-value ax:name="Created">07/22/2015 10:10:10</ax:named-value>
           <ax:named-value ax:name="Annotates">General</ax:named-value>
           <ax:named-value ax:name="Title">Comment one title.</ax:named-value>
           <ax:named-value ax:name="Text">Comment one text.</ax:named-value> 
       </ax:named-property>
       <ax:named-property name="Comment">
           <ax:named-value ax:name="Author">WAN user</ax:named-value>
           <ax:named-value ax:name="Created">07/22/2015 15:01:00</ax:named-value>
           <ax:named-value ax:name="Annotates">Source</ax:named-value>
           <ax:named-value ax:name="Title">Comment two title.</ax:named-value>
           <ax:named-value ax:name="Text">Comment two text.</ax:named-value>
       </ax:named-property>
   </ax:named-properties>    
</trans-unit>

In Translate5 we have the following data fields, where the across fields can be mapped on import:

userGuid → remains empty for imported comments
userName → maps to ax:name="Author"
comment → maps to ax:name="Title" and ax:name="Text" and ax:name="Annotates" concatenated in nice way.
created → maps to ax:name="Created"
modified → maps to ax:name="Created"

• The comments appear as ususal in translate5 then. They can not be edited in translate5.
• Additional comments in translate5 are possible (stored with userGuid then).
• On Export: the old comments are contained in the skeleton file, only the comments with an userGuid must be loaded from translate5 and stored as new comments in across xlf. No data loss of the existing across comments. Translate5 comments are added annotated as "General" comments.

Visual example for the concatenation of Across's additonal data in translate5:

This was the Across title - if any
Here comes the Across comment text.
Comment annotates: Source

The last line contains the "Annotates" value, only if it is not "General".

Export Across XLF

The export of the comments in the across format is prepared. Currently across can not reimport comments in across XLF added as named properties. Therefore we discussed with our customer, that the comments are exported from translate5 as "analysisResult" which are imported by Across. The format will look like:

<ax:analysisResult>
    <ax:errorInfos>
        <ax:errorInfo>
            <ax:description>
                <ax:type>Comment</ax:type>
                
                <ax:title>Comment from AUTHOR (DATUM)</ax:title>
                
                <ax:explanation>
                    COMMENT
                </ax:explanation>
                
                <ax:instruction/>                
                <ax:examples/>
            </ax:description>
        </ax:errorInfo>
    </ax:errorInfos>
</ax:analysisResult>

Further we discussed with the customer that comments which were imported before from Across are not reexported again as "analysisResult".