Closed
Bug 1481516
Opened 6 years ago
Closed 6 years ago
Machinery tab rarely shows results from Machine Translation
Categories
(Webtools Graveyard :: Pontoon, enhancement, P3)
Webtools Graveyard
Pontoon
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1499512
People
(Reporter: adrian, Unassigned)
Details
As far as my experience goes, I don't often see MT results in the Machinery tab in both stage and prod. Here are some examples that at the moment don't show any results: [prod] https://pontoon.mozilla.org/fr/amo-frontend/LC_MESSAGES/amo.po/?string=174070 https://pontoon.mozilla.org/sq/focus-for-ios/focus-ios.xliff/?string=161002 [stage] https://mozilla-pontoon-staging.herokuapp.com/fr/amo-frontend/LC_MESSAGES/amo.po/?string=177336 https://mozilla-pontoon-staging.herokuapp.com/de/firefox/browser/chrome/browser/feeds/subscribe.properties/?string=78663 Those seem like simple enough strings to translate, there's no Fluent involved, there are no errors in the JS console, and I can't find anything suspicious in the heroku logs (but I might have not looked correctly).
Comment 1•6 years ago
|
||
Note that the 2nd example from [prod] doesn't work because Microsoft Translator doesn't support Albanian (sq).
Comment 2•6 years ago
|
||
The root cause here is that we're using a deprecated API (v2) of Microsoft Translator. We'll be switching to Google Translate API on pontoon.mozilla.org once bug 1499512 lands, which will effectively fix this bug, too.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Comment 3•6 years ago
|
||
Commit pushed to master at https://github.com/mozilla/pontoon https://github.com/mozilla/pontoon/commit/34dcdbd3a3490f92827e2441335ab872151dba29 Bug 1481516: Support Microsoft Translator API v3 (#1088) Also: * Remove support for Microsoft Translator API v2 (deprecated) * Add tests for Microsoft Translator integration
Updated•3 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•