Segment identifier (SID) support
Segment identifiers (SIDs) are marker tags that define the context for translatable segments.
| File type | First version with SID support |
|---|---|
| Java Resources File Type | 10.4.5 |
| Custom XML (Embedded Content Processor) File Type | 11.1 and 11.2 |
| Custom XML (Legacy Embedded Content) File Type | 11.3 |
| JSON File Type | 11.4 |
SID implementation details
- Searches the starting and ending tags of the source asset for a unique identifier.
- Activates SID in WorldServer with the unique identifier.
- Associates the unique identifier with one or more TM matches.
The nature of the SID depends on your requirements. Some customers choose SIDs that are unique for each segment. This is not a WorldServer requirement. Other customers reuse SID values across different source text. The most important thing to determine is what format you will use for the SID. You can then create a tool that generates SIDs consistently and uniquely per segment.
- Defines how SID markers should be used in customer content.
- Leverages only properly defined SID markers.
- Enforces boundaries defined by proper SID usage.
- Associates defined SIDs with translation units.
- Enforces supported uniqueness requirements.
- Leverages SID content against SID TM entries.
- Completely defining how SIDs are represented in customer content.
- Embedding SID markers into customer content.
- Enforcing the proper use of SID markers within content.
SIDs in translation memories (TMs)
Through the implementation of the SID as a standard attribute, WorldServer can offer attribute options for SID values. Users can sort and filter TM entries by SID values and view SID values on the Translation Memory: <name> page.