According to https://docs.microsoft.com/en-us/azure/cognitive-services/translator/reference/v3-0-translate#obtain-alignment-information, the user 'will not receive alignment if the sentence is a canned translation. Example of a canned translation is 'This is a test', 'I love you' and other high frequency sentences.'

Could you please be consistent and provide a 'canned alignment' for canned sentences?

Always getting alignment information is quite critical for our integration of the Translator Text API.

Thanks.

I'm working on a solution to convert between English and textual ASL (i.e. English with different grammar). I've organized the data but the translation pairs are extremely restrictive.

1. I'm using this api to translate text: https://docs.microsoft.com/azure/cognitive-services/translator/reference/v3-0-translate




2. When user key in the keyword "tidak", it gets English as detected language, which is wrong, because there is no such word in English. It is a Malay word which means "No".




3. It is also the same when I tried manually in Bing Translator.

Thanks.

Hello

I have been using cognitive paid service for translating text and I have been facing issue while translating text.

1. When there are // or operators in bold, the // are deleted from the text . This has been observed with Bing translator too.




2. Where there are japanese charachter the service is unable to translate the text. This happens when there are multiple languages and my cognitive service is already choosing the sorce language as auto-detect.

Can you please suggest what can be done in such cases and how can I resolve this?

The following additional language support would be appreciated:

Albanian
Armenian
Azeri
Kyrgyz
Sesotho
Xhosa
Zulu

I put the key like this "subscriptionKey = 'here my key'",but the result is " "message": "The request is not authorized because credentials are missing or invalid."

I don't know what's wrong

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.