If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Bing Translation not working

RESOLVED INVALID

Status

Invalid Bugs
General
RESOLVED INVALID
3 months ago
3 months ago

People

(Reporter: Kapranov, Unassigned)

Tracking

Details

Attachments

(1 attachment)

11.38 KB, application/x-javascript
Details
(Reporter)

Description

3 months ago
Created attachment 8882814 [details]
BingTranslator.jsm

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170628075643

Steps to reproduce:

Translator Engine "Bing" in Firefox does not work.


Actual results:

Microsoft suffered API in Azure, which is why any translation problems. I propose a workaround solution:

// Prepare URL.
      let url = getUrlParam("https://www.bing.com/translator/api/translate?ref=edge&from=" + this.sourceLanguage + "&to=" + this.targetLanguage,
                            "browser.translation.bing.translateArrayURL");

      // Prepare request headers.
      let headers = [["Content-type", "application/json"]];

      // Prepare the request body.
      let requestString = "[";

      for (let [, text] of this.translationData) {
        requestString += '"' + text + '",';
      }

      requestString += "]";


Expected results:

In this embodiment, API keys are not needed. The server returns the data in JSON format, accordingly it remains only to display them on the screen.
Please contact Microsoft about your issue.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 months ago
Component: Untriaged → General
Product: Firefox → Invalid Bugs
Resolution: --- → INVALID
Version: 54 Branch → unspecified
(Reporter)

Comment 2

3 months ago
(In reply to Kohei Yoshino [:kohei] from comment #1)
> Please contact Microsoft about your issue.

Registration in Azure is required. Otherwise it does not work. And in the variant offered by me it is not necessary to use any keys. This method uses Microsoft in the browser Edge
You need to log in before you can comment on or make changes to this bug.