Difference between revisions of "Automating Translation QA"
(→Automation tools: full proposal) |
|||
| Line 5: | Line 5: | ||
There are various ways in which CATs (computer-aided translation tools) provide more automation for quality control. Some of that can be reused for automated quality control of OOo translations. | There are various ways in which CATs (computer-aided translation tools) provide more automation for quality control. Some of that can be reused for automated quality control of OOo translations. | ||
| − | + | == Support in translation tools == | |
| − | Tools such as Alchemy Catalyst support checking if there are duplicate mnemonics for UI elements. Implementing such a function in a translation tool such as [https://open-language-tools.dev.java.net/ Open Language Tools] doesn't seem difficult as it is possible to encode all the required parameters in the XLIFF format. | + | Tools such as Alchemy Catalyst support checking if there are duplicate mnemonics for UI elements. Implementing such a function in a translation tool such as [https://open-language-tools.dev.java.net/ Open Language Tools] doesn't seem difficult as it is possible to encode all the required parameters in the XLIFF format. Additional checks that can be done using CATs are: |
| − | Note that agreeing on a single translation tool and standard translation format (XLIFF) and translation memory format would be an additional advantage. | + | * Checking for completeness of numbers & tag translation (Are numbers transfered to target? Are numbers in the correct format? Is the number, order and/or type of tags unchanged?) |
| + | * Checking for blacklisted keywords (like checking for "Package Manager" after changing the terminology to "Extension Manager) | ||
| + | * Terminology check using an approved glossary | ||
| + | * Spell-checking | ||
| + | * Style, grammar-checking (for controlled vocabulary, punctuation etc.) | ||
| + | |||
| + | Note that agreeing on a single translation tool and standard translation format (XLIFF) and shared translation memory format would be an additional advantage. | ||
| + | |||
| + | == Support in testtool scripts == | ||
| + | |||
| + | The automated scripts in testtool can and probably should duplicate some of the functionalities covered by CATs, especially mnemonics uniqueness check, and probably other checks as well. | ||
| + | |||
| + | A spell-check (using OOo spelling dictionary for the build language) of the translation could discover possible encoding problems. This could be automated as well. | ||
| + | |||
| + | == Support in standalone tools == | ||
| + | |||
| + | Some specialised tests can be developed using standalone grammar checkers like [http://www.danielnaber.de LanguageTool] that can be customized for many of Sun-supported languages and others. | ||
Revision as of 18:21, 19 December 2006
Contents
Automation tools
There are various ways in which CATs (computer-aided translation tools) provide more automation for quality control. Some of that can be reused for automated quality control of OOo translations.
Support in translation tools
Tools such as Alchemy Catalyst support checking if there are duplicate mnemonics for UI elements. Implementing such a function in a translation tool such as Open Language Tools doesn't seem difficult as it is possible to encode all the required parameters in the XLIFF format. Additional checks that can be done using CATs are:
- Checking for completeness of numbers & tag translation (Are numbers transfered to target? Are numbers in the correct format? Is the number, order and/or type of tags unchanged?)
- Checking for blacklisted keywords (like checking for "Package Manager" after changing the terminology to "Extension Manager)
- Terminology check using an approved glossary
- Spell-checking
- Style, grammar-checking (for controlled vocabulary, punctuation etc.)
Note that agreeing on a single translation tool and standard translation format (XLIFF) and shared translation memory format would be an additional advantage.
Support in testtool scripts
The automated scripts in testtool can and probably should duplicate some of the functionalities covered by CATs, especially mnemonics uniqueness check, and probably other checks as well.
A spell-check (using OOo spelling dictionary for the build language) of the translation could discover possible encoding problems. This could be automated as well.
Support in standalone tools
Some specialised tests can be developed using standalone grammar checkers like LanguageTool that can be customized for many of Sun-supported languages and others.
