Tags represent non-translatable text; some CAT tools refer to them as placeholders. Non-translatable text can represent variables, special formatting, formal names, code, etc.
Tags must be copied from source to target to ensure formatting and variables are preserved correctly in the exported target file.
Display tags with Ctrl+Shift+E from the web editor, Ctrl+Shift+T from the desktop editor, or from the menu.
There are two types of tags:
Represent formatting that spans across a section of text. For instance, a section of text in a segment might have a different font than the rest, or a section of text is highlighted, etc..
Paired tags have an opening and a closing.
Insert paired tags by selecting the text to be tagged and clicking F8.
Represent, for instance, the position of a footnote in a segment or a joined segment.
Insert unpaired tags by clicking on the spot in the text and clicking F8.
Unpaired tags are singular.
Joined Segments tags are a special type of unpaired tag.
Tags are not included in the word count when calculating an analysis. Each join tag is replaced with one space.
Incorrect tagging can lead to improper translations. If tags are missing in the target, Memsource attempts to auto-complete when the completed target file is being generated. If missing or incorrect, add tags manually to the target and in as close a position and order as possible when compared to the source.
If tags are removed from a source, QA can not correctly check it against the target. Aerror is presented on file export with no QA tag warnings.
If this occurs, follow these steps:
Export the job to a bilingual TMX file.
Import the TMX file into a temporary TM.
Re-import the original file.
Pre-translate the new job using the temporary TM.
Check the pre-translation results, and run QA against the new job with enabled.
If successful, the temporary TM can be populated by confirming the segments and it can be imported into the main TM.
Tags are inserted through either the Edit menu or keyboard shortcuts F8 or CTRL+ALT+# to specifically number the tag and Ctrl+, to insert by section.
To edit target tag content, follow these steps:
Press CTRL+SHIFT+E in the web editor, Ctrl+Shift+T or F2 in the Editor for Desktop or from the menu, select Tags , Expand Tags.
Tag content is presented.
Click a tag to be edited.
Edited tags are displayed in yellow to indicate differences from a source tag.
To insert a custom tag or custom paired tag into the target:
From the Tags , Create Custom Tag or Create Custom Paired Tag.menu, select
The custom tag is displayed as yellow instead of blue.
Custom tags can only be added to file formats supporting tags in the completed file (such as HTML).
The Quality Assurance feature can be used to ensure tagging is in place and accurate.
If a project has been set up to check tags by the Project Manager, missing or incorrect tags will prevent the export of a valid translated document.
As tags are used to mark parts of a text with different formatting most of these format changes are obvious. Common tags are different fonts, font sizes, or colors. Some tags, such as style changes, are minor and may not be as visible.
Imported files containing many unseen tags may generate theerror due to too much metadata. This easily occurs with the import of complex file types such as PDF that have been converted to text formats.
When importing text files it is suggested:
If converting a PDF file using an OCR program, save as plain or unformatted text. Open the file in a text editor to apply required formatting such as adjusting fonts, font size, colors, columns, spacing, etc.
There are a number of tools available for cleaning text files of extra code. CodeZapper is recommended.
Use theoption when importing text files. This option attempts to remove all tags considered unnecessary from the source text imported for translation. This is an automated process and may remove required formatting. If using this option, compare the completed file with the original document to ensure required formatting is in place.