Azure single document translator (sync API) is not translating Graphs

II 105 Reputation points
2026-08-11T12:03:37.8766667+00:00

The below is the image of source and translated target. You can see the paragraphs are translated, however neither the chart legend not axis are translated. How can I fix this?chart translation problem

Azure Translator in Foundry Tools
0 comments No comments

1 answer

Sort by: Most helpful
  1. Jerald Felix 18,680 Reputation points Volunteer Moderator
    2026-08-11T17:04:02.8366667+00:00

    Hello II,

    Greetings! Thanks for reattaching the image, this makes the cause clear.

    Document Translation, whether you call the synchronous single-document API or the batch API, only walks the main document body text stored in word/document.xml inside the .docx package (along with headers, footers, and a few other standard parts). A native Word/Excel chart object embedded in the document stores its title, axis labels, category names, and legend text in a separate chart XML part (word/charts/chart1.xml and its related embedded workbook) rather than in the body text runs. The translation engine does not currently walk into that chart part, so every paragraph translates correctly while the chart title, axis labels, and legend stay in the source language, exactly what your screenshot shows.

    This is not something the sync API can be configured to fix. There is no request parameter on the single-document sync endpoint that extends translation into embedded chart parts, so this is expected behavior with the current service rather than a bug or misconfiguration on your end.

    The "translate text within images" feature will not help here either, even though it sounds relevant. That capability, available only through the batch Document Translation API with a Foundry resource and the translateTextWithinImage request option, detects and translates text baked into raster images (screenshots, scanned pictures) using Document Intelligence. Your chart is a live vector chart object, not an image, so that feature does not apply unless you first flatten it.

    Practical options, in order of effort:

    Manually retype the chart text after translation. For a small number of charts, this is the fastest path, click into the chart title, axis titles, and legend entries in the translated document and type the target-language text directly. Flatten the chart to a picture before translation, then use the batch API with translateTextWithinImage: true. In the source document, select the chart, copy it, and Paste Special as a picture (PNG) to replace the live chart. Submit that version through the batch endpoint with image-text translation enabled, and Document Intelligence will detect and translate the rasterized chart text along with the rest of the document. The trade-off is you lose the editable chart object in the output. Regenerate the chart from translated data. If the underlying chart data originates from an Excel source, translate the category labels, series names, and axis titles in the spreadsheet first, then let the chart in Word pull from the translated workbook. This gives the cleanest, fully editable result but requires access to the source data pipeline rather than just the finished report. If you need this handled automatically inside a single API call going forward, track the Foundry Tools "what's new" page for Translator, since image-in-document translation only reached general availability recently and native chart-part translation could plausibly follow the same pattern in a future update, but nothing is currently announced for it.

    If this answer helps you kindly accept the answer which will help others who have similar questions.

    Best Regards,

    Jerald Felix.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.