[BUG-8794] The Bing API used by the viewer is depreciated.

[sl-service-account]

Steps to Reproduce

Trying to enable the translation feature.

Actual Behavior

I attempted to get a Bing API Key using the link in the viewer Preferences->Chat->Translation. The link takes one to Microsoft/Bing Web Master Tools. The registration for a Bing Translate API is no longer there. So, we could say the link is bad. And replace it with a better link, maybe: http://www.bing.com/dev/en-us/translator But, one soon finds that leads to the Microsoft Translator API. That API does not work with the viewer. It will not Verify. See: https://msdn.microsoft.com/en-us/library/dn355993.aspx

Expected Behavior

I was expecting the Verify to work. None of the MS API keys I can come up with work.

Other information

It appears that to work with the new API, the viewer will need to provide User ID and Key fields for the MS API. There is also a secession token passed to the app using the translator. I think that is new, but whatever that process needs to be handled.

The Bing/Microsoft information is that existing keys will continue to work. But, all new keys have to be for the MS Translation API. The MS web sites are a bit of a mess on this subject. The tech info is here: https://msdn.microsoft.com/en-us/library/dd576287.aspx

The step-by-step to getting a key is way complex and shows an obvious change at MS: http://www.microsoft.com/web/post/using-the-free-bing-translation-apis

OMG! This is the user’s getting started page: http://blogs.msdn.com/b/translation/p/gettingstarted1.aspx

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-8794 | | Summary | The Bing API used by the viewer is depreciated. | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Nalates Urriah (nalates.urriah) | | Created at | 2015-03-17T17:50:26Z | | Updated at | 2015-04-08T22:00:33Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2015-03-17T19:04:07.420-0500', "Is there anything you'd like to add?": 'It appears that to work with the new API, the viewer will need to provide User ID and Key fields for the MS API. There is also a secession token passed to the app using the translator. I think that is new, but whatever that process needs to be handled.\r\n\r\nThe Bing/Microsoft information is that existing keys will continue to work. But, all new keys have to be for the MS Translation API. The MS web sites are a bit of a mess on this subject. The tech info is here: https://msdn.microsoft.com/en-us/library/dd576287.aspx\r\n\r\nThe step-by-step to getting a key is way complex and shows an obvious change at MS: http://www.microsoft.com/web/post/using-the-free-bing-translation-apis\r\n\r\nOMG! This is the user’s getting started page: http://blogs.msdn.com/b/translation/p/gettingstarted1.aspx\r\n', 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'I attempted to get a Bing API Key using the link in the viewer Preferences->Chat->Translation. The link takes one to Microsoft/Bing Web Master Tools. The registration for a Bing Translate API is no longer there. So, we could say the link is bad. And replace it with a better link, maybe:\r\nhttp://www.bing.com/dev/en-us/translator\r\nBut, one soon finds that leads to the Microsoft Translator API. That API does not work with the viewer. It will not Verify. \r\nSee: https://msdn.microsoft.com/en-us/library/dn355993.aspx \r\n', 'What were you doing when it happened?': 'Trying to enable the translation feature. ', 'What were you expecting to happen instead?': 'I was expecting the Verify to work. None of the MS API keys I can come up with work.', 'Where': 'Every where', } ```

[sl-service-account]

Ansariel Hiller commented at 2015-03-18T00:04:07Z

It is important to note that old Bing API keys still work and verify. So whatever change is being made here needs to take that into account and provide a way to use either the old or the new Bing API key/credentials.

[sl-service-account]

Whirly Fizzle commented at 2015-03-18T01:47:51Z

I can confirm my old Bing API key still works to enable translation in Second Life 3.7.25 (299021) Feb 13 2015 15:21:02 (Second Life Release).

However attempting to set up Bing translation using the new method is, as Nalates says, impossible. It is horribly unclear how to set it up (not LL's problem though) and once you have the new key, the key is not accepted by the viewer.

[sl-service-account]

Nalates Urriah commented at 2015-03-18T15:34:02Z

From ANSWERS: https://community.secondlife.com/t5/Viewers/Bing-Free-Translate/qaq-p/2914849

[sl-service-account]

Grumpity Linden commented at 2015-03-19T17:05:56Z

Thanks Nalates. Ugh.

[sl-service-account]

Whirly Fizzle commented at 2015-03-19T18:04:44Z

This has been broken since at least May 2012 ;) (That's when it was filed on the FS JIRA anyway: http://jira.phoenixviewer.com/browse/FIRE-6459)

[sl-service-account]

Grumpity Linden commented at 2015-03-19T18:33:03Z

I thought we had fixed it that time, Whirly. Maybe wishful thinking...

[sl-service-account]

Nalates Urriah commented at 2015-04-08T21:43:09Z

Today I am seeing people complaining in the forum and asking in ANSWERS about the Metanomics translator giving errors. I went in today and tested my copy of the translator. I didn't get an error but the translator is returning HTML.

================= !DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">