A table with intact borders can still be a failed translation: one cell may remain in the source language, a note may have slipped below the table, or a translated heading may wrap into a row that no longer fits the page. Preserving tables when translating DOCX files means protecting both the words and the relationships between cells, rows, columns, and page layout.
The tricky part is that a Word table isn’t just text arranged in boxes. Translation changes the amount of text, while Word stores table structure and formatting separately. A workflow that treats a DOCX as a stream of sentences can lose information even if the translated words look fine when copied into a plain-text editor.
This guide explains what breaks, how to choose a translation workflow, and how to check the delivered file. It also compares direct Word translation, translation by a human professional, and a document translation tool, with the trade-offs stated plainly.
What preserving a DOCX table actually means¶
A preserved table keeps the relationship between each source cell and its translated counterpart, along with the table’s visible layout and useful formatting. A document isn’t preserved just because it still has borders and a grid.
Microsoft describes DOCX tables as structured WordprocessingML elements. The table uses tbl; its grid and table-wide properties are represented separately; rows use tr; and cells use tc. Cell and row formatting also have their own properties. That structure is why a translation workflow needs to preserve more than the visible text in each box (Microsoft Open XML documentation, fetched 2025-11-06).
Think of a table as a small data model embedded in a document. A cell in the “Unit price” column has a meaning because it sits in a particular row and column. If a workflow extracts all the text, translates it, and reconstructs a table later, it has to recover those relationships as well as the words. Keeping the original structure while replacing the text avoids that separate reconstruction task.
Table preservation has several layers:
- Cell mapping: translated content stays in the cell that corresponds to the source cell.
- Completeness: every heading, note, label, and value that needs translation is handled.
- Formatting: emphasis, fonts, links, and paragraph formatting remain appropriate.
- Fit: longer or shorter text doesn’t clip, overlap, or make a row unreadable.
- Page flow: the table doesn’t create unexpected page breaks or push related content out of place.
A translation can pass one layer and fail another. A table might retain its cell mapping but have cramped row heights. A neat-looking table might still contain untranslated text. Treat text quality and visual layout as separate checks, then review them together before delivery.
Why tables break after translation¶
Table failures usually come from a mismatch between the document’s structure and the translation workflow, a change in text length, or both. Finding the cause helps you choose a repair that doesn’t damage the cells around it.
Flat text loses table relationships¶
A DOCX contains structural information beyond what a person sees on the page. When a process extracts only a list of text strings, it may no longer know which text belongs in which cell or how cells relate to the table grid. Reconstructing the table then becomes a separate job, rather than simply replacing its text.
That distinction matters in dense tables. Consider a form with a narrow label column, a wide explanation column, and a final column for a code or date. The phrase in each cell is meaningful partly because of its position. If content is moved, merged, or returned in a different order, the table may look almost right while giving the reader the wrong relationship between label and value.
Translation changes line breaks and cell height¶
A translation can take up more or less space than its source. A longer phrase may wrap onto additional lines, expand a row, or push the table onto another page. A shorter phrase may leave visible gaps or make a column look inconsistent with the rest of the document.
A participant in an RWS community discussion described the mechanism this way:
“the arrangement or layout of the text is messed up because your target sentences are longer than the text blocks or columns provided by the original document, so line breaks are inserted.”
The practical lesson is to check fit after translation, not to assume that source-language line breaks will remain suitable. A sentence can be accurate and still need a wider column, a different line break, or a review of the table’s page placement.
Fixed row heights can hide text¶
Microsoft says Word’s row height adjusts automatically to content until a user manually changes it. A manually constrained height can therefore cause trouble when a translated cell needs more room. The text may look clipped or cramped even though the cell still contains it (Microsoft’s table resizing guidance, fetched 2025-11-06).
A translation feature may miss some cells¶
A problem in a particular file or setup isn’t proof that a translation feature always fails. A Microsoft Q&A user reported that Word’s full-document translation left text in tables untranslated and shifted formatting on one computer, but not another (Microsoft Q&A report, user report posted in 2024; page fetched 2025-11-06).
Another commenter in the same discussion described partial translation and text appearing outside its original cell. Those reports are useful as reasons to validate the result, not as evidence that every Word translation behaves that way. Microsoft itself advises reviewing layouts, headings, tables, and spacing after translation because formatting may vary with document structure, length, and language (Microsoft Word guidance, fetched 2025-11-06).
Choose the translation route that fits the document¶
There isn’t one right workflow for every DOCX. The useful questions are whether the table structure must stay editable, how much review the content needs, and whether the job is a one-off document or part of a managed translation project.
| Route | Where it can fit | What to check | Main trade-off |
|---|---|---|---|
| Word’s built-in Translator | A document where a convenient first translated copy is useful | Every cell, table layout, spacing, and untranslated content | A separate translated copy is created, but layout still needs review |
| Human translator or translation agency | A document requiring human review, terminology decisions, or a specialist workflow | The brief, table mapping, and how the edited file will be checked | Human involvement does not remove the need to inspect the final DOCX |
| Document translation tool | A file-based workflow where the translated Word document and its layout matter | The table text, visual fit, and any flagged quality issues | The tool’s limits and review requirements still apply |
Word’s built-in Translator¶
Microsoft’s full-document Translator creates a separate translated copy and leaves the source unchanged. The documented route is Review > Translate > Translate Document; the translated copy opens in a separate window (Microsoft Support, support page fetched 2025-11-06).
Keeping the original unchanged is useful: you can compare the source and translated files without first making a backup copy. Microsoft says the full-document feature is available to Microsoft 365 subscribers and Office 2021 users, requires an internet connection and connected experiences to be enabled, and isn’t available to Microsoft 365 operated by 21Vianet. Availability can change, so check the current support guidance and your Word setup before relying on that route.
Word also supports translating selected text or a selected cell using Review > Translate. Microsoft documents this as a way to translate selected content, but doesn’t promise that every table’s layout will remain intact. A Microsoft Q&A user reported that translating a table selection worked in their situation when full-document translation ignored the tables; treat that as a troubleshooting option, not a guaranteed workaround (Microsoft Support; Q&A discussion, page fetched 2025-11-06).
A human translator or agency¶
A human translator can review terminology and meaning in context, including how a table’s headings relate to its entries. For a high-stakes document, ask how the provider will return the DOCX and whether the scope includes checking the table layout, not just translating text.
Don’t assume that “human translation” means the layout will be identical. The translator may work in the original DOCX, a CAT tool, or another format, and the workflow affects how the file returns. Agree on what counts as a complete deliverable: translated cells, retained structure, and a final visual check. If the document contains complex tables, send the editable source rather than a PDF export whenever possible.
An online document translation tool¶
A document tool can be useful when the task starts with a file and the required output is a formatted document, rather than translated text to paste back manually. Compare tools on the file formats they accept, what output they return, whether they preserve the source structure, and what checks they provide. Don’t treat a claim about formatting preservation as a guarantee that every cell will fit without review.
In ChatsControl, a DOCX is read paragraph by paragraph and cell by cell together with formatting such as bold, italics, fonts, and links. The translation is written back into the same paragraphs and runs, rather than being rebuilt from a flat text extract. That approach is designed to keep tables and layout in place. A translator can upload a DOCX through ChatsControl, then review the returned Word file. The tool isn’t a full CAT tool or TMS: it doesn’t provide translation-memory leverage or segment-level project management.
A separate option within a document workflow is bilingual review. ChatsControl displays source and translation together, with translated text highlighted and the original available on hover. That view can help a reviewer check whether a table heading, label, or value has been carried across correctly. The view supports review; it doesn’t replace checking the final Word layout itself.
Translate the DOCX directly, not through PDF by default¶
If the editable source is available, keep it in DOCX. Google Cloud’s documentation supports DOCX input and output and advises translating DOCX or PPTX directly before converting to PDF, because it generally preserves their layout and style better than PDF (Google Cloud document translation guidance, fetched 2025-11-06).
A PDF doesn’t behave like an editable Word table. Google Cloud warns that complex PDF layouts can lose formatting, including data tables, multi-column layouts, and graphs with labels or legends. Scanned PDF translation can also lose formatting. A conversion can introduce extra layout work before translation even begins.
The practical exception is when the PDF is the only available source. In that situation, don’t pretend it is equivalent to an editable DOCX: find a workflow that can interpret the page structure, and review the result against the original. A DOCX is usually the better starting point when the aim is an editable translated Word document.
Compare workflows by the work they leave you¶
A useful comparison looks beyond the initial translation. Ask how much checking and repair the returned file will need, and who is responsible for each part.
| Question | Word Translator | Human translator or agency | Document translation tool |
|---|---|---|---|
| Does the workflow start with the document? | Yes, for full-document translation | Depends on the agreed file workflow | Usually designed around file input |
| Does it create a separate translated copy? | Microsoft documents a separate copy | Confirm with the provider | Check the tool’s output workflow |
| Who checks meaning and terminology? | The user should review the result | The translator may review meaning as part of the job; confirm scope | Depends on the tool and its review features |
| Who checks that every cell fits? | The user must inspect the returned DOCX | Agree whether layout QA is included | Review the returned DOCX and any flagged issues |
| Is exact visual matching assured? | No; Microsoft says formatting may vary | Don’t assume so without an agreed scope | Don’t assume so from a formatting-preservation claim |
Word’s full-document translation produces a separate copy, but Microsoft’s own guidance still calls for reviewing layouts, headings, tables, and spacing. That is a useful standard for any route: treat the translated file as a deliverable to validate, not a finished layout simply because it opens.
A translation team should also decide who owns the final file check. If a linguist reviews meaning and a project coordinator returns the document, the handoff should specify whether the coordinator checks table completeness and page flow. Without that agreement, both people may assume the other person is checking the cells.
A DOCX table translation workflow, from source file to sign-off¶
A repeatable process makes it easier to catch missing text and fit problems before a translated document goes back to a client or stakeholder. The steps below work whether a translator uses Word, a human workflow, or a document translation tool.
- Keep an untouched source copy. Save the original DOCX separately before starting. Word’s documented full-document Translator creates a separate translated copy and leaves the original unchanged, but a separate backup helps when another workflow is involved (Microsoft Support).
- Inspect the source before translating. Open the document and note the tables that carry meaning: forms, lists of requirements, price or specification tables, and any table that continues across pages. Look for merged cells, narrow label columns, footnotes, and manually constrained row heights. Record any source text that shouldn’t be translated, such as an identifier or a code.
- Choose a workflow that keeps the table structure. Prefer processing the editable DOCX rather than copying all cell text into a separate text field and rebuilding the table later. If an operator proposes a PDF round trip, ask why the editable file can’t be used. Google Cloud advises translating DOCX directly when available because DOCX layout and style are generally preserved better than PDF (Google Cloud documentation).
- Translate and review terminology. Check headings and repeated labels consistently. A table can use the same label in several rows, so a small terminology change can create a visible inconsistency. Read the row as a unit: a heading may be grammatically sound on its own but misleading when paired with the values beneath it.
- Compare cell by cell. Use the source and target files side by side. Work from the top-left cell across each row, then continue to the next row. Confirm that all expected text appears in the translated file and that no translation has moved into a neighbouring cell or into a paragraph outside the table.
- Check fit and page flow in Word. Inspect line wraps, clipped text, blank cells, row heights, and page breaks. Review tables both at normal reading size and in print layout if the document will be printed. A table that fits on screen may still break awkwardly across pages.
- Repair only the problem that you found. If one column is too narrow, adjust that column rather than applying a broad change to the whole table. If a fixed row height clips text, revisit the row height. Recheck the neighbouring cells and the page after each change.
- Sign off against the source. Confirm that the final file has the expected table content and that the formatting remains usable. Keep the source and translated copies available for any later correction.
This sequence is deliberately more specific than “proofread the document.” A general read-through can miss an untranslated short label or a misplaced value because the page still looks orderly. A cell-by-cell pass checks the relationship that makes the table useful.
How to check a translated table for missing text and overflow¶
The strongest check combines a content comparison with a visual inspection. Neither one covers everything: extracted text can show that a phrase exists without revealing that it sits in the wrong cell, while a visual scan can miss a short untranslated label in a dense table.
Check content in a fixed order¶
Start with table headings, then move row by row. Compare each source cell with the corresponding translated cell and mark the result as one of three things: translated, intentionally unchanged, or needs follow-up. That simple distinction prevents codes, names, and values that should remain as written from being mistaken for omissions.
Pay particular attention to:
- Column headings and row labels.
- Short units, abbreviations, and notes.
- Cells that contain a mix of text and numbers.
- Repeated labels that must use the same translation.
- Footnotes or explanatory text placed immediately before or after a table.
- Text boxes and other content outside the table.
The last check matters because a page can contain relevant text that looks connected to a table but is stored separately. Google Cloud’s document translation guidance says text inside text boxes isn’t translated by its listed document translation support. That statement applies to the documented Google Cloud service, not to every translation tool, but it is a good reason to include text boxes in a file-wide QA pass (Google Cloud documentation, fetched 2025-11-06).
Check fit, not just presence¶
After confirming that the words are there, inspect how Word displays them. Look for text that touches borders, is clipped, wraps into an unexpected number of lines, or creates a row that is much taller than its neighbours. Check tables near page breaks and any row with a manually specified height.
Don’t shrink the font automatically at the first sign of overflow. A smaller font can make the table harder to read and may create an inconsistency with the rest of the document. First check whether the column widths, row height, or table width suit the translated content. If the problem is a single long phrase, a wording review may help, provided that it doesn’t change the meaning.
Track defects by type¶
A short issue list makes repairs easier to review:
| Defect | What to look for | First action |
|---|---|---|
| Missing translation | Source text remains in one or more cells | Compare the cell with the source and translate only the missing content |
| Cell mapping error | A value or label appears in the wrong place | Restore the correct text to its corresponding cell and recheck the row |
| Clipped text | A line is cut off or crowded by a border | Inspect row height and column width |
| Awkward page break | A table or related heading separates from its content | Review the table’s width and page flow |
| Inconsistent repeated term | The same label has different translations | Choose a consistent term and recheck every occurrence |
| Untranslated text box | A callout or label sits outside the table | Check the text box separately from the table cells |
ChatsControl’s automatic QA validator checks issues such as numbers, names, terminology, and omissions. That can help surface content problems for a reviewer, but it doesn’t make visual inspection redundant: the final DOCX still needs a check for fit, page flow, and any text that belongs outside the table. A validator is one check in the workflow, not a substitute for reading the file.
Fix column widths and row heights without creating new problems¶
Word offers different resizing options because “make this table fit” can mean different things. Microsoft documents AutoFit Contents, AutoFit Window, and Fixed Column Width; the right choice depends on whether the priority is fitting the words, fitting the page, or keeping the original column proportions (Microsoft table resizing guidance, fetched 2025-11-06).
Use AutoFit Contents when cells need more room¶
AutoFit Contents adjusts column widths to fit their content. That can help when a translated phrase is wider than its source and the table has room to expand. Check the result carefully: widening one column may leave less room for another or alter the balance of the table.
Use AutoFit Window when the table needs to fit the document width¶
AutoFit Window adjusts the table to fit the document window. Its goal differs from AutoFit Contents: one fits the table to the page width, while the other fits columns to their contents. If a table has one content-heavy column and several narrow fields, choose deliberately rather than expecting the two options to produce the same result.
Use fixed widths when column proportions matter¶
Fixed Column Width turns off automatic fitting. That can protect a layout where the relative width of each column is part of the design, but fixed widths can also leave translated text with too little room. After turning automatic fitting off, review wrapped text and row heights rather than assuming the source dimensions still work.
Microsoft also documents dragging column boundaries or entering a specific width as ways to adjust a table. For a targeted fix, change the column that has the problem and check the adjacent columns. Avoid dragging a boundary without watching the whole table: a local adjustment can affect the room available to neighbouring content.
Review row height after changing column width¶
Changing a column width can alter line wrapping and, in turn, the height a row needs. Word adjusts row height automatically until a user manually sets it. If the row has a constrained height, inspect whether the full translated text remains visible after any width adjustment (Microsoft Support, fetched 2025-11-06).
The goal isn’t identical geometry at any cost. A translated table can remain clear and usable even if a column is wider or a row is taller than in the source. Preserve the relationships and readability first; then decide whether the adjusted layout still matches the document’s purpose.
Common mistakes and how to avoid them¶
Most avoidable table problems come from treating a file conversion, translation, or visual check as proof that the whole job is complete. A few targeted checks catch the issues that otherwise survive until someone uses the document.
Converting an editable DOCX to PDF before translation¶
PDF can be appropriate when it’s the only source or when the final output specifically needs to be a PDF. Converting an available DOCX to PDF first adds a format change that can complicate table handling. Google Cloud advises direct DOCX translation when that source format is available and warns that complex PDF layouts, including data tables, can suffer formatting loss (Google Cloud documentation).
An RWS community reply also recommends obtaining the editable source when the input is a PDF, noting that conversion can change layout and create more formatting work. That discussion is historical and anecdotal, so use it as practical caution rather than a universal rule (RWS Community, page fetched 2025-11-06).
Assuming an intact grid means complete translation¶
A table can retain its borders while a cell remains untranslated. A Microsoft Q&A user described table text not being translated by Word’s full-document feature, and another commenter reported partial translation and text appearing outside its cell. These are individual reports, not proof of a general defect, but they show why checking only the visible grid isn’t enough (Microsoft Q&A discussion, page fetched 2025-11-06).
Check every cell that should contain translated text. If one or more cells are missing, test a selected-cell workflow or another method on a copy, then review the whole table again. Microsoft’s support guidance documents translating selected text or a cell; it doesn’t guarantee a specific layout outcome.
Resizing the entire table before finding the cause¶
A table may look cramped because a single row has a fixed height, because one column is too narrow, or because the translation itself needs a terminology review. Applying AutoFit to the whole table before identifying the problem can shift column proportions that were already working.
Find the affected cell first. Decide whether the issue is width, height, content, or page flow, and choose the matching repair. Microsoft documents separate options for fitting content, fitting the window, and holding column widths fixed, so those settings shouldn’t be treated as interchangeable (Microsoft Support).
Checking only the first page¶
A long document can have tables with different designs. One table may have flexible row heights; another may have fixed widths or continue across pages. A successful first page doesn’t demonstrate that later tables are complete or readable.
Review all tables, including those near the end of the document and those split across pages. Check headings that sit immediately before a table, since a layout change may separate the heading from the content it introduces.
Expecting a tool to guarantee the final appearance¶
Microsoft’s guidance is direct: review layouts, headings, tables, and spacing after translation, because formatting may vary with document structure, length, and language (Microsoft Word guidance). A file-processing method can preserve structure and still need a person to check how the translated text fits.
FAQ¶
How do I preserve tables when translating a DOCX file?¶
Use a workflow that translates text in the original table cells rather than flattening and rebuilding the content. Then compare the translated document with the source and inspect cell text, widths, row heights, and page flow.
Why do tables break after translating a Word document?¶
Translation can make text longer or shorter, changing line wraps and cell heights. Tables can also be damaged when a translation workflow extracts plain text instead of preserving Word’s table structure.
Should I translate a DOCX file directly or convert it to PDF first?¶
Use the DOCX when you have it. Google Cloud advises translating DOCX directly before converting to PDF because DOCX layout and style are generally preserved better than PDF (Google Cloud documentation, fetched 2025-11-06).
How can I check translated DOCX tables for missing or overflowed text?¶
Compare each source cell with its translated counterpart, check that every cell has content, and inspect clipped text, unexpected blank cells, row heights, and page breaks. Review the file in Word rather than relying only on extracted text.
How do I resize Word table columns after translation?¶
Use AutoFit Contents to size columns to their text, AutoFit Window to fit the table to the document window, or Fixed Column Width to stop automatic resizing. Choose based on the table’s purpose and inspect the result (Microsoft Support, fetched 2025-11-06).
Can Word’s built-in Translator preserve table formatting?¶
Word creates a separate translated copy, but Microsoft says formatting can vary with document structure, length, and language. Review tables and spacing after translation rather than treating layout preservation as guaranteed (Microsoft Word guidance, fetched 2025-11-06).