If you want to know how to translate bullet points, numbered lists and parallel structure, the first rule is to treat the list as a grammatical and logical system rather than a pile of short sentences. A list can encode sequence, priority, alternatives, cumulative requirements, examples, exceptions or parts of one larger sentence. Preserving the words but changing the list logic can produce a fluent translation that is operationally wrong.
Good list translation therefore requires structure preservation as well as language accuracy. The translator has to keep the correct number of items, nesting, numbering, scope words, grammatical parallelism and relationship to the lead-in. In high-stakes instructions, policies, forms and educational materials, a single changed “all,” “any,” “must,” “may” or exception can alter what readers are required to do.
The easiest reliable method for translating bullet points and numbered lists is to map four things before wording: list purpose, lead-in scope, item grammar and hierarchy. This guide connects with eduKateSG’s Master Art of Translation, the sentence-structure guide, and the translation verification guide.
Why list translation is a logic problem
Bullet points and numbered lists look like formatting, but they often encode logic: all conditions versus any condition, sequence versus unordered options, examples versus requirements, causes versus consequences, or parts of a larger sentence.
Main risk: A translation can preserve every bullet and still change meaning if the lead-in no longer combines grammatically with the items, if parallel structure breaks, or if numbering suggests a sequence the source never intended.
Translation method: undefined
Read the lead-in together with every item
Many lists are grammatically dependent on the sentence before the colon. Each bullet may complete that sentence rather than stand alone.
Main risk: Translate the lead-in and items as one syntactic system. Test every bullet by reading it after the lead-in. If one no longer forms a grammatical or logical whole, revise the set.
Translation method: undefined
Identify whether the list is ordered
Numbered lists may indicate sequence, priority, ranking, cross-reference or merely visual organisation. Bullets often signal unordered items, but not always.
Main risk: Do not change bullets to numbers or numbers to bullets unless the task allows it. The visual marker can carry procedural meaning.
Translation method: undefined
Preserve all-versus-any logic
A lead-in such as “You must meet all of the following requirements” differs fundamentally from “You must meet one or more of the following.”
Main risk: Translate quantifiers in the lead-in with special care. A perfectly translated bullet set becomes legally or practically wrong if the list operator changes.
Translation method: undefined
Preserve exceptions and alternatives
Lists often contain items connected by hidden and/or logic. Punctuation alone may not show whether items are cumulative, alternative or optional.
Main risk: Recover the logical relationship from the lead-in, surrounding text and source style. Make conjunctions explicit in the target when ambiguity would otherwise increase.
Translation method: undefined
Maintain grammatical parallelism
Parallel lists normally keep items in the same grammatical form: all noun phrases, all imperative verbs, all infinitives, all gerunds or all complete sentences.
Main risk: A target language may require different morphology, but the items should still feel structurally parallel. Mixed forms can make one item look more important or semantically different.
Translation method: undefined
Do not preserve awkward source parallelism blindly
A source list may itself be inconsistent because different authors edited it over time.
Main risk: If the translation brief permits copy-editing, regularise grammar without changing meaning. If documentary fidelity is required, preserve the inconsistency or flag it rather than silently rewriting the source logic.
Translation method: undefined
Keep scope from the lead-in
A word in the lead-in can apply to every bullet: must, may, includes, excludes, before, after, only, except, at least or no more than.
Main risk: When the target syntax forces repetition, repeat that scope accurately. When it permits omission, make sure readers still understand that the operator governs all items.
Translation method: undefined
Translate imperative lists consistently
Instructions often begin each item with a command: open, select, check, save, restart.
Main risk: Use the target language’s normal imperative or procedural style across the whole sequence. Do not switch randomly between command forms, infinitives and descriptive statements.
Translation method: undefined
Translate noun-phrase lists as noun phrases
Feature lists, requirements and classifications often consist of compact noun phrases rather than sentences.
Main risk: Expanding some items into full sentences can disturb visual balance and suggest extra explanation. Preserve concise nominal style when the source uses it intentionally.
Translation method: undefined
Translate sentence lists as sentences
When every bullet is a complete proposition, sentence punctuation and capitalisation usually matter.
Main risk: Follow target-language list style consistently. A sentence list should not alternate between fragments and full clauses unless the source does so for a reason.
Translation method: undefined
Preserve hierarchy in nested lists
Second-level bullets may explain, qualify or subdivide the parent item. Flattening them into one level can change which condition they belong to.
Main risk: Keep indentation and hierarchy aligned with semantic scope. If the target platform cannot preserve nesting, use explicit labels or wording to restore the relationship.
Translation method: undefined
Preserve numbering used for cross-reference
Contracts, manuals, standards and procedures may refer later to “item 3,” “step 4” or “condition (b).”
Main risk: Never renumber casually. Changing structure can break internal references elsewhere in the document.
Translation method: undefined
Preserve step sequence
Procedural numbered lists often encode chronological order. Even if the target wording reads more smoothly in another order, rearranging steps can change outcomes or safety.
Main risk: Translate content within the existing sequence unless the source itself is being redesigned under an explicit brief.
Translation method: undefined
Preserve priority ranking
Some numbered lists rank options from highest to lowest priority rather than indicating chronological steps.
Main risk: Do not rewrite numbering as neutral bullets. State priority clearly if the target language or layout makes the ranking ambiguous.
Translation method: undefined
Preserve examples versus requirements
A list introduced by “for example” is illustrative; a list introduced by “must include” is exhaustive or mandatory.
Main risk: Translate the lead-in so readers know whether omitted items are allowed. This distinction is critical in legal, educational and compliance text.
Translation method: undefined
Translate punctuation by target style
Source punctuation helps signal whether bullets continue a sentence or stand independently, but punctuation conventions differ across languages and style guides.
Main risk: Preserve the grammatical function rather than mechanically copying every mark. Keep punctuation internally consistent across the list.
Translation method: undefined
Preserve labels and bold lead words
Some lists begin each bullet with a bold category label followed by explanation.
Main risk: Translate the label as a stable term and preserve its relation to the explanation. Inconsistent labels can break scanning and terminology consistency.
Translation method: undefined
Lists in forms and checklists
Checklist items may be noun labels, questions, confirmations or actions. Their brevity is functional because users scan and tick them.
Main risk: Do not expand compact items unnecessarily. Preserve actionability and one-item-one-check structure.
Translation method: undefined
Lists in safety instructions
Warnings often separate hazards, consequences and required actions into bullets.
Main risk: Keep each safety function distinct. Combining bullets may hide a critical action or make a consequence look optional.
Translation method: undefined
Lists in educational material
Learning objectives, success criteria and marking points often rely on parallel verbs such as identify, explain, compare and evaluate.
Main risk: Translate command verbs consistently so students and teachers can distinguish cognitive demands across the list.
Translation method: undefined
Lists in ecommerce and specifications
Product specifications use repeated labels, units and compact values. Consistency supports comparison.
Main risk: Translate labels, preserve units accurately, and avoid turning one specification into marketing prose while the others remain factual.
Translation method: undefined
Lists in contracts and policies
Eligibility criteria, exclusions and obligations often use nested numbering and cumulative logic.
Main risk: Treat list structure as part of the legal meaning. Scope words such as all, any, unless and except deserve explicit verification.
Translation method: undefined
Lists in software interfaces
Menu items and settings lists may have strict length limits and established terminology.
Main risk: Keep structural order and terminology aligned with the interface. Do not translate a list item differently from the corresponding button or screen label.
Translation method: undefined
Lists in tables and compact layouts
A list can appear inside a table cell, callout or compact layout where line length matters.
Main risk: Preserve information architecture as well as wording. Excessively long target items can destroy comparability and scanning even when semantically correct.
Translation method: undefined
Parallelism across headings
A sequence of subheadings can function like a list: Plan, Build, Test, Release.
Main risk: Translate them with comparable grammatical form and rhythm so the structural relationship remains visible.
Translation method: undefined
Parallelism with negatives
Lists such as “Do not copy, do not omit, do not invent” depend on repeated negative scope.
Main risk: If the target language can state the negation once over all items, ensure scope remains unmistakable. Otherwise repeat it.
Translation method: undefined
Parallelism with comparative forms
Items may all begin with more, less, faster, safer or better, creating a rhetorical pattern.
Main risk: Preserve the comparison frame consistently. Breaking one item into a different construction weakens the list’s rhetorical logic.
Translation method: undefined
Parallelism with questions
FAQ-style or diagnostic lists may repeat a question pattern: What happened? Why? What next?
Main risk: Maintain the interrogative structure and sequence so readers can scan the reasoning framework.
Translation method: undefined
Avoid hidden subject changes
A list may begin with “The student should:” and contain verbs whose implied subject is the student. One mistranslated bullet can accidentally shift the subject to teacher, school or parent.
Main risk: Test implied subjects throughout the list and make them explicit where target grammar needs clarification.
Translation method: undefined
Avoid hidden tense changes
Parallel bullets can share tense or modality from the lead-in. A target item translated in a different tense may imply different timing or status.
Main risk: Check all items together for temporal consistency rather than proofreading them independently.
Translation method: undefined
Check list item boundaries
Source formatting sometimes breaks one logical item into two lines or merges two independent items into one bullet.
Main risk: Translate semantic units, not visual line breaks. Preserve the intended number of items while fixing accidental line wrapping.
Translation method: undefined
Do not translate markup as content
Bullets, numbering symbols, checkboxes, HTML tags and document markers are structural rather than lexical.
Main risk: Preserve or localise formatting according to platform rules without inserting those markers into the translated sentence itself.
Translation method: undefined
Keep accessibility intact
Screen readers depend on true list structure rather than manually typed bullets or numbers.
Main risk: When publishing multilingual content, preserve semantic list markup so accessibility survives alongside the translation.
Translation method: undefined
Check punctuation after expansion
Target languages can expand text substantially. A bullet that was a short phrase may become a complex clause.
Main risk: Re-evaluate punctuation and internal commas so the item remains readable, but do not change its logical level or scope.
Translation method: undefined
Review the list vertically
Sentence-by-sentence review misses parallelism errors because each item can be grammatical alone.
Main risk: Read the first words of all bullets down the page. Then read the final grammatical structures. Vertical review reveals inconsistent verbs, nouns, tense and scope quickly.
Translation method: undefined
Review the list horizontally
After vertical review, read each bullet with the lead-in and any parent item.
Main risk: This catches items that look parallel visually but no longer form a coherent sentence or logical proposition.
Translation method: undefined
Use a structure checksum
For high-stakes lists, count source items and target items at every level before release.
Main risk: A simple checksum—same number of top-level items, same nested items, same numbering labels—catches accidental omissions and duplication that normal proofreading may miss.
Translation method: undefined
Machine translation can split list logic
Automated translation systems often process list items as separate segments, losing a shared lead-in or scope operator.
Main risk: Supply context where possible and review the list as a whole. A bullet translated correctly in isolation can be wrong when attached to the source lead-in.
Translation method: undefined
Translation memory can create inconsistent parallelism
Different bullets may retrieve old translations from different projects or style periods.
Main risk: Normalise the set after reuse. Consistency within the current list matters more than preserving unrelated historical wording.
Translation method: undefined
Text expansion can break visible symmetry
A short source-language bullet may expand substantially in the target language, making one item wrap to several lines while others remain compact.
Main risk: Do not shorten meaning merely to preserve visual symmetry. Instead, look for natural concise wording, adjust layout where permitted, and keep logical equivalence ahead of cosmetic length.
Translation method: undefined
Bidirectional scripts require structural testing
Lists mixing right-to-left and left-to-right text can misplace numbers, punctuation, parentheses and nested bullets.
Main risk: Preview the rendered target rather than trusting source code alone. Verify reading order, indentation and number-label association in the actual publishing environment.
Translation method: undefined
Dynamic lists need stable strings
Some websites generate lists from databases, content management systems or product attributes. Identical labels may appear in several contexts.
Main risk: Translate reusable labels consistently, but check whether the generated lead-in changes the grammatical role. A database string that works in one sentence may fail in another if the system lacks grammatical context.
Translation method: undefined
Lists with placeholders and variables
Software and templates may include bullets containing names, counts, dates or variables such as {n}, %s or {{product}}.
Main risk: Preserve placeholders exactly while translating surrounding grammar. Test singular/plural behaviour when variable values change.
Translation method: undefined
Expandable and accordion lists
A list item may double as a button that opens explanatory content.
Main risk: Translate both the visible label and the expanded content as one information unit. The label should accurately predict what opens underneath it.
Translation method: undefined
Lists in mobile interfaces
Small screens magnify text-expansion problems and make nested structures harder to scan.
Main risk: Preserve semantic hierarchy while keeping labels concise. Test wrapping and touch-target clarity without deleting necessary distinctions.
Translation method: undefined
Lists generated from search filters
Facet lists such as size, colour, topic and date categories behave partly as navigation rather than prose.
Main risk: Use consistent taxonomy terminology and avoid sentence-level embellishment. The user’s ability to filter correctly is the primary function.
Translation method: undefined
Revision diffs can hide structural mistakes
When only wording changes are reviewed, a missing bullet or altered nesting level may escape notice.
Main risk: Compare source and target structure separately from text changes. Structural QA should include item counts, levels and labels before linguistic sign-off.
Translation method: undefined
Long list introductions can hide scope
A lead-in may contain several clauses before the final colon, making it easy to attach a qualifier to the wrong items.
Main risk: Break the lead-in into logical operators during analysis: who, must/may, under what condition, and how many items apply. Rebuild that scope clearly in the target.
Translation method: undefined
Parallelism can be semantic as well as grammatical
Three noun phrases can look grammatically parallel while belonging to different conceptual levels—for example, a person, an action and an outcome.
Main risk: Check category consistency as well as word class. Translation should not accidentally make an already coherent source list conceptually uneven.
Translation method: undefined
List order can support reader cognition
Even unordered bullets may follow an intentional progression: general to specific, cause to effect, simple to complex or most important to least important.
Main risk: Avoid casual reordering for style. Preserve cognitive sequencing unless redesign is explicitly permitted.
Translation method: undefined
Cross-document list reuse needs context
A standard list reused across manuals or policies may have different lead-ins and legal scope in each document.
Main risk: Reuse approved wording cautiously and verify that the surrounding operator still matches. The same bullet text can function differently under ‘must’, ‘may’ or ‘for example’.
Translation method: undefined
Final rendered-page review
Structure can change during publishing because themes, editors or conversion tools alter indentation, numbering or spacing.
Main risk: Check the live or previewed target page. Translation QA is incomplete until the user-visible list still shows the intended hierarchy and order.
Translation method: undefined
The Four-Part List Map
- Purpose — sequence, requirements, options, examples, ranking or classification.
- Scope — what the lead-in applies to every item.
- Grammar — noun phrase, imperative, infinitive, gerund, question or full sentence.
- Hierarchy — top-level items, nested items and cross-reference labels.
Practice Lab: Thirty List Translation Decisions
1. Eligibility list
Situation: The lead-in says applicants must meet all requirements.
Main risk: Changing all to any changes eligibility.
Best route: Preserve cumulative logic and check every bullet against the lead-in.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
2. Optional features
Situation: The lead-in says choose one or more.
Main risk: A target equivalent of all makes options mandatory.
Best route: Preserve alternative logic.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
3. Procedure
Situation: Numbered steps describe actions in sequence.
Main risk: Reordering can break the process.
Best route: Keep numbering and chronology intact.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
4. Priority list
Situation: Numbers show ranked preference.
Main risk: Converting to bullets loses ranking.
Best route: Preserve priority order visibly.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
5. Examples
Situation: A list follows ‘such as’.
Main risk: Readers may mistake examples for exhaustive requirements.
Best route: Preserve illustrative status.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
6. Nested exception
Situation: A sub-bullet states an exception to one parent item.
Main risk: Flattening applies the exception to the whole list.
Best route: Preserve hierarchy and scope.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
7. Learning objectives
Situation: Each bullet begins with an academic verb.
Main risk: Mixed target grammar weakens parallelism.
Best route: Keep command forms structurally parallel.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
8. Product specs
Situation: Each item is label plus value.
Main risk: One full-sentence rewrite breaks scanning.
Best route: Preserve compact specification format.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
9. Safety checklist
Situation: Each bullet is a mandatory action.
Main risk: Softening one verb makes it look optional.
Best route: Preserve imperative force.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
10. FAQ list
Situation: Each item is a question.
Main risk: One declarative target item breaks the pattern.
Best route: Maintain interrogative parallelism.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
11. Contract clauses
Situation: Items are labelled (a), (b), (c) and cross-referenced later.
Main risk: Renumbering breaks legal references.
Best route: Keep labels unchanged unless the whole document is intentionally renumbered.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
12. Software settings
Situation: Bullets match interface labels.
Main risk: Synonym variation breaks user navigation.
Best route: Use the exact approved UI terminology.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
13. Parallel negatives
Situation: Every item begins ‘Do not’.
Main risk: Omitting negation from one bullet reverses meaning.
Best route: Verify negative scope item by item.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
14. Gerund list
Situation: Items are planning, testing, reviewing.
Main risk: Mixed infinitive and noun forms look inconsistent.
Best route: Use a parallel target form appropriate to the language.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
15. Sentence bullets
Situation: Every bullet is a complete sentence.
Main risk: Mixed punctuation makes structure unclear.
Best route: Follow one target sentence-list style.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
16. Fragment bullets
Situation: Each item completes the lead-in.
Main risk: Expanding one into a sentence duplicates the lead-in meaning.
Best route: Preserve dependent structure or rewrite the whole set consistently.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
17. Checklist boxes
Situation: Each item should represent one checkable action.
Main risk: Combining items removes independent verification.
Best route: Keep one action per checkbox.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
18. Slide headings
Situation: Four headings use short action verbs.
Main risk: Different target word classes weaken rhetoric.
Best route: Maintain parallel heading form.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
19. Comparison list
Situation: Every item begins more or less.
Main risk: One noncomparative item breaks the scale.
Best route: Preserve comparative structure.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
20. Multilevel policy
Situation: Roman numerals, letters and bullets indicate legal hierarchy.
Main risk: Visual simplification changes scope.
Best route: Preserve every structural level and later cross-reference.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
21. Mobile menu list
Situation: Items must remain short enough to scan on a phone.
Main risk: Over-expansion can bury distinctions.
Best route: Use concise target terminology and verify rendered wrapping.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
22. RTL numbered list
Situation: Arabic or Hebrew target includes Latin product codes.
Main risk: Numbers and punctuation can display in the wrong order.
Best route: Test actual bidirectional rendering.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
23. Variable list item
Situation: A bullet contains {n} selected files.
Main risk: Target grammar may change with number.
Best route: Preserve the placeholder and test multiple values.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
24. Generated filter list
Situation: Categories appear as facets in an ecommerce page.
Main risk: Sentence-style translation makes navigation awkward.
Best route: Use stable taxonomy labels.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
25. Accordion FAQ
Situation: Each list item opens a longer explanation.
Main risk: A vague label can mismatch the expanded content.
Best route: Translate label and panel as one semantic unit.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
26. Revision with deleted bullet
Situation: A source update removes one requirement.
Main risk: Translation memory may preserve the old item.
Best route: Run a fresh structure checksum after updates.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
27. Long lead-in
Situation: A condition in the introductory sentence governs only part of the list.
Main risk: Scope may drift across translation.
Best route: Decompose the operator and rebuild it clearly.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
28. Conceptual parallelism
Situation: Three bullets are stages of one process.
Main risk: One target item becomes a result rather than a stage.
Best route: Check semantic category as well as grammar.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
29. Cross-document standard list
Situation: The same bullets appear under different lead-ins.
Main risk: Blind reuse can change legal force.
Best route: Verify each reused item against its current scope.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
30. Published-page list
Situation: CMS rendering changes nested indentation.
Main risk: Readers may misread hierarchy despite correct source markup.
Best route: Inspect the live target page before release.
After translation, run both vertical and horizontal review. Vertically, compare the grammatical form of all sibling items. Horizontally, read each item with its lead-in and parent level. Then perform a structure checksum to confirm no item, number or nested condition has disappeared or duplicated.
A 10-Minute List Translation Routine
- Identify whether the list is ordered or unordered.
- Mark all scope words in the lead-in.
- Classify the grammar of the items.
- Count top-level and nested items.
- Translate the lead-in first.
- Translate items in parallel form.
- Preserve numbering and cross-references.
- Run vertical parallelism review.
- Run horizontal lead-in review.
- Perform a final structure checksum.
Frequently Asked Questions
Should bullet points always stay as bullet points?
Usually yes when structure carries meaning or supports scanning. Change format only when the task explicitly allows redesign and the logical relationships remain intact.
Can I rewrite fragments as full sentences?
Yes if the entire list is rewritten consistently and the lead-in relationship is preserved. Mixing fragments and sentences can make one item look structurally different without a semantic reason.
Should numbered lists ever become bullets?
Only when numbering is purely decorative and redesign is allowed. Never remove numbering when it marks sequence, priority, procedure or later cross-references.
How do I preserve parallelism across languages?
Match grammatical function rather than identical morphology. Target items should share a comparable structural pattern appropriate to the target language.
What is the biggest list-translation error?
Losing list logic—especially all-versus-any scope, nested exceptions, sequence or cross-reference—even when the individual items are translated accurately.
How should machine-translated lists be reviewed?
Always review the list as one unit. Systems often translate bullets independently and can lose the shared lead-in or produce inconsistent grammar across items.
Final List Translation Checklist
- The target has the correct number of items.
- Ordered and unordered structure is preserved.
- Nested hierarchy is unchanged.
- All-versus-any logic is correct.
- Exceptions remain attached to the right item.
- Sibling items are grammatically parallel.
- Lead-in scope works with every bullet.
- Numbering and cross-references still match.
- Punctuation follows target conventions consistently.
- Semantic list markup and accessibility are preserved.
- The rendered target page still displays the intended hierarchy.
The Larger Principle
Lists are a form of information architecture. Their meaning is distributed across words, order, indentation, numbering, punctuation and the grammatical relationship between the lead-in and each item.
That is why a list can be mistranslated even when every bullet looks individually correct. Translation has to preserve the logic that holds the list together.
The practical rule is: translate the list as a system, not as isolated lines. When scope, parallelism, hierarchy and sequence survive, the target list remains useful rather than merely readable.