Translator

Built for business, Microsoft Translator is a proven, customizable, and scalable solution for automatic translation. Microsoft Translator’s cloud-based APIs can help make your business or app competitive in an increasingly globalized business environment.

We appreciate feedback and use it to guide our product direction, thanks to you!

Ideas and feedback -

Use this forum to give feedback or share your ideas on how we can improve Microsoft Translator:
• Speech API
• Text API
• Translator Hub

• For free technical support go to Stack Overflow
• For free Azure subscription and billing support go to Azure and select “Support” from the menu bar.
• For all other questions click “Contact us” to the right of this page.

For support with the Microsoft Translator apps for Windows, iOS, and Android; the Microsoft Translator Edge extension; Bing.com/translator; or other consumer products please go to Microsoft Translator support.

How can we improve Translator?

Please add your feedback and suggestions for Translator

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

We have different types of services to do speech to text transformation and to do text sentimental analysis, can we have one service which provide us real time sentimental analysis of conversation? Services like this one are already provided by https://www.nexmo.com/use-cases/real-time-sentiment-analysis and its very useful for customer support scenario. Performance is a key factor here because once the customer is left we can't do much with results of sentimental analysis.

From memoQ, in the Microsoft MT plugin settings, configure the "subscribe to Microsoft Translator" option so that one is automatically registered and can start working right away. We are translators, not computers nerds.

when i translate i get this exception "{"Invalid appId\r\nParameter name: appId"}" although i have valid microsoft text translator api key and i have put it in the code but stil it shows.
when i select soap v2 service refference it gets ok but parameters show exception

The DNN output improve is so great. The more needed capabilty to use complex business domain is dictionally as customable space. We strongly want to Translator Hub for DNN mode. That's dramatically reduce our manual process for translation workflow.

Hello. I translate from Russian into English and noticed a bug:
1. погода в Гатчине сегодня = weather in London today
2. погода в Гатчине сейчас = weather in Markham now
Гатчина is a small town in Russia and it should not be translated. There are a lot of cities where your translater makes such errors. Google translator does not make such mistakes. Thank you.

I would love to be able to consume C# wrapper libraries for the text api (similar to Azure SDKs for access to blob storage, etc.) via nuget. Then my code can be better insulated from changes in the APIs, simplify token negotiation, etc.

Hello. I hope the translation result of the Translator Text API is improved. An example is shown below.
1. When translating from Chinese (traditional) to Japanese, "-" disappears. Please keep it as original text.
2. When translating from Chinese (Traditional), Korean, English to Japanese, the capital letters of the alphabet change to lower case. Please keep it as original text.
3. When translating from Chinese (traditional) to Japanese, 'JEA' is translated into 'acid rain'. Please keep it as original text.
4. When translating from Chinese (traditional) to Japanese, ". (Period)" changes to "。" Please keep it as original text.
5. When translating from Korean into Japanese, "①②" will change to "(1) (2)". Please keep it as original text.
6. When translating from English to Japanese, Y20 is translated to 20 billion. Please keep it as original text.
7. When translating from Korean into Japanese, the quality is bad compared to Google and I do not know the meaning.
Thank you.

Hello. I hope the translation result of the Translator Text API is improved. An example is shown below.
1. When translating from Chinese (traditional) to Japanese, "-" disappears. Please keep it as original text.
2. When translating from Chinese (Traditional), Korean, English to Japanese, the capital letters of the alphabet change to lower case. Please keep it as original text.
3. When translating from Chinese (traditional) to Japanese, 'JEA' is translated into 'acid rain'. Please keep it as original text.
4. When translating from Chinese (traditional) to Japanese, ". (Period)" changes to "。" Please keep it as original text.
5.…

I post these questions as I found the translation quality is poorer when using the hub than only using the base microsoft translator. it now confuses me and I do not know how to choose between the 2 systems. So I think if they can combine together, that would be great

Would you please more self-service and short time to training and deploy process using Translator Hub? Especially, we want to understand this behavior at the first phase but it take a couple of day especailly deployment, that stop try and error process.

Dear Team, I receive a message stating: An error occured while making the HTTP request to https://api.microsofttranslator.com/V2/soap.svcThis could be to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server.

I have used MicrosoftTranslator many time before and have not changed anything since using it the last time. Can you think of a possible explanation? Thank you very much. Kind regards, LL

response:Unable to deserialize XML body with root name 'translatearrayrequest' and root namespace '' (for operation 'TranslateArray' and contract ('LanguageService', 'http://api.microsofttranslator.com/V2')) using DataContractSerializer. Ensure that the type corresponding to the XML is added to the known types collection of the service.

Hi,
we are evaluating the NMT engines and have found that English-> Chinese engine occasionally returns the "TranslateApiException: server temporarily unavailable " error.
The source for translation contain no suspicious content apart from some alphanumeric abbreviations. I suspect there might be some transliterization issue in the backround - the same sentence is translated well for European languages.
Couldyou please take a look? Thanks.

Some source examples:

The PCM monitors reference voltage deviation from the power supply circuit of the APS1.
PCM monitors peak differential value of the oxygen sensor signal after the front HO2S fluctuation being provided .