Ocelot does not read software identifiers in <iws: /> namespace elements

Description

If software identifiers are encoded as &lt;iws:segment-metadata sid="IDS_123">&lt;iws:segment-metadata> then Ocelot does not read and display them.

Environment

None

Activity

Show:
Phil Ritchie
February 20, 2017, 2:20 PM
Edited

This is categorized as a feature request because the iws namespace is not core XLIFF but rather an approved extension mechanism.

Phil Ritchie
February 20, 2017, 2:50 PM
Edited

A proposal here would be to read these iws:segment-metadata[sid] attribute values and display them in a new main grid column. Would this be acceptable?

Note: this would only be implemented for XLIFF 1.2 files.

Chase Tingley
February 21, 2017, 7:27 PM
Edited

Right, this is WorldServer specific. (This is the older "IdiomXLIFF" variant, not the SDLXLIFF produced when FTS filters are in use.)

I think the iws:segment-metadata/@sid attribute should probably be considered another way of providing the trans-unit/@resname attribute, since they perform the same function. Also, this should arguably be fixed in Okapi's XLIFF filter, not in Ocelot (where we'd have to scrape it with regular expressions or something).

Chase Tingley
May 10, 2017, 7:34 PM

The attached

shows a couple of segments with SIDs coming from WorldServer's Java Properties filter. (Search for "key1" and "key2".)

The segment-metadata also contains an iws:status element that gives match status ("fuzzy"), which is relevant for OC-93.

Assignee

Marta Borriello

Reporter

Francesco Pugliano

Labels

None

Components

Priority

Blocker