![]() original_empty.xlsx is the original file from the client.Note: if your Excel file has “Sheet1”, “Sheet2, and “Sheet3”, but the file to be translated is only in “Sheet1”, please make sure to delete “Sheet2” and “Sheet3”. Save them as “source.xlsx” and “target.xlsx” respectively. Prepare the source and target fileīecause we don’t have the xliff source file, we can copy the source text (column A) and target text (column B) to new Excel files. Here are the preparation and execution steps: A. In this case, we can use the Align Documents feature inside Trados. Trados cannot process the bilingual file directly but will import the whole Excel file as a source, and Trados cannot import the glossary, which is still in Excel format. We need to import both the bilingual file and the glossary file into Trados. No xliff file or other CAT tool-ready formats, only a plain bilingual Excel file. The bilingual file contains two columns (column A: source text, column B: target text) and >1k rows, while the glossary file contains thousands of entries. We have two Excel files: one bilingual file and one glossary file. So, how do we import the Excel files (the translated and glossary files) to CAT tools such as Trados to effectively and quickly check the translation using the built-in spellchecker, segment verifier, and terminology checker? Background Manually checking a translation against the glossary is very time-consuming and will possibly leaving the inconsistencies untouched. But, what if the file is a plain bilingual Excel file with a thousand rows, and you need to check the translation against a glossary in another Excel file? ![]() We only need to edit the file and send it back as a return package or target format. ![]() You don’t need any third party software to do all the corrections and create a brand new bilingual TMX file.Editing a prepared file as an xliff file is relatively easy. Later you can use this file to merge it into other translation memories of your choice. The third video (Terminology Check – Part II) focuses on how to modify the uploaded files and export them directly to a TMX file. After that, the report can be forwarded to translator to check all mistakes or to clients, after correction. For clients, these avoidable errors are usually easy-to-detect and can highly improve overall translation quality.Īfter running a terminology check or a Quality Assurance check, you can export a QA report to an HTML or and Excel file. The Quality Assurance functions is mostly used by Language Service Providers. You can also use customisable checklists to avoid forbidden words, for example. There are several options in XBench to detect untranslated segments, inconsistencies in source and target languages, numeric mismatches, terminology consistency and spelling errors. The second video (Terminology Check – Part I) is about Quality Assurance. Terminology search and check is mainly used by translators. It is especially useful when several translators are working on a project. Xbench can also check translated bilingual files against a glossary to verify the appropriate use of terminology created in-house or provided by the client. It is able to find terms in SDL Trados, Wordfast, TMX, RTF, XLIFF and SDLXLIFF, TTX, ITD and TXML files, among others. ![]() XBench can handle dozens of bilingual file formats, glossaries and translation memories (TMs). The first video below (Searching for Terminology) focuses on terminology search. Main functions of XBench are: terminology search, terminology check, QA check, QA report creation and TMX creation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |