Such arguments resemble discussions about religion and serve no purpose. I am not interested in getting involved in arguments about what various tools can do and trying to prove that one is better than another. I will show you SDL Trados Studio can do it too (much better than that)". Many times I have found number errors (particulary added numbers) that Trados QA has not caught, particularly in memories provided to me, presumably because the previous translator has configured the number checking to reduce all the false positives. For example, it flags this: 122,45 € > €122.45 as an error because it doesn't like the currency symbol stuck to the number. Depending on how Studio is configured, it either throws up lots of false positives or it misses errors. Number checking is far better than in Studio, even with the Number Verifier plugin installed. When your extension is then built and published, change the language of Dynamics 365. Create a directory named Translations, in the root of the extension, and place the translated xliff file there. All potential errors are shown grouped together across the entire project and can be ignored en masse instead of having to tediously look at hundreds of individual messages. When the dependencies are set, you can add xliff files in your current project that translates the object captions of the referenced extension. QAD 6.5.8 is compatible with ttx, tmx, XLIFF and bilingual STF files. XBench (see below) can import TBX files and convert them to tab-delimited TXT files. Xbench 2.8 is the only tool that interacts with a wide range of file types (27). QA is much more configurable than in Trados Studio, with checklists that can be programmed to look for common dictation errors (such as the French word "principe" being translated as "principal" instead of "principle") and that can be configured in ways that Studio termbases cannot. PlusTools is a free MS Word add-in that can handle multiple tasks. reducing the number of tags/codes in a source text (see below) and ApSIC Xbench for editing TMs. All I want in my CAT tool termbase are entries relating to the current project (for automatic QA) and nothing else.Īs regards QA, spellchecking is far better than in any CAT tool because only one instance of questionable spelling is flagged and, if necessary, these can be corrected en masse in the CAT tool. MemoQs own internal file format is a variety of XLIFF. I don't want these loaded into a CAT tool termbase because it would slow it down to a crawl and every source segment would flag entries that would be irrelevant to the current project. My XBench termbase is kept loaded into live memory and currently contains 1,795,217 entries. original documents are not converted into xliff files. XBench serves two completely unrelated functions, terminology management and QA. an extraction of IATE), organise translation memories and archive finalized.
0 kommentar(er)
