Or you can just select the engine you might know is likely to produce the best results right in your translation environment. Although, for a small or mid-sized language services provider, the latter option might very well be interesting.īy the way, before you apply your preferred MT engine to your text, you can run a test that compares several outputs in the Intento Console. I have a hard time imagining a single translator building and maintaining several different MT engines that they would like to access through a tool like Intento. Why? Because the main differentiator is access to customizable MT engines, including AutoML, DeepL (with its terminology training component), Google, Microsoft’s Custom Translator, ModernMT, and many others. While the second option is attractive, my sense is that the first will be the most popular with translators. You can find the different options and offerings listed at inten.to/localization-teams. (All fees that are payable to the original MT providers are paid by Intento.) Localization Expert for $75/month: This will provide access to all non-customizable and customizable engines with your own credentials, including the option of selecting one of 16 domains and up to one million characters per month with the possibility of incremental payments for overage use.Localization Starter for $25/month: This will provide access to all non-customizable engines, including the option of selecting one of 16 domains and up to one million characters per month.The newly unveiled plans that are relevant to individual translators include: Then you’ll need one of the plans that Intento offers to access its ready-made connectors to its MT partners.
#Lingvanex vs deepl free#
For each of these tools, a free plugin is provided (either readily integrated or separately installable) that enables you to connect to Intento. So, how does one work with Intento? First, you’ll need to work with either Lingotek, memoQ, Trados, Smartcat, Wordfast Anywhere, Wordbee, or XTM if you want to bring MT suggestions via Intento into your translation environment. I didn’t know many of these MT providers existed, either.)Ĭlearly not all of them will be relevant (Fujitsu’s Zinrai engine, for instance, supports only EnglishJapanese), but there’s a good chance that some engines will be relevant for your language combination, and an even greater likelihood that there’ll be more than you think. (And, yes, it’s also fine if you don’t use MT at all.) But for others, it might be rather attractive to have only an API-based agreement with one entity (in this case, Intento) to connect you to engines such as AISA, Alibaba, Amazon, Apptek, Baidu, CloudTranslation, DeepL, Elia, Fujitsu, Globalese, Google, GTCOM, IBM Watson, iFLYTEK, Kakao Developers, Kawamura International, Kingsoft, Lesan, LINDAT, LingvaNex, Microsoft, ModernMT, Naver, NTT Com, Pangeanic, Process 9, Prompsit, PROMT, Rozetta, RWS, SAP, SYSTRAN, Tencent, Tilde, XL8, Yandex, YarakuZen, Youdao, or Zinrai. You might be well situated if you’re already using a customizable MT engine such as OPUS-MT or ModernMT. The same might be true for languages that are well supported, particularly when it comes to different kinds of text or subject matter. For instance, if you work in a language combination that’s not particularly well supported by MT engines, the performance between different texts you translate may differ widely. Why exactly would you want to have access to so many engines? The answer to that depends on a number of variables.
#Lingvanex vs deepl how to#
It might be okay if you just want to use one or two MT engines, but if you would like to access 10 or 20, this becomes a real headache (and honestly untenable-if only because you don’t even know many of these engines exist or how to jump the language barriers of the many East Asian specimens to connect to them). What are the pros and cons of using a tool like Intento that allows you simultaneous access to dozens of machine translation (MT) engines? (When I say “a tool like,” I’m really not being particularly accurate because it’s actually the only tool that does what it does.) If you’ve used generic MT engines like those from Google, Microsoft, or DeepL via your translation environment, you know that it’s rather tedious to create an application programming interface (API) key on their respective websites and then enter it into the application you’re using.
0 kommentar(er)
