1. HIDDEN CHARACTERS - Can we turn on hidden characters?
Not yet, it is in active development and will be in one of the next system update.
We will let you know as soon as it is in our instance.
3. WORKBENCH - How do I rearrange panels in the workbench?
For rearranging panels, click in the ribbon of the panel you want to move, then drag it to the top perimeter of the workbench until you see a blue line appear and drop it there, as below:
To put the other panel on the top right, click in its ribbon, drag up and to the right of the docked panel on the top, so that you see a smaller blue line in the top right-hand corner of the workbench, and drop it there.
It should then look like this:
5. MATCH PREPOPULATION - Is it possible when setting up a project to make fuzzy (anything above 70%) and 100% matches already appear in the target segment?
We would prefer not to pre-populate matches other than leverage and ICE because pre-translation is done based on TM content at the time of project creation. Since it might be a day or two until you start on the file, this would mean old information is populated.
Since we are working as a team on this project and colleagues might have generated more favorable or even better matches in the meantime, we want to avoid outdated material getting mixed in. Remember – XTM looks up the next 3 segments when you confirm a segment, so you’ll always have the latest and greatest matches.
7. QUOTES APOSTROPHES - Special characters -XTM uses straight quotes and apostrophes. Should I make them curly?
Yes, please make quotation marks and apostrophes curly. I’ve added them to my “custom shortcuts for special characters” to give them shorter shortcuts than the alt codes. You can add these shortcuts like this for any special character you use frenquently:
2. SEGMENTATION - If a sentence has been incorrectly segmented, can I merge the segments?
To an extent, yes. It is possible to merge segments that are separated by a dotted line. To do this, use the command Alt + Page up. Segments that are separated by a solid line cannot be merged (this is due to formatting in the source file), so you should instead adapt the translation to fit across the two segments. The shortcut can be found here:
In the example below, segments 216 and 217 could be merged, but 217 and 218 could not.
4. SAVING MY WORK - I stepped away from my desk and my session timed out. Has my work been saved?
Yes, XTM auto-saves on completion of a segment and every three seconds. Even if you are experiencing a spotty internet connection, XTM saves a local backup so you don’t lose your work.
6. TAGS - AUTO-INSERTION - How can I disable auto-insertion of inline tags?
In many cases, the formatting tags that apply in the source language will not apply in the target. Because not including tags can cause errors on exporting the final file, please ensure all tags are located somewhere in the segment. In the case of irrelevant formatting tags, these can go at the end of the segment. To have more control over the placement, you can change auto-insertion settings here:
8. WORKBENCH - ICONS - Meaning
|
|
Incomplete |
|
|
Draft: This status allows you to enter a translation in a segment and move on to the next one, without validating it. Segments with this status are saved in Translation Memory as “Not approved”. |
|
|
Completed |
|
|
Non-translatable: Non-translatable segments are marked with the letter “N” and displayed in the place of a populated match value. You can manually assign the “done” status to a non-translatable segment in the status context menu. The segment status can be changed to translatable at the stage of correction. |
|
|
At LQA step: To be corrected. This status is only visible to correctors. |
|
|
At LQA step: Incomplete in this and previous steps. This status informs a corrector that a segment was not finished in the previous step and does not require verification. |
|
|
Processing |
|
|
QA warning in the segment |
|
|
Indicates one of the XLIFF:doc statuses: -1: Rejected, 1: New, 2: Translated, 3: Proofed, 4: Validated |
|
|
Locked segment |
|
|
Alternative translation |
|
|
Not approved status of TM or Concordance match |
|
|
Accept and insert match |
|
|
Edit |
|
|
Remove |
|
|
Go to previous segment with comment |
|
|
Go to next segment with comment |
|
|
Add comment |
|
|
Add term |
|
|
Open Terminology |
|
|
Restore |
|
|
Comment has been added to the segment. If more than one comment has been added, still only one icon will be displayed. |
|
|
Non-translatable |
|
|
Repeated segment |
|
|
Insert match without inline tags |
|
|
Insert match with inline tags |
|
|
Segment won’t be saved in TM |
|
|
Leveraged match 100% |
|
|
In-context exact match |
|
|
Machine translation matched |
|
|
Unpopulated match |
The letters in the status box refer to the original matching type and have the following meaning:
|
LETTER |
MATCHING TYPE |
|
U |
Unmatched |
|
MT |
Machine translation matched |
|
M |
Matched, unpopulated |
|
ICE |
In-context exact match |
|
N |
Non-translatable |
The only change that you can make to the letter in the status box is to change it to “N”, otherwise it remains the same throughout the workflow.