A translated procedure can read perfectly and still send the reader to the wrong step when its numbering skips, restarts, or merges with a neighboring list. List formatting carries meaning, not just decoration, so check the structure as well as the translated words.
What list formatting actually includes¶
A list is a set of paragraphs with relationships between them. A visible number or bullet is only one part of the setup. The document also stores information about which paragraphs belong to the list, which level each paragraph occupies, where numbering begins, and how the marker sits beside the text.
That distinction matters when you translate a document. A translation workflow might keep every sentence but flatten the list into ordinary paragraphs. Another might retain the list but move a child item to the wrong level. Both files can look plausible at first glance, especially when a reader scans only the first few lines.
A numbered list normally communicates sequence, order, or a reference point. A bullet list signals a set of related items without necessarily ranking them. A multilevel list adds a hierarchy: a main item, a subordinate item, and perhaps another level below it. Translation must preserve those relationships even when the target-language text is longer or wraps differently.
The marker itself can be automatic or typed. In an automatic list, the word processor generates the number or bullet as part of the paragraph’s list formatting. In a typed list, someone has entered characters such as 1. or - directly into the text. Both can look similar on the page, but only the automatic version behaves as a connected list when items move or change.
Word also separates the marker’s appearance from the list-item text. Microsoft’s current guidance explains that selecting a bullet or number selects the markers in that list, while selecting list text affects the text and its numbering or bullets. That distinction is useful when a translation looks right but the marker has the wrong size, color, or format. See Microsoft’s instructions for formatting list markers.
A list’s structure can therefore be described through several checks:
- Membership: Which paragraphs belong to the same list?
- Sequence: Does numbering continue, restart, or begin at the intended value?
- Level: Does each paragraph sit at the correct place in the hierarchy?
- Marker: Is the item numbered, bulleted, or formatted with another marker?
- Layout: Do indentation, alignment, spacing, and the gap after the marker match the intended design?
Those checks apply to bullets too. A bullet list doesn’t have a numerical sequence to verify, but it still has membership, level, marker, and layout. An item that accidentally becomes ordinary text can break the visual rhythm and obscure whether it belongs under the preceding bullet.
For teams working across formats, list structure is one part of a broader document-formatting check. The same principle applies to preserving formatting in Word, PDF, and Excel documents: the readable text and the document’s underlying organization both matter.
Why lists change during translation¶
A word processor doesn’t decide that two paragraphs belong together just because their visible markers look alike. List membership and numbering settings live in document formatting. Translation and editing tools can alter those settings when they extract text, create new paragraphs, paste translated content, or rebuild a file.
A DOCX file can contain separate text runs and paragraph properties. A translation process that works paragraph by paragraph can retain more of that structure than a process that turns the whole document into plain text and reconstructs it afterward. Once paragraph relationships have been flattened, the output may need someone to rebuild list levels, numbering starts, and indentation.
Text length adds another complication. A translated phrase may take more or fewer lines than the source. Longer text can make a hanging indent look too shallow, cause a sub-item to wrap beneath the marker rather than beneath its text, or push the next item onto a new page. A line break alone doesn’t prove that numbering has failed, but it can make a broken list harder to spot.
Copying and pasting adds its own ambiguity. A pasted paragraph might inherit the destination’s list format, keep the source format, or arrive as plain text, depending on the action and the content. Word can also interpret text that resembles a list marker as the start of an automatic list. Microsoft’s current instructions describe how to turn off automatic numbered-list creation through Word’s AutoCorrect options on Windows. Check the current interface before changing that setting, since Microsoft’s documentation describes a particular product interface and may change.
In Microsoft’s current multilevel-list instructions, the setup includes choices for the number style, alignment, and text that follows the number, such as a dash or parentheses.
Those controls explain why two markers that both appear as 1. can still behave differently. One list might use a tab after the number; another might use a space. One might align the marker differently or restart at a specified value. A translated list can preserve the visible 1. but lose the spacing or alignment that made the page readable.
Nested lists need separate attention because a document can have several list levels with distinct formatting. Microsoft’s current support guidance says each level of a multilevel list can be reformatted by selecting a marker at that level. In practice, checking only the top-level numbers won’t tell you whether the second-level bullets have shifted or changed style.
Numbering controls also affect continuation. Word’s multilevel-list setup allows a level to link to an existing style, set a starting value, and restart lower-level numbering after a selected higher level, according to Microsoft’s current documentation. A translation that keeps the marker shape but loses the restart rule can produce a sequence that looks tidy while communicating the wrong hierarchy.
The practical takeaway is simple: compare the document’s structure, not only its appearance. A document can show consecutive numbers and still assign them to the wrong paragraphs. A bullet can look right while sitting at the wrong level. A matching marker doesn’t prove that a translated item belongs to the same list as its source counterpart.
A practical workflow for preserving lists¶
Start with a copy of the source file and a clear record of its list structure. The record doesn’t need to describe every font or margin. Note where each list begins and ends, how many items it contains, which items are nested, and where numbering intentionally restarts. That small map gives a reviewer something concrete to compare against the translation.
1. Mark list boundaries and hierarchy¶
Before translation, identify each distinct list. Note whether the list is numbered or bulleted, whether it contains sublevels, and whether it continues across a heading, page break, table, or other layout element. A numbered heading is not necessarily the same thing as a numbered procedure list, so record the purpose as well as the visible marker.
For multilevel lists, write down the intended relationship in plain language. For example, “A is a main step; A.1 and A.2 are details under A; B begins the next main step.” That note is more useful than a screenshot if the target language changes line lengths or page breaks.
A source document may already have inconsistent formatting. If one item uses a typed number while the rest use automatic numbering, don’t assume that translation will resolve the inconsistency. Flag it before work begins so the reviewer can decide whether to preserve the source or correct it as an agreed change.
2. Keep list paragraphs as list paragraphs¶
When possible, translate the editable document rather than copying its text into a separate plain-text field and rebuilding the layout later. The goal is to keep each item connected to its paragraph formatting and list level. For a Word file, that means preserving the paragraph’s list properties rather than reproducing only the visible number or bullet.
Avoid treating a marker and its text as one indivisible string if the document uses automatic numbering. The marker may be generated by the word processor rather than stored as part of the sentence. Translating a typed 1. as if it were ordinary text can lead to a duplicated number when Word adds its own marker.
A human editor may still need to rebuild a list if the translation route has stripped the structure. In that case, recreate the list intentionally: set the correct marker style, assign the right level, verify the starting value, and check where numbering should restart. Don’t repair only the first item and assume the rest have inherited the right settings.
3. Translate without changing item relationships¶
Translate the text inside each list item while keeping the item boundaries intact. If a source item contains two sentences, don’t split it into two list paragraphs unless the meaning and document owner call for that change. If several source items are combined, the reviewer needs to confirm that the new structure still communicates the same steps and references.
Longer target-language text may wrap onto more lines. Wrapping is a layout issue, not a reason to split an item automatically. A well-formatted hanging indent keeps continuation lines under the item text rather than under the number or bullet. Check that behavior after translation, especially for long instructions, legal clauses, and nested bullets.
Keep references to list items in the surrounding prose in sync. If a paragraph says “see step 4,” and the list is reordered or a new item is inserted, the reference may no longer point to the right place. A list can look flawless and still fail as a document if those cross-references have become stale.
4. Repair level and numbering settings deliberately¶
If an item has moved to the wrong level, Word exposes a Change List Level control for correcting it, according to Microsoft’s current list-formatting instructions. Use the control on the affected paragraph rather than fixing the indentation by adding spaces. Spaces can make the item look indented without changing its actual place in the list hierarchy.
For a multilevel list, inspect each level on its own. Check the marker style, alignment, indentation, and the text that follows the marker. Microsoft’s current setup instructions describe options for choosing whether a number is followed by a tab, a space, or nothing, as well as settings for indentation and alignment. Those are useful checks when a translated list wraps awkwardly or no longer lines up with the source.
Check the start value and restart behavior separately. A new main section might need to continue the main sequence, while its sub-items might need to restart. Don’t fix an apparent numbering error by typing over the marker before confirming the intended structure. A manually entered number can hide the symptom without correcting the underlying list.
5. Compare the source and translated lists¶
Compare each source list against its translated counterpart in a stable order:
- Count the items and compare their order.
- Check that every item remains a list paragraph.
- Inspect each nesting level separately.
- Confirm the starting number, continuation, and restart points.
- Review marker style, indentation, alignment, and spacing.
- Check wrapping, page breaks, and references to list items.
The sequence matters. Counting items first can reveal an omission or an accidental split before a reviewer spends time adjusting indentation. Checking the hierarchy next catches an item that has slipped out of its parent list. Layout checks come afterward because visual polish can’t compensate for a missing or misclassified instruction.
A reviewer should compare meaning as well as formatting. The first item might be numbered correctly but translated as a heading rather than an instruction. A sub-bullet might have moved to the top level and become a separate requirement. Read the text in order while following the markers; don’t rely only on visual alignment.
A useful QA sheet can have one row per list and columns for location, item count, nesting depth, numbering behavior, marker style, and review status. The sheet doesn’t need to reproduce the document. Its purpose is to make list checks repeatable across reviewers and versions.
Microsoft’s current instructions for multilevel lists describe linking a list level to an existing style, setting a starting value, and restarting lower-level numbering after a higher level.
Those settings are worth checking because an item can appear to belong to the right section while following the wrong numbering rule. A reviewer who checks only the visible sequence might miss that a child list should have restarted under a new parent.
6. Check the output in the application people will use¶
Review the translated file in the word processor where it will be edited or delivered. A rendered PDF can show spacing and page breaks, but it won’t reveal every list relationship. An editable Word document lets a reviewer inspect whether a paragraph belongs to a list and whether a level change is real or only simulated with indentation.
Word for the web supports standard bullets, numbering, and multilevel lists, while Microsoft’s current instructions say custom bullets require the desktop app. If a document uses custom markers, check it in the desktop application rather than assuming every editing environment can reproduce them identically. Product features and menus can change, so confirm the current instructions for the version in use.
LibreOffice Writer also supports numbering applied manually or through a paragraph style. Its help page recommends Heading Numbering rather than manual numbering for numbered headings. The same page says paragraph styles offer more control over numbering and that changing the list style assigned to a paragraph style updates paragraphs using that style. See LibreOffice’s numbering and paragraph-style documentation.
The application matters because list controls and behavior differ. A file can be opened in Word, LibreOffice, or a browser-based editor, and each environment may present different controls. The reviewer should record the application used for the final check, especially when another team will later edit the document in a different program.
When a list needs repair, and when it doesn’t¶
Not every visual difference is a structural error. A translated item may wrap to a second line because the target-language wording is longer. A number may sit slightly farther from the text because the document uses a different tab or indentation setting. Repair the formatting when the difference harms readability or changes hierarchy, not simply because every line break fails to match the source.
A list needs structural repair when an item has become plain text, numbering skips unexpectedly, a sub-item appears at the wrong level, or a sequence restarts where the source continues. A list also needs review when a marker is duplicated, missing, or styled differently from other items at the same level.
A list may not need repair when the only change is line wrapping and the continuation lines remain aligned with the item text. Nor does a translated list have to preserve the source’s exact line count. Languages differ in word length and syntax; the goal is to preserve order, meaning, hierarchy, and usable layout rather than identical page geometry.
Typed numbers can be appropriate for a short list that won’t change and has no cross-references. The tradeoff is manual maintenance. Inserting an item in the middle means checking every later number by hand, and a reviewer can miss one. Automatic numbering is more suitable when lists are long, frequently edited, or referenced elsewhere.
Word users can disable automatic numbered-list creation through File > Options > Proofing > AutoCorrect Options > AutoFormat As You Type, according to Microsoft’s current Windows instructions. That setting can help when the editor wants text that resembles a list to remain plain text. It doesn’t repair an existing list, and the menu names should be checked against the current Word version.
LibreOffice Writer describes a different useful editing behavior: pressing Enter in a numbered or bulleted list creates the next list paragraph, and pressing Enter again removes the marker from the new paragraph. That behavior helps explain why an accidental extra paragraph can create an unwanted list item. The LibreOffice help page is the reference for that editor’s current guidance.
Choose style-based numbering when a document repeats the same kind of list and consistent formatting matters. Styles can help keep list levels aligned across many sections. For a one-off document with many custom list types, applying a distinct paragraph style to every list may take more work than it saves. A Microsoft Q&A poster described that burden for contracts with many lists and sublists in different styles; the discussion is anecdotal and specific to that Word setup, but the tradeoff is practical.
What about bilingual side-by-side documents?¶
Parallel documents need a separate check for list membership. Two columns can show matching visible numbers while actually sharing a numbering sequence. A Microsoft Q&A user reported that a bilingual two-column Word table produced 1 - 2, 3 - 4 instead of matching pairs such as 1 - 1, 2 - 2. The report was posted in 2021 and describes one practical case, not a rule that applies to every Word document. Read the Microsoft Q&A discussion.
The user described the problem this way: “I need 1 - 1 2 - 2 3 - 3 but I always get 1 - 2 3 - 4 5 - 6.”
In plain terms, each language column was expected to have its own matching sequence, but the numbering ran through the two columns as one list.
The moderator’s answer in the same thread was to make the columns separate lists with the same visible numbering format. That approach keeps the numbers looking alike while giving each language its own list structure. The thread dates to 2021, so treat it as a documented failure mode to test rather than a universal Word rule.
For a bilingual table, check both the display and the list relationship. Confirm that the first source item corresponds to the first translated item, then verify that adding or moving an item in one column doesn’t alter the sequence in the other. Matching 1. markers alone don’t prove that the two lists are independent.
A parallel document can also fail in less obvious ways. One column may have a missing item, leaving the visible sequences correct but the translations out of alignment. A reviewer should compare the item content across columns, not just the numbering. If the two languages use different sentence lengths, a row may become taller without changing the list structure.
Common list errors and a final QA checklist¶
The most common review mistake is treating the marker as the whole list. A number that looks correct can be typed text, a marker from a different list, or a number generated by a sequence that continues elsewhere. Check the paragraph’s membership and level before deciding that a visual marker proves the structure is sound.
Another frequent mistake is fixing indentation with spaces. Spaces change the text position but don’t necessarily change the list level. A paragraph can look like a sub-item while remaining a top-level item in the document structure. Use the application’s list-level control or paragraph-style settings when the hierarchy is wrong.
Reviewers also sometimes check only the first and last numbers. A sequence might start and end correctly while containing a duplicated or omitted item in the middle. Compare item count and order, and read the translated text in sequence. A skipped number might signal an error, but it can also be an intentional continuation from an earlier section, so compare it with the source and the document’s numbering plan.
Restart points deserve their own check. A lower-level list may restart beneath each higher-level item, or continue through the whole document. Both patterns can be valid. The source’s structure, not a reviewer’s preference, determines which behavior the translated document should preserve.
Marker formatting can drift independently from the text. A second-level item might use a number when the source uses a bullet, or a marker might change size or alignment. Microsoft explains that multilevel list formatting can be adjusted one level at a time by selecting a marker at that level. Inspect nested levels individually rather than applying one broad formatting change to the entire list.
Use this final checklist before delivery:
- Every source item has a matching translated item, unless an agreed edit changed the list.
- Items appear in the same logical order.
- Every paragraph belongs to the intended list.
- Each nested item has the right parent and level.
- Numbering begins, continues, and restarts in the right places.
- Bullet and number styles match the intended level.
- Continuation lines align under the item text.
- Spacing and marker alignment remain readable.
- Cross-references to list items still point to the right content.
- Bilingual columns have independent numbering where the layout requires it.
- The file has been checked in an application that can inspect its list structure.
For team handoffs, record unresolved issues rather than silently hiding them. A reviewer might note that a source list uses inconsistent marker styles, or that an item appears to continue from a section outside the translated file. That note gives the next editor context and avoids turning a source inconsistency into an unapproved translation change.
A final layout pass should include the pages before and after each list. A list may continue across a page break, sit inside a table, or follow a heading that carries its own numbering. Those neighboring elements can affect how a reader interprets where the list begins and ends. A check that starts and stops at the first and last marker can miss that context.
In the Microsoft Q&A thread, moderator Stefan Blom advises: “These should be two different lists with the same “1, 2, 3, …” format (so that numbering is kept separate).”
That advice captures an important distinction for any translated document: identical appearance doesn’t require shared list structure. Separate lists can look consistent while keeping their numbering independent, which is especially useful for parallel language columns.
FAQ¶
How do I keep numbered lists and bullets when translating a Word document?¶
Keep the file editable and preserve each item’s list formatting instead of translating only the visible marker and text. After translation, compare item count and order, check each level, and review numbering, marker style, and indentation.
Why does Word numbering change after translation or copy and paste?¶
Word stores list membership and numbering separately from the words a reader sees. Pasted paragraphs can inherit a destination list, retain a source list, or arrive as plain text, so the visible result depends on the underlying formatting and the editing action.
How can I keep nested list levels consistent in a translated document?¶
Inspect each level separately and confirm that every sub-item remains attached to the correct parent. If an item has moved to the wrong level, use Word’s Change List Level control rather than adding spaces to imitate indentation, as described in Microsoft’s list-formatting guidance.
How should I check numbered lists after translating a document?¶
Compare item count and order first, then check list membership, nesting, start values, and restart points. Finish by reviewing marker style, indentation, alignment, spacing, page breaks, and references to list items.
How do I stop a bilingual Word table from numbering across both columns?¶
Give each language column its own list structure while retaining the same visible numbering format. A 2021 Microsoft Q&A discussion documents one case where two columns unexpectedly shared a sequence, so check both the visible numbers and the list membership.
Can I use typed numbers instead of automatic numbering?¶
Typed numbers can work for a short, stable list that won’t be reordered or referenced elsewhere. Automatic numbering is easier to maintain when items change, but reviewers still need to check its start, continuation, and restart behavior.