Su búsqueda retornó 2 resultados.

Resumen: In the January/February 2021 issue I wrote about the surprising quality and ease-of-use of the OPUS-MT and OPUS-CAT products.1 When I interviewed developer Tommi Nieminen, an experienced professional translator and MT researcher, about the OPUS tools, he said—much to my surprise—that according to his testing, his products (the locally installed MT and the connector to CAT tools) are as good as or better than any other trainable machine translation (MT) engine.2 Except one: ModernMT.

Resumen: 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. 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).