Formatting Issues with Borderless Tables in PDF Translation using Azure Translator API

Amulya Sharma 20 Reputation points
2025-08-13T08:44:28.2266667+00:00

There is a formatting issue when translating PDFs with the Azure Translator API, particularly with borderless tables. It has been noted that this is a known problem. Are there any workarounds available, aside from manually converting tables to have borders?

Azure AI Translator
Azure AI Translator
An Azure service to easily conduct machine translation with a simple REST API call.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Pavankumar Purilla 10,680 Reputation points Microsoft External Staff Moderator
    2025-08-14T05:35:46.1133333+00:00

    Hi Amulya Sharma,

    This behavior is a documented limitation of the Azure Translator service when processing PDFs that contain borderless tables. In such cases, the service may not correctly identify the table structure during translation, which can cause formatting issues in the translated output. As per the current known issues for Translator, the recommended workaround is to modify the source file so that the tables have visible borders before running the translation. Bordered tables are detected more reliably by the document translation pipeline, which helps preserve their layout in the output.

    At present, there is no configuration or API parameter that can automatically correct formatting for borderless tables. If updating the source document is not feasible, you could consider preprocessing it programmatically to add faint borders around tables or extracting the table data and translating it using the Translator text API, then reassembling it into a PDF with proper formatting. However, these are manual or custom workflow solutions, and the only officially supported method to mitigate this issue is to ensure tables have borders prior to translation.


Your answer

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