Editing project TM and verification settings
You can edit the TM settings and verification settings of an existing project.
About this task
- TM settings are used during translation (when you apply TM lookups) and after your translations are confirmed and automatically updated in the TM.
- Verification settings are used during translation in Trados Online Editor and signal any tag or QA inconsistencies. Verification settings are also used by the Automated QA task which runs after the Translation task and the Linguistic Review task are completed.
Procedure
- Connectez-vous à Trados Enterprise (en cliquant sur ce lien : http://languagecloud.sdl.com/fr/lc).
- Accédez à l'affichage Projets.
- Select the check box corresponding to the project you want to edit.
- Select Open.
- Select the Settings sub-tab.
- Select Configuration > Batch tasks.
- Specify the TM settings:
- Under Pre-Processing Settings, configure how TMs are applied by configuring the following:
- Choose a value in the Minimum match value box.
- Choose an option from the Translation overwrite mode box:
- Overwrite existing translation if better match found (default value) - For this option, unlocked segments (including confirmed segments) are overwritten, while unlocked Perfect Match segments and locked segments are not overwritten.
- Keep existing translation
- Always overwrite existing translation - For this option, Perfect Match segments (both locked and unlocked) are overwritten, while other locked segments are not overwritten.
- Overwrite except Perfect Match translation - For this option, unlocked segments (including confirmed segments) and locked segments are overwritten, while unlocked Perfect Match segments are not overwritten.
- Choose an option from the After applying translations box: Confirm 100% matches (default value), Confirm context matches (default value), Lock 100% matches; Lock context matches.
- Choose an option from the When no match found box: Leave target segment empty (default value), Copy source to target.
- Select Advanced Settings and decide whether you want to enable the Report Cross-File Repetitions option.
- Select Configure penalties and specify a numeric value for each standard penalty: Missing formatting penalty, Different formatting penalty, Multiple translations penalty, Auto-localization penalty, Text replacement penalty, Alignment penalty, Character-width difference penalty. The maximum value a standard penalty can have is 20. The Auto-localization penalty applies to auto-substituted dates, times, numbers and measurements. The Text Replacement penalty applies to auto-substituted variables, acronyms and alphanumeric strings.
- Select Configure penalties and specify a numeric value for each TU status penalty: Translated, Translation Rejected, Translation Approved, Sign-off Rejected, Signed Off, Not Translated, Draft. The maximum value a translation unit penalty can have is 20.
- Select Filters and configure a penalty filter for all non-matching TUs. Select Add New Filter, and then give your filter a name and a numerical value. Under Conditions select the criterion based on which filtering can be performed: Last modified on, Last modified by, Last used on, Last used by, Usage count, Created on, Created by, TU confirmation level, Source segment, Target segment, Source segment length, Target segment length, Number of tags in target segment, Number of tags in source segment. Depending on the criterion you choose, you must further select or enter values. To create a complex filter, use the operator check boxes and add as many conditions as you need. Select Save filter.
- Under Report locked segments in analysis, select one of the options:
- Select Report locked segments in analysis > Exclude from analysis report to have locked segments completely ignored from the Analysis report. The total number of reported segments will not include any locked segments.
- Select Report locked segments in analysis > As a separate category to have locked segments appear as a standalone category in the Analysis report. If the locked segments are repetitions, the locked segments are reported neither in the Repetitions category, nor in the Cross-File Repetitions category of the Analysis report.
- Select Report locked segments in analysis > Using the original match category to have locked segments distributed across the available fuzzy bands. If the locked segments are repetitions, the locked segments and their repetitions are reported neither in the Repetitions category, nor in the Cross-File Repetitions category of the Analysis report.
- Under Update Translation Memory, configure how TMs are updated throughout the project workflow depending on the status of the segments.
- Choose an option from the If target segments differ box:
- Merge translation units = Replace (update) only the TU (from which a match was retrieved for the edited TU) with the latest available translation AND keep the other duplicates as they are. Use this option to have multiple translations for the same source together with Multiple Translation Penalty = 0.
- Add new translation units = Add translations as new TUs to the TM. Specify the status of the TUs (which will be added) under Segment status. This means that the existing TUs in the TM are not overwritten.
- Overwrite existing translation units = Delete all TUs (which have the same source, all TU duplicates) and keep only the last added TU (the latest available translation). Use this option to prevent inconsistent translations.
- Leave translation units unchanged = Keep the existing TUs and do not add any new ones.
- Keep most recent translation units = Replace (update) only the most recent TU (from which a match was retrieved for the edited TU) with the latest available translation AND delete all other duplicates.
- Choose an option from the Segment status box: Translated, Translation Approved, Signed Off, Draft, Translation Rejected, Sign-off Rejected.
- Select Update Translation Memory fields, and add fields and their values. Note that if you edit the field templates and change their type, this will impact all the project templates and projects where the field template is used. Moreover, the TMs which use these field templates are not updated and the Translation Memory Update task will fail. Therefore, if you change the field type, in the Settings > Update Translation Memory Fields section of your project template or project, edit the field values or reset the field.
- Select Filters and configure a hard filter which automatically excludes all non-matching TUs. A hard filter completely filters out non-matching TM results. If a TM match does not match the filter conditions, it is completely excluded from lookup results. Select Hard Filter, and then, under Conditions select the criterion based on which filtering can be performed: Last modified on, Last modified by, Last used on, Last used by, Usage count, Created on, Created by, TU confirmation level, Source segment, Target segment, Source segment length, Target segment length, Number of tags in target segment, Number of tags in source segment. Depending on the criterion you choose, you must further select or enter values. To create a complex filter, use the operator check boxes and add as many conditions as you need. Select Save filter. For more information on hard filters, consult this topic.
- Choose an option from the If target segments differ box:
- Under Pre-Processing Settings, configure how TMs are applied by configuring the following:
- Specify the verification settings:
- Under Verification > Tag Verifier, configure which tags should be checked and which ignored. Select Advanced Settings to specify different warnings to the elements which do not behave as expected: Note, Error, Warning.
- Under Verification > QA Checker, configure how checks are performed at global level (All languages), at target-language level or both.
- The following settings are available at global level (All languages): Segments Verification, Segments to Exclude, Inconsistencies, Punctuation, Numbers, Word list, Regular Expressions, Trademark check, Length verification.
- The following settings are available at target-language level: Punctuation, Numbers, Word list, Regular Expressions, Length verification.
For Punctuation, Numbers, Word list, Regular Expressions, and Length verification, which can be set at global level and/or at target-language level, the enforcement logic goes as follows:- If users specify these settings at global level, and keep the default values for these settings at target-language level, then the global level apply to all target languages.
- If users specify these settings at target language level, then these values apply.
- If users specify these settings at both global level, and target-language level, then the target-language level values take precedence over the global ones.
Depending on your needs, select either All languages or a specific target language, and configure the settings:- Segments Verification: segments you forgot to translate, segments which are identical in the source and the target, various inconsistencies.
Field Options Basic Settings Forgotten and empty translation Select the Check for forgotten and empty translation check box to be notified that your translation is incomplete. Compare source and target segments - Select the Source and target are identical check box to be notified that you have not translated a segment.
- Decide whether you want to have target segments checked based on their length and use the Longer by and Shorter by fields to configure the length value.
Ignore segments fewer than # words Decide whether you would like to ignore some segments based on their number of characters or words. If you choose the latter option, configure the number of words. Advanced Settings For each of the above elements, specify different warnings to mark how severe the unexpected behavior is: Note, Error, Warning. - Segments to Exclude: exclude segments per translation status.
- Inconsistencies: repetitions, non-edited fuzzy matches.
Field Options Basic Settings Check for inconsistent translations Select the check box to have inconsistent translations highlighted. Check for repeated words in target Select the check box to be notified of repetitions. Check for unedited fuzzy matches Select the check box when you enter fuzzy matches without additional edits. Advanced Settings For each of the above elements, specify different warnings to mark how severe the unexpected behavior is: Note, Error, Warning. Ignore numbers and Ignore case If you selected Check for repeated words in target, decide whether you want to ignore numbers and case from the repetition count. Only check confirmed segments If you selected Check for unedited fuzzy matches, decide whether you want to narrow down your search to confirmed segments. Only check if match scores below If you selected Check for unedited fuzzy matches, decide whether you want to narrow down your search to a match score of your choice. Specify the percentage of the match score. - Punctuation: extra spaces, brackets, capitalization.
Field Options Basic Settings End punctuation Decide which type of end punctuation should be checked for inconsistencies: - Check that source and target end with the same punctuation
- Check for Spanish punctuation
- Select the Check for unintentional spaces before check box and insert the punctuation marks which prompt a check.
Extra dots and spaces Specify the cases where extra dots and extra spaces should be checked for inconsistencies: - Check for multiple spaces
- Check for multiple dots
- Ignore ellipsis dots
- Check for extra space at the end of target segments
Capitalization check Specify the cases where capitalization should be checked for inconsistencies: - Check capitalization of initial letters
- Check consistency of global capitalization
Check for brackets Select the Check brackets check box to have brackets verified for inconsistencies. Advanced Settings For each of the above elements, specify different warnings to mark how severe the unexpected behavior is: Note, Error, Warning. - Numbers: numbers, dates, times, measurements
- Word list
Field Options Basic Settings Word list Toggle on Word list to add the wrong and correct form of words you want checked. Advanced Settings Specify a warning to mark how severe the unexpected behavior is: Note, Error, Warning. Search whole words only Select the check box to restrict the search to whole words. Ignore case Select the check box to perform the search irrespective of the word case. - Regular Expressions
Field Options Basic Settings Regular Expressions Toggle on Regular Expressions to add the default conditions which automatically check the differences between source and target content. Advanced Settings Specify a warning to mark how severe the unexpected behavior is: Note, Error, Warning. - Trademark check - Keep the trademark list as such or add more trademark symbols to the list.
Field Options Basic Settings Trademark check Toggle on Trademark check to add the trademark symbols which are automatically identified. Advanced Settings Specify a warning to mark how severe the unexpected behavior is: Note, Error, Warning. - Length verification: limits, character counts, context.
Field Options Basic Settings Check length limitation Choose an option: - Check if target segments are within file specific limits
- Check if target segments are longer than character count - Add a numeric value for the character count.
Contexts Choose an option: - Check all segment contexts
- Check the following contexts (one per line) - Add the contexts in the box.
Advanced Settings Specify a warning to mark how severe the unexpected behavior is: Note, Error, Warning.
- Under Verification > Terminology Verifier, configure how cloud terminology is checked in Trados Studio and in Trados Online Editor. Terminology Verifier is enabled by default, but you can toggle it off. To export your Terminology Verifier settings in a
*.jsonfile, select the three-dot icon, and then select Export settings. To import Terminology Verifier settings as a*.jsonfile, select the three-dot icon, select Import settings, and load your file. The Terminology Verifier settings apply to a specific termbase included in the project. When you export the Terminology Verifier settings attached to a specific project termbase, you can import the settings only into the same project termbase. You cannot export the Terminology Verifier settings associated with a termbase and import them in a project where the Terminology Verifier settings are associated with a different termbase.For Trados Studio, terminology verification is performed only on the first cloud termbase included in the translation engine. For terminology verification to work correctly in Trados Studio, you must access the advanced settings and configure the Studio Settings section.For Trados Online Editor, terminology verification is performed on all cloud termbases in the translation engine. Terminology is validated interactively when confirming a segment in Trados Online Editor. Moreover, the settings specified as part of terminology verification are taken into consideration as part of the Translation Automated QA Check task and the Linguistic Review Automated QA Check task.Under Check for the following, select or clear the available settings. The settings under the Check for the following section apply to both Trados Online Editor and Trados Studio.- Possible non-usage of target terms - Select this option to check source segments for known terms. Where a term is found, the corresponding target segment is examined to ensure that the correct term translation (from the termbase) has been used. By default, faulty usage is marked by a Warning message.
- Terms which may have been set as forbidden - Select this option to check that you are not using any terms expressly forbidden by this termbase. The information about whether a term is forbidden comes from the termbase itself. By default, faulty usage is marked by an Error message. Note that you must enable this option if you want to further enable the Studio Settings > Picklist Fields option and specify the fields which indicate whether a term is forbidden or allowed.
- Terms without the target term equivalent - Select this option to check source segments for known terms for which there is no translation in the termbase. By default, faulty usage is marked by a Note message.
Under Exclude the following, select or clear the available settings. The settings under the Exclude the following section apply to both Trados Online Editor and Trados Studio.- PerfectMatch units - Select this option to exclude locked segments translated by PerfectMatch from the verification.
- Exact matches - Select this option to exclude segments translated with a 100% translation memory match from the verification.
- Fuzzy matches down to 99% - Specify the value down to which fuzzy matches are excluded from the verification. Use the percentage box to specify a percentage match cut-off point. For example, if you specify a limit of 90%, then segments with a 90-99% match will be included in the check and segments with a 75-89% match will be excluded.
- Locked segments - Select this option to exclude locked segments from the verification
Under Studio Settings, specify the available settings. As the name suggests, the settings below apply to Trados Studio only.- Enable recognition of two-letter terms - Select this option to search for two-letter terms if your source file contains two-letter acronyms, such as the "UN" (United Nations).
- Termbase - The name of the first termbase listed in the translation engine is displayed here in read-only mode.
- Picklist Fields - Select the descriptive field which indicates if a term is forbidden or allowed. To enable this option, you must first select the Terms which may have been set as forbidden check box.
- Under Verification > TQA Profile, consult the selected TQA profile or select another one. Once a project contains a TQA profile, you can choose another TQA profile, but you cannot remove TQA profiles from your project. To edit the TQA profile (severities or values), select the link and start editing it.
Note: If you delete a TQA profile which is already included in a project template or a project, you can consult the TQA profile (severities or values) in read-only mode by accessing it from the Settings tab of your project template or project.
- Select Save.
Related reference