You are currently working on UAT 

MT plugins provided as default

I just noticed that memoQ provides some 15 plugins for MT as default (although of course you need to obtain accounts, API keys, etc. as necessary). When will Studio come as far?

Parents
  • Mats Linder said:
    When will Studio come as far?

    Studio is already a lot further!  I have plugins for 48 MT providers and there could be even more who don't ever send them to us!

    Not everyone wants their MT solutions to be on the appstore so they provide the plugins to their users as needed.  memoQ on the other hand doesn't have a plugin capability so they have to put everything in their core product.  Others can develop plugins for some things but they are only usable if memoQ put them in the product.

    There is no comparison between the environment we provide for developers and that offerred by memoQ or any other CAT tool provider.

    Very surprised to read this question from you

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Thanks very much Paul for this swift reply.

    "memoQ on the other hand doesn't have a plugin capability so they have to put everything in their core product." -- I didn't think of that -- you're right that this makes a huge difference. That said, I wonder why Google Cloud Translation API is (a) included by default, and (b) the only MT provider included by default. (At least Microsoft Translator Text API seems to be [almost] as good as Google and almost as widely used; also of course it can be used via "SDL's own" MT Enhanced Plugin.)

    I'm glad to see that I can surprise you this easily. Expect more in the same vein! :-)
Reply
  • Thanks very much Paul for this swift reply.

    "memoQ on the other hand doesn't have a plugin capability so they have to put everything in their core product." -- I didn't think of that -- you're right that this makes a huge difference. That said, I wonder why Google Cloud Translation API is (a) included by default, and (b) the only MT provider included by default. (At least Microsoft Translator Text API seems to be [almost] as good as Google and almost as widely used; also of course it can be used via "SDL's own" MT Enhanced Plugin.)

    I'm glad to see that I can surprise you this easily. Expect more in the same vein! :-)
Children