A single merged heading can make a translation quote look simple, while a nested table hidden inside a cell turns the file into a small structure-preservation project. The risk isn’t just a line wrapping badly: a translator or tool can miss text, move it outside the table, or leave the reader unsure which label belongs to which value.
The right workflow depends on what you’re translating. Word tables carry cell and paragraph structure inside a DOCX file; Excel worksheets have their own rules for merging and translating cell contents. In both cases, the safest approach is to treat the layout as information, not decoration.
What you need to preserve when translating a complex table¶
A table communicates through more than words. A heading may span several columns, a left-hand label may apply to multiple rows, and a smaller table inside a cell may hold detailed values for one main-table entry. Translating the text while losing those relationships can change the meaning even when every sentence looks correct.
A useful distinction is between content and structure. Content includes words, numbers, dates, and labels. Structure includes which cell contains each item, which cells are merged, how rows and columns relate, and whether one table sits inside another. A review that checks only the translated words can miss a structural error.
Merged cells carry relationships¶
A merged cell combines adjacent cells in the same row or column. In Word, the command is available through Table Layout > Merge Cells, and Word can also split or unmerge selected cells, as described in Microsoft’s instructions for merging or splitting table cells.
The resulting visual cell can span more than one column or row, but the underlying structure still has to express how it relates to the table grid. In WordprocessingML, the format used inside DOCX files, horizontal spanning uses w:gridSpan; vertical merging uses w:vMerge. A cell can use both properties, according to the OOXML reference for the Word table-cell element.
Those properties matter to a translation workflow because a file isn’t simply a grid of text boxes. A translation system that extracts text without tracking its source cell can lose the information needed to put each translated segment back in the right place. A human working directly in Word can make a similar mistake by copying a heading into a neighboring cell or by splitting a merged cell without recording the original layout.
Consider a project form with a merged left-hand cell labelled “Delivery details” beside several rows for address, date, and contact person. The phrase “Delivery details” applies to the group, not just to the first row. If a translation is moved into one row and the merged relationship disappears, readers may interpret the label as applying to only one field.
Nested tables are content inside a cell¶
A nested table is a table placed inside a cell of another table. WordprocessingML allows a table cell, identified by w:tc, to contain block-level content such as paragraphs and nested tables. A cell can therefore hold a heading paragraph, an inner table, and other paragraph content rather than one uninterrupted text string, as described in the OOXML cell reference.
The parent table and nested table have different jobs. The parent table may define a section or category, while the inner table holds detailed values. Translate the inner table without checking its parent cell, and the translated words might still be correct but no longer clearly connected to the right category.
A practical example is a main table with one row per service. One cell contains the service name and another contains a nested table with a list of included items. A translator who treats the nested table as a separate item could place it after the main table, where the list no longer identifies the service it describes.
The file format also includes a detail that’s easy to miss during programmatic processing: each w:tc cell must end with at least one paragraph element, w:p, even when the cell contains a nested table or has no visible text. That required paragraph may not look like meaningful content on the page, but it remains part of the document structure.
Translation changes the visual fit¶
A translated phrase may be longer or shorter than its source. A heading that fits in a merged cell in the source language may wrap to several lines in the target language. A table can grow in height, push content to another page, or split in a place that changes how readers scan it.
That doesn’t automatically mean the translation is wrong. The real question is whether the text remains readable and attached to the right row, column, heading, or nested table. Review the rendered document rather than judging only the editing view or the extracted text.
Microsoft describes a related accessibility concern: screen readers track their position in a table by counting cells. Merged cells, split cells, or a nested table can disrupt that count and prevent the screen reader from providing helpful table information. The Microsoft accessibility guidance for Word documents explains why table structure affects more than appearance.
A table that looks fine on a desktop screen can still be confusing when read with assistive technology. When accessibility matters, structure and headers deserve review alongside translated wording.
Why tables break during translation¶
Table problems often start before anyone edits the document. A workflow may flatten text into a sequence of segments, translate those segments, and then try to reconstruct the original layout. That can work for a simple table, but merged and nested structures give the reconstruction process more relationships to remember.
A DOCX file isn’t just a picture of a table¶
A DOCX file stores document structure, not only a picture of the page. WordprocessingML records cells, paragraphs, table properties, and formatting. In a merged cell, the grid relationship matters; in a nested table, the cell contains more than a single paragraph of text.
When a tool extracts a table into plain text, the visible sequence might look like this:
| Source view | Flattened sequence |
|---|---|
| Group heading spans several columns | Group heading |
| Row label and value | Row label, value |
| Inner table with its own labels and values | Inner labels, values |
The flattened sequence doesn’t show all the cell boundaries or the relationship between the inner table and its parent cell. Without that information, a tool or operator has to infer where each piece belongs when rebuilding the document.
A useful comparison is a set of labelled folders. Translating the words on the pages but discarding the folder labels leaves the content present but its relationships unclear. Table-aware processing aims to retain those boundaries while changing the text.
Merged cells can hide empty-looking structural cells¶
A vertical merge may appear as one tall cell in Word. In the underlying structure, the first cell starts the merge and later cells continue it. Continuation cells remain part of the table even when their paragraphs are empty or not visible in the rendered layout, according to the OOXML reference for w:vMerge.
That difference between what a person sees and what the file stores creates a common trap. A script that discards empty paragraphs or cells may also discard part of the structure that tells Word how to keep the merge intact. The result can be a broken table even though the visible source seemed to contain no text in the affected position.
Don’t treat every empty-looking cell as disposable. First check whether it is a continuation in a vertical merge, a deliberate spacer, a header cell, or an accidental blank. The answer determines whether to preserve it, change it, or ask the document owner to clarify.
A nested table may not appear in ordinary text extraction¶
A text extraction can return the words from the main table but fail to show the words inside a nested table in the expected order. Some processing methods may omit the inner table, while others may extract its content but lose the fact that it belongs to a particular parent cell.
Word’s whole-document translation workflow is available through Review > Translate > Translate Document and creates a translated copy in a separate window instead of replacing the source file, according to Microsoft’s translation guidance. A separate copy is useful for comparison, but the workflow doesn’t remove the need to inspect tables in the result.
A user report in a Microsoft Q&A thread about translating tables in Word describes text not translating, formatting changes, and some cell text moving outside the table. The thread contains user reports, not a Microsoft-confirmed general limitation, so treat it as a warning about a possible failure mode rather than a universal description of the feature.
An anonymous user wrote on May 17, 2024, in the Microsoft Q&A thread: “Now its a complete mess, some cells translate, others do not, formatting is lost and some cell text is taken right out of the table into a different part of the document.”
That report points to the exact checks a reviewer should make: coverage, cell position, and formatting. It doesn’t prove that every document translation will fail, but it does show why “the document opened” isn’t the same as “the table survived intact.”
Formatting can be a clue, not just a cosmetic issue¶
A border, shading pattern, or indentation can show which cells belong together. A missing border might make a merged heading appear to belong to one column rather than several. A lost indent can make a nested table look like another section of the outer table.
Keep formatting where it helps readers understand the structure. If a layout uses decoration instead of clear headers or relationships, translation is also a chance to ask whether the table can be simplified. Microsoft recommends avoiding tables when possible for accessibility and using a simple data-table structure with column headers when a table is needed. See the Microsoft accessibility guidance for Word.
Choose a workflow for Word, Excel, or a document tool¶
No single translation route fits every file. The best choice depends on the source format, how much table complexity the document contains, and whether you need a working spreadsheet or a translated document for review.
| Workflow | Useful when | Main limitation to plan for |
|---|---|---|
| Edit and translate directly in Word | The table is small, the structure is clear, and a human can inspect every cell | Manual copying can move text into the wrong cell or change merge relationships |
| Word’s built-in translation | You want a translated document copy for an initial review | A translated copy still needs a table-by-table check |
| Excel’s TRANSLATE function or Review > Translate | You need translations for text in a worksheet | Results must be copied and checked in the original workbook; cell layout isn’t a translation review |
| Document translation tool | The source is a DOCX or PDF and retaining document layout is part of the task | Support varies by file type; check whether the tool supports the source format and its structural edge cases |
| CAT tool with a document conversion or interchange workflow | The work needs a managed translation process and a way to transfer content between tools | The interchange format must retain enough structure and inline data to rebuild the native file |
Use Word for careful manual work on a manageable table¶
Direct editing in Word gives a translator access to the original rows, columns, and cell boundaries while translating. That visibility helps with smaller tables whose structure is already sound. The translator can click into a cell, preserve the merge, and check how the target text wraps.
For a careful workflow, keep the source copy unchanged, translate within the working copy, and compare the two documents side by side. If a cell contains a nested table, inspect it as a separate unit while keeping track of its parent cell. When a heading spans columns, translate the heading once rather than copying it into individual cells unless the document owner specifically wants that change.
Manual work becomes harder when the document contains many tables, repeated terms, or extensive nested content. A human still needs to review meaning and layout, but repetitive cell-by-cell handling increases the chance of a missed row or an accidental structural change.
Use Word’s translation feature as a draft, not a final table check¶
Microsoft’s documented whole-document workflow creates a translated copy in a separate window. That protects the original from being replaced by the translation, but it doesn’t tell you that every table has been translated correctly. Compare the copy with the source and review the complex tables individually.
Word can also translate selected text through Review > Translate. Microsoft says the selected-text or cell workflow is available in Word, Excel, and PowerPoint. The exact handling differs by application: Excel doesn’t offer an Insert button in this workflow, so the translated result has to be copied and pasted into the worksheet. Check Microsoft’s guidance on translating text before relying on the feature in a particular Office setup.
Office translation requires an internet connection and connected experiences to be enabled. Microsoft documents the feature for Microsoft 365 subscribers and Office users; availability and interface details should be checked against the current Microsoft translation instructions. Those conditions are product requirements, not a guarantee that the table structure needs no review.
Use an Excel formula for cell text, then place the result deliberately¶
Microsoft’s Excel TRANSLATE function accepts a text string or cell reference. Its syntax is =TRANSLATE(text,[source language],[target language]), and the optional language codes identify the source and target languages. The function’s documented behavior and supported language details are in Microsoft’s TRANSLATE function reference.
For a known source language, specify it rather than relying on automatic detection, especially when the cell contains a short label. A short heading such as “Open” can be ambiguous without context. Review the output before replacing source text, and keep the source available so a reviewer can compare the wording.
Excel also has a Review > Translate route for selected text or a cell. In that workflow, Excel doesn’t provide an Insert button, so copy the translation back into the intended cell and verify that the destination is correct. A formula-driven working column can help preserve the original while the translation is reviewed, but the workbook still needs a human check for relationships between headings, merged cells, and values.
The TRANSLATE function isn’t a substitute for a table-aware workflow. Microsoft notes that its supported languages and results can change as languages are added or removed. The documentation lists errors that include text that is too long for a cell, a non-text value, an unsupported language code, and throttling. Check the current function documentation if a formula returns an error.
Use a document workflow when the deliverable is a DOCX or PDF¶
A document translation tool can make sense when the job is a file that needs to come back as a document rather than as a list of strings. The useful question isn’t only “Does it translate?” Ask what it does with cell boundaries, merged content, nested tables, and the output format.
In ChatsControl, a DOCX workflow reads text paragraph by paragraph and cell by cell with its formatting, then writes translated text back into the same paragraphs and runs. For a supported DOCX, that means the table is processed as part of the document rather than rebuilt from a plain-text dump. The tool also provides a bilingual review view, so a translator can compare source and translation while checking whether text sits in the right place.
ChatsControl supports DOCX and PDF, not Excel or PowerPoint. A PDF workflow first reconstructs editable Word content, including tables and text positions, then translates the resulting document; the deliverable is a Word file. The format and reconstruction step matter: if you need an Excel workbook, this isn’t the right route. For a PDF with complex tables, inspect the reconstructed structure and the translated output rather than assuming that an original-looking page guarantees a correct cell map.
Understand the role of an interchange format¶
A CAT tool may use an interchange format to move text between a source document and a translation environment. XLIFF 2.0 is an interchange format intended to be understood across localization providers and tools, with a primary focus on lossless interchange, according to the OASIS XLIFF 2.0 standard.
“Lossless” is a goal of the interchange process, not a reason to skip checking the returned file. XLIFF explains that original inline-code data may be needed to recreate the native format when translated content is merged back. If the XLIFF file doesn’t store that data, the originating tool needs another way to recreate the format. That matters when a table’s formatting or inline elements carry structural meaning.
The OASIS XLIFF 2.0 standard describes XLIFF as “the XML Localisation Interchange File Format designed by a group of multilingual content publishers, software providers, localization service providers, tools providers and researchers.”
For a translator or project manager, the practical point is to check the full round trip: what the source tool exports, what the CAT environment receives, and what the originating tool can rebuild from the translated file. If the return path can’t reproduce the native table structure, the translation may need a separate formatting pass.
A practical workflow for preserving merged and nested tables¶
A table-safe workflow starts with the source, not the translation. Before editing, establish what the table is meant to communicate and which parts of its structure must stay intact.
Step 1: Keep an untouched source copy¶
Save the original file separately from the working copy. The source is the reference for text, cell boundaries, formatting, and table order if a later step changes the layout.
For a Word document, create a working copy before using whole-document translation or making structural edits. Microsoft says Word’s built-in whole-document workflow creates a separate translated copy, but keeping a source copy outside that process gives the team a clear baseline for comparison. The workflow is documented in Microsoft’s translation guidance.
For Excel, retain the source values in the workbook or a separate copy before filling formulas or pasting translations. That safeguard matters because formula results can replace the original text if they’re copied over the source cells.
Step 2: Map the table before translating¶
Identify the outer table, its merged cells, and any nested tables. Note which merged headings apply to which rows or columns, and record whether a nested table belongs to a particular parent cell.
A simple inventory is enough for many documents:
| What to record | What to look for |
|---|---|
| Table purpose | What information does the table present? |
| Headers | Which row or column labels identify the values? |
| Merged cells | Does a label span columns or rows, and what does it apply to? |
| Nested tables | Which parent cell contains each inner table? |
| Blank-looking cells | Are they real blanks, merge continuations, or spacing? |
| Special content | Are there numbers, dates, codes, or links that need exact checking? |
Mapping is especially useful when the visual layout is irregular. A heading spanning columns can be obvious to the eye but easy to lose in a text-only export. A short note beside the table can record the relationship without changing the file itself.
Step 3: Decide whether a merge is meaningful¶
Don’t unmerge cells simply because they look difficult to translate. A merge may express a real relationship, such as one category label applying to a group of rows. Removing that merge can make the document easier to process while making it harder to understand.
Ask what the merge does. If a heading spans several columns because it labels them as one group, keep the relationship and translate the heading as one unit. If a merged layout is being used only for visual positioning and creates accessibility or editing problems, discuss a simpler structure with the document owner.
Word allows adjacent cells in a row or column to be merged and selected cells to be unmerged, as shown in Microsoft’s cell-merging instructions. The command changes the table, so keep the source and note what changed before modifying a working copy.
Step 4: Translate within the right structural unit¶
For Word, translate each paragraph and cell while keeping track of the parent table and any nested table. Don’t treat a nested table as an independent table with no connection to the surrounding row. Translate headings, labels, and values in a way that preserves their relationship.
For Excel, translate the intended cell text and place the result back in the right cell. If a formula is used, keep the source and result separate during review. The function translates a text string or cell reference, but it doesn’t decide which heading should apply to which group of cells.
ChatsControl’s bilingual review view addresses a related review need for DOCX and PDF workflows: the source and translation appear together, with translated text highlighted and the original available on hover. A reviewer can use that view to check a translated line against its source, then inspect the actual returned Word file for layout. The tool doesn’t support Excel, so spreadsheet work needs a separate worksheet workflow.
Step 5: Check coverage before polishing wording¶
Confirm that every visible text item has a translation, including content inside nested tables, headings, footnotes in cells, and labels in merged areas. Then check that no source text has disappeared and no translated text has moved to an unrelated cell.
Coverage review is different from language review. A sentence can be fluent and still be in the wrong row. First confirm that the translation is present and correctly placed; then assess terminology, tone, and meaning.
For a long or repeated table, compare labels and values systematically. Look for duplicate translated segments, missing units, a heading that appears only once when it should label a group, and source text that remains untranslated. A reviewer can mark each row as checked rather than relying on a quick visual scan.
Step 6: Render the file and inspect the page¶
Open the translated document in Word and inspect the page view. Look for text wrapping, row height, column width, page breaks, clipped content, and unexpected blank rows or columns. Microsoft explicitly advises visually checking for blank rows and columns as part of its accessibility guidance for Word tables: Make your Word documents accessible.
A layout change isn’t automatically a defect. Translation can change line length, so a row may become taller. The defect is a change that hides text, obscures the relationship between label and value, or makes the table hard to navigate.
Also open the document in the application that will be used for delivery or review. A table can look different in a preview, a browser, or another word processor. If recipients rely on a specific Office format, inspect the file in Word before delivery.
Step 7: Run a structure and accessibility check¶
Use Word’s Accessibility Checker to look for tables containing split cells, merged cells, or nested tables. Microsoft says the checker can flag these structures, and its guidance recommends simple data tables with column headers where tables are necessary. The checker doesn’t decide whether a merge is appropriate for your content, but it can bring a structural issue to your attention.
Set or confirm header rows when the table uses column headings. Microsoft explains that header rows communicate table information to Word and assistive technologies, helping users understand the content. A translated heading should remain identifiable as a heading, not merely look like one through bold formatting.
Treat a warning as a prompt to review, not an automatic instruction to flatten every table. A complex table may be required for the document’s purpose. If the content can be represented as a simpler table without losing meaning, simplification can improve both accessibility and translation review.
Step 8: Compare source and target cell by cell¶
Finish with a source-to-target comparison. For each table, verify the labels, values, merged relationships, nested contents, and visual layout. When a document contains multiple tables, check them individually instead of assuming that a successful review of one applies to the rest.
For a DOCX, compare the original and translated files side by side. For Excel, compare the source and destination cells in the workbook and check formulas or copied values. Keep the source available until the translated file has passed content, structure, and visual review.
The pitfalls that cause avoidable rework¶
Most serious table defects don’t come from one complicated technical problem. They come from a small assumption: that an empty cell contains nothing important, that a merged heading can be copied anywhere, or that a translated document must have preserved the original because it opens successfully.
Unmerging Excel cells can delete text¶
Excel has a data-loss risk that deserves special attention. When cells are merged in a left-to-right worksheet, Excel keeps the content from the upper-left cell; contents from the other selected cells are deleted. For a right-to-left worksheet, Excel keeps the upper-right cell’s content instead. Microsoft describes this behavior in its instructions for merging and unmerging Excel cells.
That rule matters before translation as well as after it. If several cells hold different text and a user merges them to make the worksheet look cleaner, the merge can remove content. Unmerging later doesn’t restore deleted values. Save a copy or consolidate the contents deliberately before merging.
Excel also doesn’t make its Merge Cells feature available when the selected cells are formatted as an Excel table. If the command is disabled, check whether the range is formatted as an Excel table and consult the current Microsoft instructions rather than changing the data structure without a plan.
Removing empty cells can break a vertical merge¶
A Word table may store continuation cells for a vertical merge even when those cells appear empty. A processing step that removes empty paragraphs or cells can disrupt the merge. The OOXML reference for vertical merging explains that later cells continue the merge started by the first cell and remain part of the table structure.
Before deleting an apparently empty cell, check whether the cell belongs to a merge, marks a row boundary, or provides space between sections. A visible blank isn’t proof that the underlying element can be removed safely.
Moving nested content can detach it from its label¶
A nested table’s position tells readers which parent entry it belongs to. Moving it below the outer table may preserve all the inner text but remove the relationship that gives the information meaning.
Check the parent cell after every translation or conversion step. If the nested table appears elsewhere in the document, return it to the cell that introduces or labels it. If the table can’t be placed back without damaging the layout, stop and identify whether the conversion or the original structure caused the problem.
Relying on automatic language detection can misread short text¶
Short cell labels can be ambiguous. Microsoft’s Excel TRANSLATE documentation says source-language detection is supported for most languages but recommends specifying a known source language, especially for short text. The current function reference also notes possible errors such as unsupported language codes, non-text values, and throttling.
A short label may be a noun, a verb, a status, or an abbreviation. Give the translation workflow enough context to choose the intended meaning, and review abbreviations and one-word labels against the surrounding rows.
Treating an accessibility warning as a formatting task alone¶
A merged cell may look neat and still make a table difficult to navigate with a screen reader. Microsoft explains that screen readers track their position by counting cells, and nested, merged, or split cells can disrupt that count. The warning is about how people interpret the table, not only whether its borders align.
Where the table’s purpose allows it, use a simple structure, clear column headers, and a logical reading order. Where a complex layout is necessary, review it with the document’s accessibility requirements in mind instead of assuming that visual polish resolves the issue.
Microsoft Support explains that “Screen readers keep track of their location in a table by counting table cells. If a table is nested within another table or if a cell is merged or split, the screen reader loses count and can’t provide helpful information about the table after that point.” Read the Word accessibility guidance.
The quote is a reminder to review how the table communicates, not merely how it looks. If the structure makes the reading order hard to follow, consider whether the information can be reorganized before translation.
A comparison checklist for choosing a workflow¶
The right approach is the one that fits the source format and gives you a reliable way to inspect the result. Use this checklist before assigning a job or choosing a tool.
| Question | Manual Word or Excel workflow | Document translation tool | CAT or interchange workflow |
|---|---|---|---|
| Is the source a DOCX? | A translator can work directly in the file | Check whether the tool processes table cells and returns a Word file | Check how the tool imports and rebuilds table structure |
| Is the source an Excel workbook? | Work in Excel and preserve source values | Confirm spreadsheet support; ChatsControl doesn’t support Excel | Check whether workbook structure is in scope |
| Does a cell contain another table? | Track the inner table and its parent cell | Test whether the workflow retains both levels | Verify that the export and return path preserve the relationship |
| Are there merged cells? | Keep a map of what each merge labels | Check that the translated text remains in the same structural unit | Verify that merge-related structure survives import and export |
| Does the final layout matter? | Render and inspect the finished file | Review the returned document, not just the text | Confirm that inline and native-format data can be restored |
| Who checks the content? | A translator or reviewer compares source and target | Use a bilingual review view if available, then inspect the file | Assign linguistic and layout checks separately |
A team may use more than one route. A document can go through automated translation for a draft, human post-editing for terminology and meaning, and a separate formatting review before delivery. The important part is assigning responsibility for every check, rather than assuming the tool or the translator has covered all of them automatically.
For clients who need a finished document rather than translated strings, clarify the expected deliverable before starting: a translated DOCX, an edited Excel workbook, a bilingual table, or text ready to import into another system. The file format affects both the workflow and what “preserved” means.
FAQ¶
How do you translate a Word table with merged cells without breaking its layout?¶
Preserve the existing table structure, translate the text in each cell, and compare the result with the source for missing content, changed row relationships, and layout shifts. Avoid unmerging cells unless you’ve backed up the file and mapped what each merge means.
How should translators handle nested tables in a DOCX file?¶
Treat a nested table as content inside its parent cell, not as a separate object outside the document structure. Check the parent cell, the inner table, and the paragraph Word requires at the end of the cell, even when that paragraph has no visible text.
Can Excel translate text in merged cells without losing data?¶
Excel’s TRANSLATE function can translate text or a cell reference, but the worksheet still needs a structural review. Before merging cells, preserve any content outside the upper-left cell in a left-to-right worksheet because Excel deletes the other selected cells’ contents during a merge.
Should merged cells be unmerged before translation?¶
Not by default. Unmerging can change the table’s meaning or appearance, so first decide whether the merge expresses a real relationship or only a visual layout choice.
How can you check whether a translated table preserved all cell content?¶
Compare source and target row by row and cell by cell, including nested tables and blank-looking merge continuations. Then render the translated file and run Word’s Accessibility Checker to look for table issues.
Does ChatsControl translate Excel spreadsheets?¶
No. ChatsControl supports DOCX and PDF document translation, not Excel or PowerPoint files. For an Excel worksheet, translate and review text in an Excel workflow, then check the copied results in the original workbook.
Does a translated document need a human review if a tool kept the formatting?¶
Yes. Preserved formatting doesn’t prove that every cell was translated, that values remained in the right rows, or that the wording is accurate. Review content, structure, and rendered layout as separate checks before delivery.