You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 11, 2022. It is now read-only.
In #6, we gave Microsoft's machine translation service a try. But as @vaartis suggested in that thread, perhaps we should also try out Google's service, which is supported by Crowdin.
Here's some info that @alebourne gathered about Google's service:
In March 2017, Google has released the commercial version of their translation API that with Neural Translation Memory. This brings their offering on par to Microsoft already existing support of NMT.
The Neural Machine Translation arms race is on!
The Neural Translation model is now used when signing up for the Premium edition as a default, and if a language pair is not available, then the Phrase based (older style machine translation) is used.
To quote the Google website (https://cloud.google.com/translate/docs/premium):
Instead, the premium features of the Google Cloud Translation API have been made generally available in the Standard Edition. All users have access to the robust translation features available using the Neural Machine Translation (NMT) model, as well as the capabilities of the Phrase-Based Machine Translation (PBMT) model. There is no difference in pricing between the standard, PBMT model, and the NMT model.
Pretty sure we're not going to need any machine translation after all, as the consensus seems to be that humans still need to proofread all the content, and it's harder to know what's been proofed when everything is translated. Closing this but we can open it back up if anyone feels strongly about giving MT another try for any languages.
In #6, we gave Microsoft's machine translation service a try. But as @vaartis suggested in that thread, perhaps we should also try out Google's service, which is supported by Crowdin.
Here's some info that @alebourne gathered about Google's service:
The text was updated successfully, but these errors were encountered: