Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switching translator to Google #1800

Closed
joenas opened this issue Nov 17, 2016 · 13 comments
Closed

Switching translator to Google #1800

joenas opened this issue Nov 17, 2016 · 13 comments

Comments

@joenas
Copy link
Contributor

joenas commented Nov 17, 2016

Hey there and thanks for an awesome app!

I noticed this when trying to use the TranslatorAgent:

DataMarket and Data Services are being retired and will stop accepting new orders after 12/31/2016. Existing subscriptions will be retired and cancelled starting 3/31/2017. Please reach out to your service provider for options if you want to continue service.

Any plans on switching service, to for example Google Translate? If I find some spare time, I might start implementing it if there's interest.

Also, the current Agent doesn't work... 😄

no implicit conversion of nil into String
/app/app/models/agents/translation_agent.rb:44:in `+'
/app/app/models/agents/translation_agent.rb:44:in `translate'

which seems to be because access_token is nil.
I was gonna create an issue about that but since it's being retired anyways I figure no point.

@cantino
Copy link
Member

cantino commented Nov 20, 2016

I don't personally use it, but it'd be nice if it worked. We'd gladly accept a PR to fix it.

@Maroo-b
Copy link

Maroo-b commented Apr 17, 2017

@cantino it seems that google translate is a paid service ( source )

For free services it seems Yandex the most promising, do you suggest another service to integrate ?

@cantino
Copy link
Member

cantino commented Apr 19, 2017

Probably the best solution would be to support multiple translation backends. Would you be interested in working on that?

@Maroo-b
Copy link

Maroo-b commented Apr 19, 2017

Absolutely, I suggest that we start by implementing an alternative to the existent solution, it seems that Microsoft Translator is the upgrade for the current implemented solution. (I need to do more checks )
Afterward we can add other backends based on users feedback.

@joenas
Copy link
Contributor Author

joenas commented Apr 19, 2017

I actually have a working implementation of Google Translate, I just haven't gotten around to write specs...

@cantino
Copy link
Member

cantino commented Apr 19, 2017

It'd be great to get both Google and Microsoft in one Agent. @joenas, maybe you can contribute yours and @Maroo-b can add to it?

@Maroo-b
Copy link

Maroo-b commented Apr 20, 2017

@cantino that would be interesting I'll wait for @joenas PR.

@joenas
Copy link
Contributor Author

joenas commented Apr 20, 2017

PR submitted!

@Maroo-b
Copy link

Maroo-b commented Apr 27, 2017

should this issue be closed ?

@joenas
Copy link
Contributor Author

joenas commented Apr 28, 2017

It depends on whether you want to use it for Microsoft/Yandex/whatever too or not I guess?

@Maroo-b
Copy link

Maroo-b commented Apr 28, 2017

@joenas thank you for the feedback,
I don't use the translator Agent but if there is a need for another translate API I can submit a PR otherwise I'll check other issues :)

@joenas
Copy link
Contributor Author

joenas commented Apr 28, 2017

Then I think we should close and move on :D

@cantino
Copy link
Member

cantino commented Apr 28, 2017

Agreed! Thanks.

@cantino cantino closed this as completed Apr 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants