machine translation for addon reviews

RESOLVED FIXED in 2013-11-26

Status

P5
enhancement
RESOLVED FIXED
6 years ago
3 years ago

People

(Reporter: davemgarrett, Assigned: vagnano)

Tracking

(Blocks: 1 bug)

unspecified
2013-11-26

Details

(Whiteboard: [contribute][lang=js], URL)

(Reporter)

Description

6 years ago
It would make it a lot easier to read through the reviews for certain addons if there was a built in feature to automatically translate it into the user's language using Google Translate or Microsoft Translator (formerly Babel Fish).
This sounds like a fun bug to do.  If you need help with UI recommendations just ask.
Priority: -- → P5
Whiteboard: [contribute][lang=js]
(Assignee)

Comment 2

5 years ago
It does sound fun! I guess we would have a "translate" link next to the "parmalink"?
Is there any better service than another (Mozilla Policy concerns or else)?
Google has gone for paid service API. Same for Microsoft Translator (first 2 millions characters are free).
There's http://mymemory.translated.net/ and a bunch of others.
We could also inspire from https://addons.mozilla.org/en-US/firefox/addon/google-translator-for-firefox/ but it read content from web interface.

Any opinion?
(Assignee)

Updated

5 years ago
Assignee: nobody → vagnano
Tell me which one is the best and I'll run it by the privacy group.
(Assignee)

Comment 4

5 years ago
(In reply to Wil Clouser [:clouserw] from comment #3)
> Tell me which one is the best and I'll run it by the privacy group.

After trying a few actual reviews and read translation, each of them have their flaws and are barely readable.
I guess I'd suggest Google Translate API for the sake of popularity, though any other suggestion is very welcome.
Google's API has no free level so we can't actually try this before we start paying for it.  Lisa & Andrew - can you give the thumbs up that this would be useful before I pursue it further?
It sounds kinda useful in theory yes.  Both Google and Microsoft produce fairly readable results between languages with a common history (and laughably bad with others).  Obviously if its going to cost mega bucks someone will need to sign off on it.
(Assignee)

Comment 7

5 years ago
Added in https://github.com/mozilla/zamboni/commit/5685a3017fd337e846f8b7dd5902f7dccd718b99
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-11-19
Hey Vincent,

This is good stuff.  I like that you can click through to the google translate page (in a new tab or whatever).  I enabled the flag on -dev so people could try it out.  Two things I'm doing to reopen:

1) The ajaxy part doesn't work for me.  The link just doesn't do anything.

2) It wasn't clear from the bug, but the place we need this is actually in the flagged reviews queue (https://addons-dev.allizom.org/en-US/editors/queue/reviews) - not on the public pages.  I think leaving it open to everyone might get more expensive than we want it to be, although, I think if we don't have the AJAX part on the public side it would be free, since we're just linking to google, right?  

Let me know if this isn't clear, happy to chat more on IRC.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 9

5 years ago
Replies:

1) we get an error 400. That's most probably due to a API key error. Maybe the API on the dev site is not activated for Translate.

2) I can obviously activate translations on that admin page.
If we don't have the ajax and we keep the external link ot won't imply any cost.

What I'd suggest then is:
- we implement the current translations on the admin
- we deactivate the ajax on the public pages.
(In reply to Vincent Agnano [:vinyll] from comment #9)

> What I'd suggest then is:
> - we implement the current translations on the admin
> - we deactivate the ajax on the public pages.

perfect, thanks.  I'm pretty sure the API keys are correct on -dev but I'm not sure how to confirm it.  Is there something I can run on the CLI to test?
(Assignee)

Comment 11

5 years ago
> Is there something I can run on the CLI to test?

You can check the response with (replacing GOOGLE_key with what's on the server):
curl "https://www.googleapis.com/language/translate/v2?key=GOOGLE_KEY&q=hello%20world&source=en&target=de"
I think you're right, Vincent.  I talked to Rob earlier in the week and it sounds like our GA credentials are in monolith and not in zamboni.  I'll get it sorted out and get one added to zamboni.  Thanks!
(Assignee)

Comment 13

5 years ago
Fixed in https://github.com/mozilla/zamboni/commit/7baa40c0e29bdb78bb75ad5c23bcb089b38f7a3a
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED
Target Milestone: 2013-11-19 → 2013-11-26
(Reporter)

Updated

5 years ago
Blocks: 983804
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.