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.

Please add bahasa Indonesia into translator of kindle

We regularly (once a week) monitor the translation outputs of Microsoft Translator API with test set of 500 sentences. We have observed that the translation outputs change quite frequently, but just very seldom we get a notification from Microsoft regarding changes to the translation framework or the translation models that can explain the changes. It would really help to have regular notes with an explanation of what changes and what should be the expectations in the translation differences.

Thanks.

I did some tests with in a simple app that I created, which uses the Translator Text API 3.0.
But when I try to translate documents with the markdown syntax, the translation return adds spaces between the ###, which results in the text formatting problem.
I would like to know how to make api ignore these spaces between the #.
Thanks.

I'm using Microsoft's Translator Text API 3.0 dictionary lookup. It successfully provides a response but some of the numerical values are incorrect. It is responding with:

confidence: 0.99, numExamples: 0 and frequencyCount: 0

I'm sure this is incorrect! Here's my question I posted on stackoverflow hoping the 'Mircrosoft Translator' stackoverflow account would reply and help me out:

https://stackoverflow.com/questions/55934991/incorrect-response-from-microsoft-translator-api-dictionary-lookup

How does one migrate to v3!!!!?????

Custom Translator doesn't the language pair we used on Translator Hub
We recently migrated our translation project - English - Pashto, over to the Custom Translator. However, Custom Translator doesn't have this language pair as in the Hub. Can you please add this so we can create the necessary projects and proceed with our work?

Over the years, requests to add Pashto has increased significantly. With 50-60 million speakers, it's the official language spoken in Afghanistan, 2nd largest in Pakistan and around the world wherever the Afghan/Pashtun diaspora lives. It's the top trending idea here, but Microsoft hasn't paid attention to it: https://microsofttranslator.uservoice.com/forums/421776-how-do-i-get-my-language-supported/suggestions/14808924-pashto-afghanistan

Translation add a lot of Uppercase on translations.

Example :
From French :

"Fournit avec :
- Certificat de conformité
- Certificat d'immatriculation
- Rapport d'identification
- Certificat de visite aunCT
Dimensions d'encombrement : 240 cm x 470 cm x 310 cm"

To English :

"Provides with:
-Certificate of Conformity
-Registration Certificate
-Identification Report
-Inspection Certificate AunCT
Dimensions Dimensions: 240 cm x 470 cm x 310 cm"

Our problem is thes tranlation in english is used to translate in dutch.
And a custom translation dictionnary.
But the translation dictionnary is Case sensitive.
=> The system doesn't use our custom dictionnary.

I am looking for Translate Text in Hindi.

Do you have any plan to support other language pairs in Custom Translator which do not include English, such as between German and French?

Add markdown as a possible value for textType parameter. Would be great to have it in addition to HTML and plain text.

My client needs a Translate button with a drop-down menu to select on of several languages. His website editor is GoDaddy. Would the MS translator do this?

It would be great to get "translations" for different language localizations via either the /translate or the /dictionary apis. A simple web search shows that this is a wide-spread need that has few if any pre-built solutions.

This would be useful for all variations of english as well as any other language with country-specific words such as spanish.

When translating from DE to EN, the originally capitalized DE words (nouns) are still capitalized in EN. Of course this is only acceptable in German and not in English. I could not find any previous post flagging this issue, not sure if you are already working on this.

Translating "Brown / Cow" to (for example FR) returns "Brun/vache".
Problem 1 is the space around the slash is missing. I puzzled out an undocumented escape sequence that fixes that though: "Brown\ /\ Cow" returns "Brown / vache" so the spaces are kept.
Problem 2 is the letter v in the translation should be Uppercase V and return "Brown / Vache"

I am using the generic NMT and found a serious mistranslation:
Source- 若中英文条款有不一致之处，以中文条款为准
Target- In the event of any inconsistency between the Chinese and English terms, the English terms shall prevail

The correct translation should be "the Chinese terms shall prevail". This is legal content and the error is fundamental