Bing Translator not working on Firefox or Safari (both latest running under OS X) RRS feed

  • Question

  • Per the title, translator fails to translate in either auto-detect or when input and output languages are specified.

    In auto-detect, English is always detected no matter the source language. I've tried German, Ukranian, Russian, Korean and Japanese but all were detected as English with, strangely enough, the same text showing up on the translated side in the same character set.

    I'd really like someone on the MS team to look into this as I abhor Google translate and google products in general.



    Wednesday, July 15, 2015 3:54 AM


All replies

  • Good day!

    Just looking for a little additional info:

    As a bonus, if you have a Fiddler or network trace (via F12 in Firefox) showing any calls to http://api.microsofttranslator.com/v2/ajax.svc/TranslateArray2?... that would be invaluable for debugging your issue.

    Thank you!

    Wednesday, July 15, 2015 6:56 PM
  • Hi,

    Thanks for the quick reply!

    • I am indeed viewing http://www.bing.com/translator/
    • My native browser language is always en-US.

    I'm happy to oblige with traces, firebug test, etc. Here's what I get from network trace on a trial run:

    • page already loaded to http://www.bing.com/translator/
    • input language: Korean
    • output language: English
    • text string to translate: 미안합니다 (translation: I am sorry/I apologize)

    GET 200:  http://api.microsofttranslator.com/v2/ajax.svc/TranslateArray2?appId="T77VVwdUv0KQldAmbxsNHko5jfMHtOijzxnwjwmXYc-rv9OP5vaKsNcxTWI5X_4nc"&texts=["미안합니다"]&from="ko"&to="en"&options={}&oncomplete=onComplete_8&onerror=onError_8&_=1436996611444

    GET 200: http://www.microsofttranslator.com/sync.ashx?callback=jQuery111204073776712600795_1436996611431&0=E_5_1_1_64&svc=LP&loc=en&from=ko&to=en&error=TranslateApiException:+Error+processing+request+:+ID=3427.V2_Json.TranslateArray2.28777AF2&dtc=&text=미안합니다...&_=1436996611445

    GET 200:  http://www.bing.com/translator/LandingPage/GetDefinition?oncomplete=jQuery111204073776712600795_1436996611421&market=ko&word=미안합니다&_=1436996611446

    ... and that is it. I can provide more languages and or debug output if you need it. Once again thanks for the quick reply.


    Wednesday, July 15, 2015 10:17 PM
  • Just to add some info - this doesnt appear to be related to the OS or the hardware on the user end.

    I live in China, and I have been using the Bing translator as a much better alternative to the Google translator. I last used it less than 12 hours ago.

    But today, while translation between English and Spanish, French, etc work fine, it does not work with translation to/from Chinese.

    Instead, translation (for example) of 'hello' to Chinese just shows 'hello'. This is on 2 different computers, not a PC problem. 2 versions of Windows 7, using latest Firefox and also Internet Explorer. One is signed up for the pre-Win 10 updates, the other isn't, so that's not the answer, but something has changed in the last 12 hours.

    Sunday, July 19, 2015 6:06 AM
  • I've also been using Bing to "machine translate" some novels and it suddenly can no longer translate to/from Chinese. I've tried it with other languages and only Chinese is affected.
    Sunday, July 19, 2015 7:59 PM
  • Thanks for your alert.

    We are aware of Chinese<>English and Japanese<>English failures on bing.com/translator, and addressing it. Updates are here:


    Chris Wendt
    Microsoft Translator

    Monday, July 20, 2015 3:53 PM
  • Still broken for Ukranian, Korean and German. I didn't bother to check Russian or Japanese. I can provide traces again, if you'd like.
    • Edited by Omerod Wednesday, July 22, 2015 4:43 PM more langs.
    Wednesday, July 22, 2015 4:41 PM
  • This is not a fix for my problem, so please, MSFT employees, either allow me to mark it as not an answer for my specific problem I opened this thread for, or remove it as an answer from this thread.

    Please stop acting like Google. This is still broken and I doubt that mine is an edge case.

    Thursday, July 23, 2015 3:38 AM
  • Hi Omerod,

    we believe we have fixed the issue for all cases except for large number of requests behind a proxy. Would be great if you can provide a tracert.

    Thanks much,
    Chris Wendt
    Microsoft Translator

    Friday, July 24, 2015 9:13 PM
  • Hi Chris,

    Thanks for the reply; sorry for being so snippy in my last ... work pressures, etc.

    Here's my traces. This time I'm using the same phrase in each language with Auto-Detect set:

    • Korean phrase: 공항에 도착 (trans. arrive at the airport):

    GET 200 http://api.microsofttranslator.com/v2/ajax.svc/TranslateArray2?appId="T6m-0PUfKBPevxPhn5gdwzAIsqXwO1VQ8YPK8chZdmruwXD4dK4YRz2vhgqsuBEJi"&texts=["공항에+도착"]&from=""&to="en"&options={}&oncomplete=onComplete_0&onerror=onError_0&_=1437772801795

    GET 200 http://www.microsofttranslator.com/sync.ashx?callback=jQuery111207356555448357558_1437772801796&0=E_6_1_1_151&svc=LP&loc=en&from=&to=en&error=TranslateApiException:+Error+processing+request+:+ID=3627.V2_Json.TranslateArray2.409BCEFC&dtc=&text=공항에+도착...&_=1437772801797

    GET 200 http://www.bing.com/translator/LandingPage/GetSpeakLocales?sourceLocale=en

    GET 200 http://www.bing.com/translator/LandingPage/GetSpeakLocales?sourceLocale=en

    • German phrase: kommen am Flughafen:

    GET 200 http://api.microsofttranslator.com/v2/ajax.svc/TranslateArray2?appId="T6m-0PUfKBPevxPhn5gdwzAIsqXwO1VQ8YPK8chZdmruwXD4dK4YRz2vhgqsuBEJi"&texts=["kommen+am+Flughafen"]&from=""&to="en"&options={}&oncomplete=onComplete_0&onerror=onError_0&_=1437773634505

    GET 200 http://www.microsofttranslator.com/sync.ashx?callback=jQuery1112013693013550718625_1437773634506&0=E_19_1_1_62&svc=LP&loc=en&from=&to=en&error=TranslateApiException:+Error+processing+request+:+ID=3541.V2_Json.TranslateArray2.3FC1BB28&dtc=&text=kommen+am+Flughafen...&_=1437773634507

    GET 200 http://www.bing.com/translator/LandingPage/GetSpeakLocales?sourceLocale=en

    GET 200 http://www.bing.com/translator/LandingPage/GetSpeakLocales?sourceLocale=en

    • Japanese phrase: 空港に到着

    GET 200 http://api.microsofttranslator.com/v2/ajax.svc/TranslateArray2?appId="TJFxx-eCDcAM286_LYgu1e-B_wSoHTKH8TqJJVm3dTrMX-VfF6Js9AEC5sAKr4MjH"&texts=["空港に到着"]&from=""&to="en"&options={}&oncomplete=onComplete_0&onerror=onError_0&_=1437773979072

    GET 200 http://www.microsofttranslator.com/sync.ashx?callback=jQuery111203437054125940695_1437773979073&0=E_5_1_1_112&svc=LP&loc=en&from=&to=en&error=TranslateApiException:+Error+processing+request+:+ID=3730.V2_Json.TranslateArray2.40A79F6E&dtc=&text=空港に到着...&_=1437773979074

    GET 200 http://www.bing.com/translator/LandingPage/GetSpeakLocales?sourceLocale=en

    GET 200 http://www.bing.com/translator/LandingPage/GetSpeakLocales?sourceLocale=en

    GET 200 http://www.bing.com/translator/LandingPage/GetDefinition?oncomplete=jQuery111203437054125940695_1437773979075&market=en&word=空港に到着&_=1437773979076

    Each of those requests produced input detected as English with text remaining the same on input and output sides. That ought to be enough traces for you to work with I hope. If you need more please feel free to ask.

    Friday, July 24, 2015 9:44 PM
  • Thanks, Omerod, that helps a lot.

    We had blocked the IP range you are calling from, obviously erroneously. Can fix that now.

    We work in machine translation, and are used to snippiness and ridicule :] No problem at all. Please keep the feedback coming.

    Chris Wendt
    Microsoft Translator

    • Marked as answer by Omerod Saturday, July 25, 2015 2:44 AM
    Friday, July 24, 2015 11:47 PM
  • Boom! Well done MSFT, thanks for getting things working for me again.
    Saturday, July 25, 2015 2:46 AM