Translator
Built for business, 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 a global environment.
We appreciate feedback and use it to guide our product direction, thanks to you!
Use this forum to give feedback or share your ideas on how we can improve Translator:
- Text translation with Translator on Azure
- Custom Translator
- Frequently Asked Questions (FAQ)
- Free technical support in Stack Overflow.
- Free Azure subscription and billing support go to Azure and select “Support” from the menu bar.
- Signing up for a Translator Text API subscription in the Azure portal.
- For all other Translator questions, click “Contact us” at the top right of this page.
-
When do you plan to add Tamil?
when do you plan to add tamil language to the translator?
72 votesHello alamdar.cse
Tamil is now a Microsoft Translator Text API supported language!
Please see the announcement in our blog article here at https://blogs.msdn.microsoft.com/translation/2017/10/24/microsoft-translator-adds-tamil
Thank you for your interest in the Microsoft Translator service.
Pauline
Microsoft Translator -
Support dictionaly only feature for DNN mode
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.
16 votesHello 李國安,
We’re following up as you indicated interest in neural machine translation and customization. Microsoft Translator announced today the availability of a new customization feature for neural machine translation (NMT): Custom Translator (Preview).
Custom Translator (Preview) offers similar capabilities to what Translator Hub does for Statistical MT but exclusively for NMT systems.
The new version 3 of Microsoft Translator Text API is required to use Custom Translator.The supported languages are limited to pairs where NMT languages exist and the list of NMT languages available today can be found on the Microsoft Translator Languages webpage at www.aka.ms/TranslatorLanguages.
The new unified Speech services (Preview), also announced today, offers neural network based customization for speech recognition, translation, and speech synthesis. Learn more at www.aka.ms/AcomSpeech.
Read more about this announcement in the Microsoft Translator blog at www.aka.ms/TranslatorCustomNMTBlog.
Thank you for your interest.
-
Translated URL string gets capitalized
URL contained in the original sentence gets converted to capital letters.
For example,
"This news is from https://www.microsoft.com"
translates to
"Эта новость от HTTPS://www.Microsoft.com",
"HTTPS" and "Microsoft" get capitalized unwantedly.
15 votes -
I found that the translator hub is still using SMT. So I wonder if there is any plan to move it to NMT?
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
8 votesHello cash_ma001,
We’re following up as you indicated interest in neural machine translation and customization. Microsoft Translator announced today the availability of a new customization feature for neural machine translation (NMT): Custom Translator (Preview).
Custom Translator (Preview) offers similar capabilities to what Translator Hub does for Statistical MT but exclusively for NMT systems.
The new version 3 of Microsoft Translator Text API is required to use Custom Translator.The supported languages are limited to pairs where NMT languages exist and the list of NMT languages available today can be found on the Microsoft Translator Languages webpage at www.aka.ms/TranslatorLanguages.
The new unified Speech services (Preview), also announced today, offers neural network based customization for speech recognition, translation, and speech synthesis. Learn more at www.aka.ms/AcomSpeech.
Read more about this announcement in the Microsoft Translator blog at www.aka.ms/TranslatorCustomNMTBlog.
Thank you for your interest.
-
TranslatorArray CORS support
I got "405 method not allowed" error when try to send POST to /TranslatorArray endpoint
Same question here: https://social.msdn.microsoft.com/Forums/en-US/3b032fed-222d-44af-ae2d-3304651337d7/microsoft-translator-text-api-returns-405-error?forum=DataMarket
const key = 'Bearer ' + valid token;
const texts = ["some", "Japanese", "words"];const response = $.ajax({
url: '<a rel="nofollow noreferrer" href="http://api.microsofttranslator.com/V2/Http.svc/TranslateArray'">http://api.microsofttranslator.com/V2/Http.svc/TranslateArray'</a>,
type: 'POST',
headers: {
'Access-Control-Allow-Origin': '*',
},data: {
'appid': key,
'texts': texts,
'Accept': 'application/xml',
'to': 'en',
})console.log(response);
// Got an error, "http://api.microsofttranslator.com/V2/Http.svc/TranslateArray/ 405 (Method Not Allowed)"
What's wrong here.
Actually, the response contains olny the GET as allowed HTTP method, but the documentation describe I need to send a POST.
7 votes -
Translation Array: less-than sign (<) ruins the translation when using text/html
When source contains < character (encoded either as < or <) the source text is incorrectly parsed; and translation nis garbage.
For example:
curl -X POST -H "Authorization: Bearer xyz" -H "Content-Type: application/xml" -d '<TranslateArrayRequest>
<AppId />
<From>en</From>
<Options><Category xmlns="<a rel="nofollow noreferrer" href="http://schemas.datacontract.org/2004/07/Microsoft.MT.Web.Service.V2"">http://schemas.datacontract.org/2004/07/Microsoft.MT.Web.Service.V2"</a>; >XYZ</Category>
<ContentType xmlns="<a rel="nofollow noreferrer" href="http://schemas.datacontract.org/2004/07/Microsoft.MT.Web.Service.V2"">http://schemas.datacontract.org/2004/07/Microsoft.MT.Web.Service.V2"</a>>text/html</ContentType></Options>
<Texts><string xmlns="<a rel="nofollow noreferrer" href="http://schemas.microsoft.com/2003/10/Serialization/Arrays"">http://schemas.microsoft.com/2003/10/Serialization/Arrays"</a>>A resolution of &lt; is very fast, but you lose surface details, so I recommend trying 500 to start and adjusting from there.</string>
</Texts><To>de</To>
</TranslateArrayRequest>' "http://api.microsofttranslator.com/v2/Http.svc/TranslateArray"The returned response:
<ArrayOfTranslateArrayResponse xmlns="http://schemas.datacontract.org/2004/07/Microsoft.MT.Web.Service.V2" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
…<TranslateArrayResponse>
<From>en</From>
<OriginalTextSentenceLengths xmlns:a="<a rel="nofollow7 votesDeclined ·
AdminChris Wendt
(Product Director, or Executive, Microsoft Cognitive Services)
responded
Translator unescapes all HTML named entities, for instance ä or : before translation. < here becomes the opening of an HTML element, and the HTML element name as well as attributes are not translated.
This logic allows you to pass in actual HTML with tags.
Try using text/plain when not passing in HTML. -
JSON
Support a modern JSON-based REST API for request/response (no more SOAP/XML, please!)
7 votes -
Kurdish language
Hi. We are millions of kurd want to use Windows and other Microsoft products in Kurdish with latin script to. There is Kurdish with Arabic script, Central Kurdish. But we want in latin script
6 votes -
Translator Text API does not translate correctly.
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.6 votes -
Translator Text API does not translate correctly.
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.…6 votes -
Markdown as content type
Add markdown as a possible value for textType parameter. Would be great to have it in addition to HTML and plain text.
5 votes -
Text Translator translates only separate words, making sentences unreadable (Finnish language)
Typically, verbs and nouns are mixed up, resulting in hilarious, yet totally unusable (business-wise) translations.
It seems that the translation engine lacks any kind grammar knowledge - it doesn't even try to make up sentences of what it translates.
While this technique might play out with germanic<->germanic languages, it certainly does not with Finnish language.. It might be unfair to compare it to Google Translate (which has no problem translating even complex sentences), but that's the consumer standard so ofc people are comparing to it. As a matter of fact, even Microsoft's translation built-in-feature in Twitter does way better job!
…
5 votes -
Make C# client libraries available on nuget, similar to Azure SDKs
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.
5 votes -
Dear Team, I receive a message stating: An error occured while making the HTTP request to https://api.microsofttranslator.com/V2/soap.svc
Dear Team, I receive a message stating: An error occured while making the HTTP request to https://api.microsofttranslator.com/V2/soap.svc
This 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
5 votes -
Special characters gets encoded after translation
I'm using the text translator api to auto translate text. However some characters could get encoded when comes back from the api, which is surprising. For example, if I need to translate this text "> 12 days" into different languages. "fr" and "es" would encode ">" to ">" while "nl", "de" wouldn't change it.
Correct result from en to nl:
https://api.microsofttranslator.com/v2/ajax.svc/TranslateArray?appId=%22Tqu9huv-RrHgQf20iMFrVx1L5GOPE22QQHdlrcbnpI8M*%22&texts=[%22%3E+14+days%22]&from=%22%22&to=%22nl%22Encoded result from en to fr:
https://api.microsofttranslator.com/v2/ajax.svc/TranslateArray?appId=%22Tqu9huv-RrHgQf20iMFrVx1L5GOPE22QQHdlrcbnpI8M*%22&texts=[%22%3E+14+days%22]&from=%22%22&to=%22fr%225 votesThanks for the report.
Currently indeed a bit random on what happens to < and > when it is not recognized as a tag. We’ll address in an upcoming update. -
Please show the number of characters used for the free tier translation API.
Currently, the portal doesn't show, for the free tier, the number of characters that have been used per month. If it does, it will help determine when I need to switch using the paid tiers.
5 votes -
Clearly identify special characters that are not supported in translation
When using the translate endpoint, text sent with special characters ends up generating a 400 return with no details as to what input was causing the issue.
So far, I have seen this problem with text containing ®, ™ and a non-breaking space.
It would be nice to either have guidelines on which characters are allowed and which are not (documentation), or to have a debug flag on the service that would allow us to get more information on which characters are failing to be processed so that we can easily work around the problem.
4 votes -
Request for a NoTranslate tag for publishers
I don't know what category this belongs to and I just picked any old category. This is a general request for a feature for web publishers. It would be a big help if you could establish a standard tag for MS Translator that disallows translation of specific phrases, or offer publishers the ability to provide a translation glossary of some sort.
For example, our organizational name King County can be mistranslated to mean some permutation of "Monarchy County" in some languages -- and we'd like it to default to its real name, as we would with other place names and…
4 votes -
Language pairs other than English
Do you have any plan to support other language pairs in Custom Translator which do not include English, such as between German and French?
4 votes -
Completely wrong translation from German
I use MS Translator to translate the following text from German to English:
Zentrale Lage, üppiges Frühstück, topp Zimmer Sauna auf dem Dachgeschoss;This is the returned result:
The staff were very friendly and helpful.How can this be that the translation talks about staff where the German original is about location, breakfast and a rooftop sauna?
4 votes
- Don't see your idea?