Translating a pleading breaks line numbering whenever the tool rebuilds the document instead of translating inside it, because the printed numbers in the left margin only stay aligned if the original page setup survives. On California-style 28-line pleading paper the margin numbers must track the text exactly, line for line — and text expansion of 15–30% into most European languages reflows the body, so a filing that was compliant on page one can be misaligned by page four. Bluente translates professional documents across 120+ languages and returns them in their original layout, which is the part most general-purpose translation tools give up on.
As of August 2026 there is abundant guidance on how to format pleading paper and essentially none on what translation does to it. Here is the mechanism.
What Is Pleading Paper Line Numbering, Technically?
It is a numbered column printed in the left margin, restarting at 1 on every page, that lets a court, a deponent, or opposing counsel cite a specific line rather than a general passage. California's standard is 28 lines per page; other jurisdictions use their own counts and their own local rules.
The critical detail is how those numbers are produced. In a well-built template they are not typed — they are generated by the word processor's line-numbering feature and bound to the page layout, or drawn into the header so they repeat on every page. Either way, they exist because the page setup says they should: specific margins, a specific line height, a specific paper size, and a specific number of lines per page.
That makes line numbering a derived property. It is not stored in the text. It is computed from the layout. Which is precisely why it is fragile.
Why Does Translation Desynchronise the Numbers?
Two independent things happen at once.
The text reflows. Translating English into Spanish, French, Italian, or Portuguese typically adds 15–30% length; German can add more. The same paragraph now occupies more lines. If the numbering is generated by the layout, it recomputes correctly and everything still tracks — the document is simply longer. That is the good case.
The layout changes. This is the bad case, and it is what text-first translation tools cause. They extract the visible text, translate it, and pour the result into a new document with default margins, default line spacing, and default page setup. The numbering feature is either lost entirely or re-applied against a different geometry. Now the margin numbers exist but no longer correspond to the lines beside them — or a template that drew the numbers into the header keeps drawing 28 evenly spaced numbers while the body text sits at a different line height underneath.
The second failure is worse than losing the numbers outright, because it looks correct at a glance and is wrong everywhere.
What Else in a Court Filing Depends on the Page Map?
Line numbering is the visible symptom. Several other things break from the same cause.
Footers. Many local rules require a footer on every filed paper, divided by a printed line, carrying the document title and often the case number. Rebuild the file and the footer is generic or gone.
Exhibit pagination. Exhibits and attachments must be clearly numbered, and electronic filing rules increasingly require that the PDF page numbers match the document's own numbering so the court's viewer and the filing agree. Repagination without control breaks that correspondence.
Bates ranges. Any citation to a Bates number assumes a fixed page map. Change the map and every cross-reference to it needs verification.
Internal cross-references. "See ¶ 32, lines 4–9" is a line-number citation. It is wrong the moment the lines move and nobody regenerated it.
Tables of contents and authorities. Page-number-dependent, and stale by default after any repagination.
Caption block alignment. The caption's fixed geometry — party names, court, case number — sits in a table or a set of tab stops that a rebuild will not reproduce faithfully.
Does This Matter If the Translation Is Only for Internal Review?
Often not. A large share of translated litigation material never gets filed: foreign-language evidence translated for attorney review, a counterparty's pleading translated so the team can read it, discovery material triaged before certified translation is commissioned. For those, alignment is cosmetic.
It matters in three situations.
When the translation is the filing. A pleading prepared in one language and filed before a foreign court in another has to meet the receiving court's formatting rules, including line numbering where required.
When the translation is an exhibit. A translated document attached to a filing inherits the exhibit and pagination rules of the filing it sits inside.
When someone will cite the translated version by line. Depositions, meet-and-confer correspondence, and briefing that quotes a translated pleading all assume the line numbers mean something.
How Do You Keep a Translated Pleading Compliant?
Five checks, none of which take long.
Use a document-first translator. Translation happens inside the original file, so page setup, margins, line-numbering settings, headers, footers, and the caption block are never regenerated. This removes the layout-change failure entirely and leaves only honest reflow.
Verify the line-number source. Open the translated file and confirm the numbers are still generated by the layout rather than baked into a header image or a static text column. Generated numbers recompute; static ones lie.
Recount a page. Pick a page in the middle of the translated document, count the body lines, and confirm the last number in the margin matches. If page 6 shows 28 margin numbers against 31 lines of text, the binding is broken.
Regenerate everything page-dependent, last. Tables of contents and authorities, internal line and page citations, exhibit indices. After the translated text is final.
Budget for expansion before drafting. If a pleading will be filed in German or Spanish, draft the source shorter. This is the only control that prevents a length problem rather than detecting one.
How Bluente Handles Court-Formatted Documents
Bluente translates inside the original file structure rather than rebuilding the document, so margins, paper size, line spacing, line-numbering settings, section breaks, headers, footers, and caption tables come through as they were. Text expands — that is a property of language — but it expands within the original page geometry, so generated line numbers recompute against the correct layout instead of drifting away from it.
Custom glossaries lock party names, defined terms, statutory citations, and case names so they resolve identically throughout a filing, which matters as much as layout when the same term appears eighty times. The platform supports 27 file types across 120+ languages, including DOCX, PDF, and scanned exhibits via OCR, with 100% formatting retention as the design target and most documents completing in under two minutes. Tracked changes, comments, insertions, and deletions are preserved, which is what makes translated redlines usable.
On confidentiality: documents are never used to train AI models, are auto-deleted within 24 hours, and the platform is SOC 2 Type II, GDPR, and ISO 27001 compliant. Where a court requires attested output, human-certified translation is available on the same platform — AI for the review and drafting cycle, certification for the submission. Litigation teams with concentrated volume can scope project blocks with the sales team rather than committing annually.
Frequently Asked Questions
Q: Does translating a pleading remove the line numbers? It can. Tools that extract text and rebuild the document lose the line-numbering settings along with the rest of the page setup. Tools that translate inside the original DOCX keep them, and the numbers recompute correctly against the reflowed text.
Q: My translated pleading has 28 margin numbers but the text does not line up. Why? The numbers are almost certainly static — drawn into the header or a fixed text column — while the body was reflowed at a different line height. Static numbering cannot recompute, so it silently stops matching.
Q: Will the page count change after translation? Almost always. Expect 15–30% expansion into Spanish, French, Italian, or Portuguese and more into German; Chinese, Japanese, and Korean usually contract. Check any applicable page limit before filing.
Q: Do exhibit numbers and Bates ranges survive translation? The stamped values do if the file is translated in place rather than regenerated. Any citation that refers to a page or line position needs re-verification after repagination.
Q: Is an AI translation acceptable for a court filing? For internal review, discovery triage, and drafting, yes. Official submissions in most jurisdictions require a certified translation with a translator's certificate of accuracy — use AI for the working cycle and certified output for what is filed.
Q: Can I translate a scanned exhibit and keep it usable? Yes, via OCR. The output should keep the page layout so exhibit pagination and any stamped numbering still correspond to the original document.
Related Reading
Does Translating a Document Break the Table of Contents and Numbering?
Does Translating a Document Break Headers, Footers, and Page Numbers?
Does Translating a Document Break Its Metadata and Document Properties?
Sources and Further Reading
Primary standards, regulations and specifications referenced above:
Need advice translating scanned PDFs — practitioners describing this problem in r/TranslationStudies
Last reviewed 23 August 2026. Written by the Bluente document engineering team, who build and test the format-preservation pipeline described above. We update these guides when the underlying standards, regulations or file formats change.
Start translating documents for free. Bluente preserves your formatting across 120+ languages in under 2 minutes. Try BluTranslate free — no credit card required.