Synchronous document translation rejects any RTF snd DOC

Question

Synchronous document translation rejects any RTF snd DOC

Aleksandar Kostadinov 0

Hi, trying to translate an RTF document fails. I think the issue is in the synchronous translator with any RTF. I'm wondering - nobody translating RTFs? I tried with 2 RTFs, one of which I created new just for the test. ~~Not allowed to attach it here but I uploaded it to [1], will be there for 7 days.~~

My file is:

echo '{\rtf1\ansi\deff0 {\fonttbl {\f0 Times New Roman;}} Hello world}' > /tmp/ttt. rtf

My request is:

curl -v -o /tmp/ttt.translated.rtf -X POST "https://yoga-translator.cognitiveservice s.azure.com/translator/document:translate?sourceLanguage=en&targetLanguage=bg&api-version=2024-05-01" -H "Ocp- Apim-Subscription-Key: [REDACTED]" - F 'document=@"/tmp/ttt.rtf";type=application/rtf;filename=document.rtf'

I get back HTTP 400 and the content of /tmp/ttt.translated.rtf is:

{"error":{"code":"InvalidRequest","message":"The format parameter is not valid.","target":"ContentType","inner Error":{"code":"InvalidFormat","message":"The format parameter is not valid."}}}

Whether I specify type or not with curl doesn't matter. I always get the same when I submit an RTF file. I successfully translated only a sample text/plain document but only succeeded when file extension was .txt. When `filename`` had no extension, everything else equal, I've got the same error as with the RTF. That's why I'm thinking that whatever auto-detection is going on is broken over there. With a confusing error message on top of it.

I hope some support person can chime in because I can't file a support case. I'm not paying $29 for the privilege to be a qe tester. I'd rather go to a different provider as I'm just kicking the tires of azure translate.

P.S. I verified that the translator does support RTF with the application/rtf mime type using some endpoint /translator/text/batch/v1.0/documents/formats

Update: it also rejects any .doc files but works with .docx

~~[1] https://limewire.com/d/jkv1f#Sm9q9ncgc0~~

Aleksandar Kostadinov 0 Reputation points

2025-12-04T19:34:15.5133333+00:00

Thank you @Aryan Parashar , good to be documented. But is this documentation brand new? I didn't find it browsing the docs, I couldn't find it in search and AI also could not point me at it.

If I go to synch translator api docs: https://learn.microsoft.com/en-us/azure/ai-services/translator/document-translation/reference/translate-document

The link to supported document formats points me at the link that you have just posted. But I'm sure that I went through this exercise the other day and it pointed me at the endpoint to discover supprted formats that returned the formats for async translation.

So either the document is brand new or I experienced a glitch and AI that is otherwise super helpful in finding such kind of stuff also has a glitch about it. Both of which is very possible so that's why I'm asking.

In general, I'm not frustrated that something doesn't work, it's frustrating something meant to work doesn't, as well not to find what is supposed to work in the first place.

At least the mystery i solved. Cheers.
Aryan Parashar 3,380 Reputation points Microsoft External Staff Moderator

2025-12-05T09:27:24.7566667+00:00

Hi Aleksandar Kostadinov,

I’m glad the explanation helped clarify things for you. Please feel free to reach out if you have any further questions.

If this resolves your issue, I would appreciate it if you could mark this response as the accepted answer. Thank you for reaching out to The Microsoft Q&A Portal

1 answer

Your answer

Aleksandar Kostadinov 0 Reputation points

2025-12-04T19:34:15.5133333+00:00

Thank you @Aryan Parashar , good to be documented. But is this documentation brand new? I didn't find it browsing the docs, I couldn't find it in search and AI also could not point me at it.

If I go to synch translator api docs: https://learn.microsoft.com/en-us/azure/ai-services/translator/document-translation/reference/translate-document

The link to supported document formats points me at the link that you have just posted. But I'm sure that I went through this exercise the other day and it pointed me at the endpoint to discover supprted formats that returned the formats for async translation.

So either the document is brand new or I experienced a glitch and AI that is otherwise super helpful in finding such kind of stuff also has a glitch about it. Both of which is very possible so that's why I'm asking.

In general, I'm not frustrated that something doesn't work, it's frustrating something meant to work doesn't, as well not to find what is supposed to work in the first place.

At least the mystery i solved. Cheers.
Aryan Parashar 3,380 Reputation points Microsoft External Staff Moderator

2025-12-05T09:27:24.7566667+00:00

Hi Aleksandar Kostadinov,

I’m glad the explanation helped clarify things for you. Please feel free to reach out if you have any further questions.

If this resolves your issue, I would appreciate it if you could mark this response as the accepted answer. Thank you for reaching out to The Microsoft Q&A Portal

Answer 1

Hi Aleksandar Kostadinov,

I understand how this issue can be frustrating, especially when the format appears valid.

As you are using the synchronous translator, it does not officially support .rtf.

It supports the following document formats: .txt, .txv, .tab, .csv, .html, .htm, .mhtml, .mht, .pptx, .xlsx, .docx, .msg, .xlf, .xliff.

It supports the following glossary formats: .csv, .xlf, .xliff, .tsv, .tab.

Here is supported documentation: https://learn.microsoft.com/en-us/azure/ai-services/translator/document-translation/overview#synchronous-supported-document-formats

Please accept this as an answer.
User's image

Thank you for reaching out to The Microsoft Q&A Portal

Share via

Synchronous document translation rejects any RTF snd DOC

1 answer

Your answer