When you find a translation issue in Xbench that you wish to fix, select it, press Ctrl+E and the Matecat editor will open automagically at that segment so that you can edit it!ġ. The Matecat project will open in Xbench where you will be able to run QA on your translations. xbp file to launch Xbench and load the Matecat job. Click the Xbench icon that appears next to the address bar.ģ. Open a Matecat job in the Matecat online editor.Ģ. August 2017 29.Instantly run QA with ApSIC Xbench on cloud-based CAT tools The ApSIC Xbench Chrome Extension will allow you to instantly run QA with ApSIC Xbench 3.0 on your Matecat, Memsource, Transifex, Smartcat, or Crowdin projects with just one click.ġ. Create a QA rule in Xbench that checks if mobile device has always been translated with Mobilgerät.Īuthor Doreen Schoon-Hammermann Posted on 23.Create a QA rule in Xbench that checks if there is a non-breaking space between z.Create a QA rule in Xbench to automatically spot a blacklisted word.Use LQE feedback from the past as quick reference in XBench (save them as tab separated txt file).Īdd German corpora from to your Xbench project for quick German usage reference (shortcut: Ctrl+Alt+Backspace) Hands-on task: Simple RegEx QA rules in Xbench.highlight blacklisted words like Anweisungen. Use word macros to spot errors directly in MS Word, e.g.Create own rules in Xbench to reflect client feedback.Implement major errors from LQE reports and updates from client as Xbench rule to avoid them in the future.
This is especially useful if you need to implement changes across a large number of files. Jump directly to a sentence/string in a specific file for quick change implementation (Ctrl+E).You can export all files in a project to ONE single Word file for proofreading.
XBENCH 3.0 SOFTWARE
Export it to an MP3 file, listen to it with F4, a transcription software that allows easy forwarding and rewinding of audio files (which unfortunately VoiceReader is not capable of). Highlight the entire target text or parts of it. Listening to text helps to find grammar issues that passed the spell check. Using this approach, I often find mistakes that would otherwise have slipped under my radar. Step 3: Listening spot check with TTS software Linguatec VoiceReader or Chrome TTS plug-in Copy erroneous segments to review template file as a reference for the translator. Implement changes in the translated file.
XBENCH 3.0 PLUS
Step 2: Duden Korrektor Plus Spell Check in MS WordĮxport the translated files to a Word file: Click Ctrl+W in Xbench to export the file (exclude ICE matches and duplicate sentences if needed). It contains a checklist and four list items: Nice solution, Implemented, To check, Translator feedback necessary.Īfter having implemented changes for a certain segment, mark it done in Xbench by pressing Ctrl+M. Also copy segments that need translator feedback to this Word file. I collect my changes in a Word file: Copy implemented segments to a word file (to be sent to translator for acceptance).
Optional: I usually do not do a check for keyterms mismatches as this usually yields a lot of false positives. Maybe this is of help for someone who is struggling to streamline his or her reviewing workflow. My reviewing routine is something I want to share with interested people working in the same area. With this background, I was able to gather some routine in this area. Translated words up to now: around 2 million words, reviewed words up to now: around 900.000 words. I have been working as a freelance translator and reviewer in the localization business for about 9 years. Here are my best practices for reviewing UI and help translations in software localization using Apsic Xbench 3.0, Duden Korrektor Plus and text-to-speech software and for implementing client feedback to constantly improve translations.
0 kommentar(er)
