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

Machine Translation no longer possible #54

Closed
cherpake opened this issue Feb 24, 2017 · 9 comments · Fixed by #114
Closed

Machine Translation no longer possible #54

cherpake opened this issue Feb 24, 2017 · 9 comments · Fixed by #114

Comments

@cherpake
Copy link

Microsoft retired it - can't create new accounts: https://datamarket.azure.com/account/applications

@Jeehut
Copy link
Member

Jeehut commented Mar 3, 2017

Thanks for the pointer. I will remove the feature once I have some spare time and add an explanation to the README. If anybody needs the feature, they are free to copy the code and adapt it for a different translation service in its own library. I think supporting incremented updates is going to be the main goal of this library going forward.

@jaimeagudo
Copy link

I could create a new account yet, the correct url is https://datamarket.azure.com/developer/applications

From what I understand they are re-organizing/integrating it within their services, not really retiring

@Jeehut
Copy link
Member

Jeehut commented May 2, 2017

Thanks for the information, it's good to know. The big question is though if they are going to keep a free service and if the API will be implemented into Polyglot, otherwise work would be required to get it working again what I don't have the time for.

@jaimeagudo
Copy link

jaimeagudo commented May 2, 2017

After some browsing here you have the refurbished service page, free tier still available for 2Mchars/month 😄 https://azure.microsoft.com/es-es/pricing/details/cognitive-services/translator-text-api/

Btw I checked out the Google Cloud one too and there is no free tier at all

@Jeehut
Copy link
Member

Jeehut commented May 2, 2017

Thanks for the research, sounds good. Only question is if it continues to work out of the box – then I would only update the registrations links (or are they even still correct?).

@pooran
Copy link

pooran commented Jun 17, 2017

Yes, free tier is good for most applications out there

@Jeehut
Copy link
Member

Jeehut commented Oct 17, 2017

That doesn't answer my question. Is translation working as-is with the current version of BartyCrouch? Or do we need to update the links? If this is not an issue at all, I'd like to close this issue.

@0xNSHuman
Copy link

0xNSHuman commented Jan 15, 2018

So I just registered with Microsoft Translator using its new home — Azure Portal, and it seems to have different authorization flow now. I couldn't find anything like API Secret there, but requests can be satisfied using just single "Subscription Key".

Not sure what service BC uses, but current endpoint is https://api.cognitive.microsoft.com/sts/v1.0. Btw, it still has the same nice free plan.

I tried running BC with the closest credentials to API Key/API Secret I had (Subscription ID/Subscription Key), but it just did nothing. No errors thrown as well.

Hope this clears things up.

@Jeehut
Copy link
Member

Jeehut commented Jan 16, 2018

Thanks for the update. Looks like we need to either update that part of BartyCrouch or remove it, just as I planned previously. If anyone was really using the translation feature of BartyCrouch, I encourage them to fork BartyCrouch at version 3.8.x, rename the project and stripp off all non-translation related code to create a new tool specifically for that task.

I will let this issue open so long as BartyCrouch doesn't receive an update with the translation feature dropped.

@Jeehut Jeehut mentioned this issue May 16, 2018
@Jeehut Jeehut added this to the Version 4.0 milestone Jan 28, 2019
@Jeehut Jeehut mentioned this issue Feb 4, 2019
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants