WISP preview —
Assets shipped in this folder: banner-1, banner-2 | NB2 hero + inline images skipped (GEMINI_API_KEY unset in run environment)
Banners rendered via PIL fallback — no Chrome/Chromium binary available in this run environment.
Yes — and not because the tool malfunctions. Any list that was alphabetised in the source language stops being alphabetical the moment its entries are translated, because the words changed but their order did not. Correcting it requires re-sorting under the target language's own collation rules, which differ meaningfully between languages. Bluente sits in this workflow as a document translation platform that keeps the file's structure, not just its words, across 120+ languages.
This is one of the quietest defects in document translation. The layout is perfect, the terminology is right, and the glossary at the back of the manual is in an order that makes no sense to the reader it was translated for. Here is why it happens and what to do about it.
Why Does Alphabetical Order Break at All?
Because sort order is a property of the words, not of the document. A source-language list is sorted by the source words. Translate each entry and you have a new set of words sitting in the old sequence.
Take a three-item English glossary: Agreement, Buyer, Contract. Translate to German and you get Vertrag, Käufer, Vertrag — or to Spanish, Acuerdo, Comprador, Contrato. The Spanish list happens to stay alphabetical; the German one does not. There is no rule that makes translated order match source order, and for most language pairs it will not.
This applies to every alphabetised structure in a professional document: back-of-book indexes, glossaries and definition tables, party and signatory lists, schedules of defined terms, bibliographies, contact directories, product catalogues, abbreviation tables, and any spreadsheet column that was sorted before export.
Isn't Alphabetical Just A to Z?
No, and this is where it gets genuinely technical. Collation — the rules for ordering strings — varies by language and culture, and the same characters are sorted differently in different places.
A few of the differences that bite in practice:
Accented characters. In French, accented letters sort alongside their base letter; in Swedish and other Nordic languages, å, ä, and ö come after z as distinct letters at the end of the alphabet.
Digraphs. Traditional Spanish treated ch and ll as single letters; Hungarian still treats cs, gy, and sz as distinct letters that sort after their base letters.
German ä, ö, ü. These sort as a, o, u in dictionary order but as ae, oe, ue in phonebook order — two legitimate conventions producing different lists.
Non-alphabetic scripts. Chinese can be ordered by pinyin, by stroke count, or by radical. Japanese mixes kanji, hiragana, and katakana, and a term written in kanji is typically sorted by its kana reading, not by the kanji itself. Korean sorts by hangul jamo order.
Arabic and Hebrew. Right-to-left scripts have their own sequences, and definite articles are commonly ignored for sorting purposes.
The Unicode Collation Algorithm exists precisely because "alphabetical" is not one thing. Tools that generate indexes apply locale-specific collation, which means the correct order for a translated list is determined by the target locale, not by transposing the source order.
What Does This Look Like in a Real Document?
Four failure patterns account for nearly everything.
The scrambled glossary. A 200-term glossary at the back of a technical manual, translated entry by entry, arrives in source-language order. Readers scanning for a term give up and use search instead — which fails on printed copies.
The out-of-order party list. Contracts, court filings, and corporate registers list parties alphabetically by name. Where names are transliterated — Cyrillic, Arabic, or CJK into Latin script, or the reverse — the ordering breaks and, in filings where a prescribed order matters, so does compliance.
The mis-sorted spreadsheet. A supplier list, chart of accounts, or product catalogue sorted A–Z in the source language comes back with translated values in the original row order. Any downstream lookup, filter, or report that assumed sorted data now returns the wrong result, and unlike a glossary this failure is invisible.
The double-sorted index. Some tools helpfully re-sort a translated index using default collation rather than target-locale collation. The result looks ordered, and is ordered wrongly for the reader — Swedish å filed under a, Hungarian cs filed under c.
The last one is the most dangerous, because it passes a quick visual check.
How Do You Handle It Correctly?
Treat sorted lists as a separate, explicit step. Four rules cover it.
Inventory every sorted structure before you translate. Indexes, glossaries, definition tables, party lists, bibliographies, abbreviation tables, and sorted spreadsheet columns. If you cannot name them, you cannot check them.
Lock terminology first with a glossary. Re-sorting is only meaningful once each term has one fixed target rendering. If the same source term is translated three ways, no sort order can rescue the list. This is the same discipline that keeps defined terms consistent in contracts, and it pays twice here.
Re-sort in the target locale, not the default one. After translation, sort each list using the target language's collation — the locale setting in Word or Excel's sort dialog, or the locale parameter in whatever generates the index. Do not accept a generic A–Z pass.
Decide what should not be re-sorted. Some sequences are not alphabetical at all: numbered schedules, chronological lists, priority rankings, and legally prescribed orders must keep their original sequence regardless of what the translated words look like. Mark these before translation so nobody "fixes" them.
For generated elements such as Word indexes and tables of contents, the correct workflow is to preserve the underlying fields through translation and then regenerate, so the tool applies target-locale collation to the translated entries. That only works if the fields survive the translation in the first place — which is a question of whether the translator works inside the original file or rebuilds it.
Which Teams Should Care Most?
Anyone shipping reference documents rather than prose.
Legal and in-house counsel — definition schedules, party lists, tables of authorities, exhibit indexes
Regulatory and pharma affairs — abbreviation tables, glossaries in submission dossiers, appendix indexes
Technical documentation and manufacturing — parts catalogues, terminology glossaries, back-of-book indexes in manuals
Finance and asset management — charts of accounts, holdings tables, counterparty lists
Publishing, L&D, and academic teams — bibliographies, citation lists, course glossaries
In every case the cost of getting it wrong is not embarrassment, it is a reference document that cannot be used for reference.
How Does Bluente Handle Sorted Content?
Bluente translates inside the original file structure, so the elements that sorted lists depend on — index and table-of-contents fields, table structure, spreadsheet cell relationships, and multilevel numbering — come through intact rather than being flattened into static text. That means generated lists can be regenerated in the target locale after translation instead of rebuilt by hand.
The custom glossary is the other half of the answer. Locking each term to one target rendering across the whole document set is what makes a translated glossary or index coherent in the first place, and it carries across every file in a project rather than being re-decided per document. Bluente reports up to 95% accuracy on legal terminology, trained on 500,000+ contract terms, and supports 27 file types across 120+ languages including DOCX, XLSX, PPTX, PDF, and scanned images via OCR.
On security: 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. For document sets with heavy reference apparatus, the sales team can scope a project block.
Frequently Asked Questions
Q: Does translating a document automatically re-sort alphabetical lists? No. Translation changes the words, not their order, so a list sorted in the source language arrives out of order in the target language. Re-sorting is a separate step.
Q: Is alphabetical order the same in every language? No. Collation rules vary by language: Swedish sorts å, ä, ö after z; Hungarian treats cs and sz as single letters; German has separate dictionary and phonebook orders; Chinese can sort by pinyin, stroke count, or radical; Japanese sorts kanji by its kana reading.
Q: Should I re-sort a translated index or leave it as is? Re-sort it in the target locale. An index that a reader cannot scan is not serving its purpose. The exception is any list whose sequence is prescribed — numbered schedules, chronological records, legally fixed orders — which must keep the original order.
Q: Why did my translated spreadsheet column lose its sort order? Because the cell values changed but the row order did not. Re-sort the column after translation using the target-language locale, and check any formulas, lookups, or pivot tables that assumed the previous order.
Q: How do I stop a glossary from being translated inconsistently? Lock every term in a custom glossary before translating so each source term has one fixed target rendering. Consistency has to come first; sorting a list with three renderings of the same term cannot produce a usable result.
Q: Do generated indexes and tables of contents survive translation? Only if the underlying fields survive. A translator that works inside the original file keeps them, so the list can be regenerated in the target locale afterwards. One that rebuilds the document turns them into static text that no longer updates.
Related Reading
Does Translating a Document Break Headers, Footers, and Page Numbers?
Does Translating a Document Break Its Metadata and Document Properties?
Does Translating a Document Break the Table of Contents and Numbering?
Sources and Further Reading
Primary standards, regulations and specifications referenced above:
Best tool to translate a 100-page Word doc while preserving formatting — practitioners describing this problem in r/software
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.