Lilt supports the import, export, and placement editing of tagged text. This includes both within the CAT Editor itself, and in exported documents. This article describes:
Tags Overview
Lilt supports both structural tags (e.g. spacing, line breaks), and formatting tags (e.g. bold, italic, underline). Other arbitrary tags may not be shown, though they will be preserved.
Tags are not shown for unconfirmed segments, and can be ignored when translating text. The exception are formatting tags, which will be rendered in source segments.
Types of Tags
Tags may be shown in different colors to indicate different states:
- Gray: normal tag
- Green: currently selected tag (use the keyboard shortcuts to move the currently selected tag)
- White with green outline: the matching paired tag for the currently selected tag (use the keyboard shortcut to jump to the matching tag)
- Red: invalid position (nesting does not match source)
- Yellow: stray tag (this tag is part of a pair but its matching tag has been split into another segment)
Editing Tags
Tags are first shown in the editor after you confirm a segment (note: this can be turned off by deselecting 'Show tags for confirmed' in the top menu and selecting Tools).
Once a segment has been translated and confirmed, Lilt will automatically place the source tags into the translated text. For more information on our Research Team's work on tag projection, click here.
You can manipulate tag placement through keyboard shortcuts to move tags, allowing you to place tags without taking your hands off the keyboard. To learn more about tag related hotkeys click here.
If you prefer to use your mouse, tag placement can be accomplished through drag-and-drop. Simply mouse over the tag, click it, and drop it where the tag belongs.
You can click a tag for more information about its properties.
A few notes about tag manipulation:
- If you cannot see tags in the source segment, in the menu go to Settings and then select Tags: source: Always show source tags.
- Manipulating tags will unconfirm / unaccept a segment.
- Tags are automatically saved after being placed. No additional saving is required.
- Tags cannot be edited or deleted.
Reviewers can manipulate tags and text the same way that Translators can modify confirmed segments.
Tag validation
We have automatic checks to determine whether tags are positioned and nested correctly. When a tag is invalid, it shows as red and does not save automatically. If you are sure that tag placement is correct in a particular case, you can override the validation rules by confirming or accepting the segment. When a segment is confirmed / accepted, all tags will be saved.
Tags auto-propagation
Tags are auto-propagated with 100% TM matches. This means that if you change tag positions in a segment and another segment has the same source tags, the target tags will be propagated to match. Note that you must have forward and/or backward auto-propagation turned on in "Settings." 100% or 101% TM matches with the same source text but different source tags will be degraded to 99% matches, while a 100% or 101% TM match with matching source tags is leveraged, the target tags will be leveraged as well.
Tag QA
Issues with tag placement are typically found around punctuation, whitespace, or numbers. It's easy for translators / reviewers to miss these "typo-like" tag errors so there is a set of Tag QA checks run against commonly found tag errors. When the Run Tag QA option is selected from the Tools menu, the editor runs a set of tag rules against segments containing tags. Just hover over the tag to see information about the tag error.
Summary of the Tag QA rules
|
ERROR MESSAGE |
TRIGGER |
EXAMPLE |
|
Tags may be misplaced around punctuation |
A tag has a leading or trailing punctuation mark in the source, but not the target OR a tag has an extra leading or trailing punctuation mark in the target |
Source: <b>Hello,</b> from Lilt Target: </b>Bonjour</b>, de Lilt --- comma should be contained in tag |
|
Tags may be misplaced around whitespace |
A tag has a leading or trailing space in the source, but not the target OR a tag has an extra leading or trailing space in the target |
Source: <b>Hello there </b> Target: <b>Bonjour</b> --- second tag missing leading space |
|
Tags do not wrap identical content in the target |
If the span wrapped by a tag pair in the source appears exactly in the target, but it is not wrapped by the tag pair. |
Source: <b>Intel Pentium</b> works well Target: <b>Intel Pentium fonctionne bien</b> --- "Intel Pentium" appears exactly in the target, and likely should be wrapped by the same tag pair |
|
Tags co-located in the source are not co-located in the target |
Two tags have the same position in the source, but they don't have the same position in the target. |
Example: <1><2>hello -- tags 1 and 2 are both at position 0 in the source then <1>bonjour<2> would violate, but bonjour<1><2> would be ok |
|
Missing text between tags |
There is a paired tag with no text between the tags in the target but not in the source. |
Source: <b>Hello</b> Target: <b></b>Bonjour -- tag span is empty |
|
Mismatched tags at beginning of sentence |
Tag has position 0 in the source but not position 0 in the target OR Tag has position 0 in the target but not in the source |
Source: <1><2>Hello Target: <1>Hello<2> -- tag 2 should be highlighted |
|
Mismatched tags at end of sentence |
Tag has position (source_length - 1) in the source but not position (target_length - 1) in the target OR Tag is at end of target but at end of source |
Comments
0 comments
Please sign in to leave a comment.