This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 94%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
The document translation feature of Azure AI Translator is being tested using the cURL method from the documentation. A Hindi document with a .docx extension is being submitted with the target language set to English, but it returns some unsupported text.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 17%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
Hi Saurabh Gohain,
Greetings & Welcome to the Microsoft Q&A forum! Thank you for sharing your query.
I understand that you're encountering an issue with Azure's Document Translation API.
To resolve this, ensure that the .docx file is properly formatted, UTF-8 encoded, and primarily in Hindi, as mixed or unsupported content can sometimes cause problems.
When making your cURL request, explicitly specify "source": {"language": "hi"} for the source language and "language": "en" for the target language. Double-check that your API region, subscription key, and API version (3.0) are correctly configured in the request.
For more detailed steps, please refer to the: Get started: Document Translation REST APIs
I hope this information helps! If you have any further queries, please feel free to reach out. Thank you!
Hi Saurabh Gohain,
Hope you are doing well.
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Hi Saurabh Gohain,
Hope you are doing well.
Just checking in to see if you had a chance to see my response to your question. Please tell us if it was helpful and feel free to reach out to us if you have any queries.
Hi, Pavan
Sorry for the delayed response, had been busy with other task, Thank you for the response, I will check out the tips provided by you and see if it works.
Hi pavan,
I tried out verifying, I could see that .docx type is primarily a binary file, but after unziping it and checking the word/document.xml file it was utf-8 encoded document,
After I tried again, it is still giving me binary data.
I am attaching the screenshot of the output document and as well as the command used
file -I /Users/saurabh/Desktop/document-translation/output_utf8.docx
curl -v -i -X POST "https://translation-dev.cognitiveservices.azure.com/translator/document:translate?sourceLanguage=hi&targetLanguage=en&api-version=2024-05-01" \
-H "Ocp-Apim-Subscription-Key:xx" \
-F "document=@/Users/saurabh/Desktop/document-translation/output_utf8.docx;type=application/vnd.openxmlformats-officedocument.wordprocessingml.document" \
-o "/Users/saurabh/Desktop/document-translation/output.docx"
Hi Saurabh Gohain,
Hope you are doing well.
The issue appears to be related to handling the .docx file during translation, as the API returns binary data, which is expected for document translation outputs. Ensure the input file is a valid .docx containing UTF-8 encoded Hindi text, as confirmed by inspecting the word/document.xml file after unzipping. Verify that the file type is correctly specified as application/vnd.openxmlformats-officedocument.wordprocessingml.document in your curl command. Ensure the endpoint and subscription key are valid, and that the API version (2024-05-01) and languages (hi to en) are supported. The command you are using seems correct, and the output should save as a translated .docx. Open this output to verify its content. If issues persist, test with a simpler .docx file to isolate the problem.