If you are searching for how to translate ECLI numbers, how to translate ELI links, how to translate CELEX numbers, or how to preserve European legal-document identifiers in multilingual judgments, legislation, contracts, research and compliance work, the first rule is simple: translate the legal language around the identifier, not the identifier itself. ECLI, ELI and CELEX are reference systems designed to keep a legal decision or legislative text findable even when readers use different languages.
This matters in court judgments, legal memoranda, EU legislation, national legislation, regulatory compliance, academic citations, cross-border litigation, procurement, policy papers, legal databases and multilingual websites. A target text can be perfectly written and still become legally misleading if an ECLI is mistyped, an ELI URI is rewritten like prose, a CELEX number is confused with a case number, or a translated title is allowed to replace the machine-stable reference to the actual legal document.
This guide explains how to translate around the European Case Law Identifier, European Legislation Identifier and CELEX system without changing legal identity. It shows what each identifier does, how their structures differ, how to handle citations, court names, titles, dates, article references, consolidated texts, corrigenda and language versions, and how to build a quality-assurance workflow in which legal meaning moves across languages while the underlying source remains traceable.
1. ECLI identifies judicial decisions, not legislation
The European Case Law Identifier is designed for case law. EUR-Lex describes it as a uniform identifier that makes judicial decisions easier to identify, cite, search and link. It does not replace the judgment’s title, case number, court name or procedural history; it gives the decision a stable reference across systems and languages.
Translation control: Translate the court name and case description when appropriate, but preserve the complete ECLI string exactly. Quality assurance: Search the target ECLI in an authoritative legal database and confirm it resolves to the same decision as the source.
2. An ECLI has five ordered components
EUR-Lex explains that ECLI contains five parts separated by colons: the literal ECLI prefix, a country or organization code, a court code, the four-digit year of the decision and a unique identifying component. The order itself is part of the identifier logic.
Translation control: Do not reorder the parts to match target-language syntax or replace the literal prefix with a translated phrase. Quality assurance: Run a structural check that counts the expected colon-separated components and preserves their order.
3. The ECLI prefix remains ECLI in every language
ECLI is the standardized identifier label, not an English-language word that should be translated. A legal translation can spell out European Case Law Identifier in the target language for explanation, but the code itself begins with ECLI.
Translation control: Keep the identifier and explanatory expansion in separate fields or clauses. Quality assurance: Check that no spellchecker, translation engine or style tool has expanded or altered the ECLI prefix inside the code.
4. The country or organization code is controlled metadata
The second ECLI component identifies the relevant jurisdiction or organization according to the ECLI rules. It should not be replaced with the target-language country name, a flag emoji or an informal abbreviation.
Translation control: Translate the country name in surrounding prose while retaining the code inside the identifier. Quality assurance: Compare the code with the authoritative ECLI record, especially in cross-border litigation where multiple jurisdictions appear together.
5. The court code is not the translated court acronym
The ECLI court component is assigned under the participating system’s rules. A translated court name can produce different initials, but those initials are not a substitute for the registered court code.
Translation control: Preserve the court code and localize the court’s human-readable name separately. Quality assurance: Check that a translated court name still points to the same institutional court represented in the ECLI.
6. The ECLI year is the year encoded by the identifier
For ECLI, the four-digit year is part of the identifier. Translators should not rewrite it because a decision was published, reported or translated in another year. The identifier year follows the ECLI assignment rules.
Translation control: Keep the year inside the ECLI unchanged and translate narrative date expressions independently. Quality assurance: Compare the decision date, publication date and ECLI year rather than assuming they are interchangeable.
7. The final ECLI component is jurisdiction-specific identity data
The final ECLI component can be up to the permitted length under the system and may contain structures defined by the issuing jurisdiction. It is not a sentence, case title or number that can be reformatted freely.
Translation control: Treat the entire last component as protected data, including permitted dots or other authorized characters. Quality assurance: Use exact-string comparison between source and target ECLI values.
8. An ECLI is not a CELEX number
EUR-Lex explicitly notes that the final part of the Court of Justice ECLI is not the CELEX number. A single decision can therefore be discoverable through more than one identifier system, each serving a different legal-information architecture.
Translation control: Keep ECLI and CELEX in separately labeled fields or citation positions. Quality assurance: Retrieve both identifiers and confirm they point to the same underlying case-law document when the source provides both.
9. An ECLI is not the procedural case number
A Court of Justice case number serves a procedural and citation role that differs from ECLI. National courts likewise have their own case-number conventions.
Translation control: Translate surrounding procedural wording but preserve official case numbers according to the issuing court’s format. Quality assurance: Check case number, ECLI and document title as three linked but distinct pieces of metadata.
10. An ECLI is not every jurisdiction’s neutral citation
Some legal systems use neutral citations or report citations that may look similar in function to ECLI. They are not automatically interchangeable. ECLI is one identifier framework within a broader legal citation environment.
Translation control: Preserve each citation namespace exactly rather than converting one into another by analogy. Quality assurance: Maintain separate citation fields when the source includes ECLI, report citation and domestic neutral citation.
11. ELI identifies legislation through web-oriented identifiers
The European Legislation Identifier provides a standardized framework for identifying and describing legislation. EUR-Lex explains that ELI uses HTTP URIs that can be read by humans and machines and combines identification with structured metadata.
Translation control: Translate titles and metadata labels while preserving the ELI URI structure. Quality assurance: Open the target URI and confirm it resolves to the intended legislative resource.
12. ELI is more than a translated URL label
An ELI is not merely a web address pasted into a legal article. It participates in an interoperability framework for legislation, including metadata and machine-readable description. Changing path components casually can point to a different act, subdivision or expression.
Translation control: Keep the ELI as a protected URI and localize only human-facing anchor text where the design permits. Quality assurance: Test the link after publication rather than assuming visual similarity means technical correctness.
13. ELI can identify an act at different levels
ELI implementations can identify whole acts and, in some systems, subdivisions such as articles. EUR-Lex gives examples where the URI includes a path for a specific article. A translated legal commentary therefore must distinguish the act-level identifier from an article-level resource.
Translation control: Preserve every path component and translate the article label outside the URI. Quality assurance: Resolve both act-level and subdivision-level links during QA.
14. ELI URI components are not free-form target-language words
A simple EU ELI can include controlled path components representing document type, year, number and publication status. Those path segments follow the publisher’s ELI template, not the translator’s preferred wording.
Translation control: Do not translate URI path words unless the official ELI publisher defines a different target URI. Quality assurance: Compare the final link with the official ELI displayed on the legal document page.
15. ELI metadata and visible prose should agree
A page can contain the correct ELI but a mistranslated title, date or article description. The identifier makes the source recoverable, but it does not excuse linguistic or legal errors in the human-facing text.
Translation control: Use ELI as an identity anchor while translating descriptive metadata carefully. Quality assurance: Compare title, date, document type and referenced subdivision against the resolved ELI resource.
16. ELI implementations can have different URI templates
The ELI framework supports implementation by different publishers. National systems can define their own URI templates within the framework. A translator should not assume that an EU-level ELI pattern can be copied mechanically onto every national legal citation.
Translation control: Preserve the publisher’s supplied ELI rather than generating one from memory. Quality assurance: Verify national ELI implementations through the issuing legal-information service.
17. CELEX is the EUR-Lex document identifier
EUR-Lex assigns CELEX numbers to most documents in its database regardless of document language. That language independence is exactly why translators should preserve the number: different language versions of the same EU document can share the same CELEX identity.
Translation control: Translate the document title and legal description, but keep the CELEX number unchanged. Quality assurance: Search the CELEX number directly on EUR-Lex and verify the correct document.
18. The common CELEX structure has sector, year, type and number
EUR-Lex explains that the most common CELEX form contains a sector, a year, a document-type descriptor and a document number. The familiar example 32000L0060 encodes a legal-act sector, year 2000, the directive descriptor and the document number.
Translation control: Do not add target-language initials or punctuation inside the canonical CELEX value. Quality assurance: Parse sample CELEX values by sector and descriptor during QA to catch improbable mutations.
19. The first CELEX character identifies a sector
EUR-Lex organizes documents into sectors such as treaties, international agreements, legal acts, preparatory documents, case law, consolidated texts and other categories. The first CELEX character therefore has structural meaning.
Translation control: Do not translate or renumber the sector based on a target-language category name. Quality assurance: Check that the sector matches the type of legal document described in the target.
20. The CELEX year is not every date mentioned in the document
CELEX uses a year component under allocation rules that depend on the document type. A legal act can contain signature, publication, entry-into-force and application dates that differ from the CELEX year.
Translation control: Preserve the CELEX year inside the identifier and translate every narrative date according to its own legal role. Quality assurance: Create a date-role checklist for adoption, publication, entry into force and application where the document depends on them.
21. CELEX document-type descriptors are controlled codes
Letters such as L for directives and R for regulations occur in particular CELEX sectors. The descriptor is not a target-language abbreviation. Translating Directive into another word does not change the CELEX L.
Translation control: Keep the descriptor untouched and translate the document-type name separately. Quality assurance: Check that the translated prose accurately names the type encoded by the CELEX value.
22. The final CELEX number can vary in length and meaning
EUR-Lex notes that the final component can contain different numbers or patterns depending on sector and document type. Translators should not normalize all endings to one fixed width based on a single example.
Translation control: Protect the full source CELEX string as one identifier. Quality assurance: Validate unusual CELEX structures against EUR-Lex rather than repairing them from a template.
23. Corrigenda can share the base CELEX with a suffix
EUR-Lex documentation shows that corrigenda can use the original CELEX number with an additional suffix. That suffix distinguishes a correction document from the original act.
Translation control: Preserve the suffix and translate corrigendum or correction wording in prose. Quality assurance: Open both the original and corrigendum links to confirm which document the target is citing.
24. Consolidated texts use their own CELEX sector logic
Consolidated texts bring amendments together for reading convenience and use CELEX conventions distinct from the basic act. A consolidated text is not automatically the legally authentic equivalent of the original Official Journal act.
Translation control: Translate consolidated text clearly and preserve the CELEX identifier assigned to that resource. Quality assurance: Check whether the target is citing the basic act, a consolidated version or both.
25. A CELEX number can stay stable across language versions
Because CELEX is language-independent, translators do not create a French CELEX, German CELEX or English CELEX. Language is handled by EUR-Lex content versions rather than by translating the identifier.
Translation control: Use the same CELEX identity while linking to the appropriate language version when needed. Quality assurance: Test language switching on EUR-Lex to confirm document identity remains constant.
26. The legal title can differ by language while identity remains stable
Official titles are translated across EU languages and can differ substantially in word order and terminology. The stable identifier lets readers connect those language-specific titles to the same act or case.
Translation control: Use the official target-language title where available rather than inventing a back-translation. Quality assurance: Compare the target title with the language version linked to the preserved CELEX or ELI.
27. Official terminology should outrank literal translation
EU legal vocabulary is highly standardized. Terms such as regulation, directive, decision, implementing act, delegated act, opinion and recommendation have established equivalents in official language versions.
Translation control: Use official target-language terminology from the legal source rather than a dictionary-only translation. Quality assurance: Build a terminology list from the actual multilingual legal corpus referenced by the identifier.
28. Article, paragraph, point and annex references need structural fidelity
Legal references such as Article 3(2)(a), Annex II or recital 17 are not decorative. A target that changes hierarchy can direct readers to the wrong provision even when the act identifier is correct.
Translation control: Preserve the provision hierarchy and localize labels according to legal drafting convention. Quality assurance: Resolve a sample of cited provisions through ELI or EUR-Lex and verify the target reference reaches the same text.
29. Recitals are not articles
EU legislation often separates recitals, which explain context and reasoning, from operative articles. Translating both simply as sections can erase legal structure.
Translation control: Use target-language legal terms that distinguish recital from operative provision. Quality assurance: Check cross-references against the official target-language version of the act.
30. Annex identifiers need exact attachment
A regulation can contain multiple annexes, tables and schedules. A translation that preserves the correct CELEX number but attaches a requirement to the wrong annex still misstates the law.
Translation control: Treat act identity and internal subdivision identity as two levels of control. Quality assurance: Compare annex numbering and headings across source and target.
31. Case names can be translated or presented differently from ECLI
Legal databases, textbooks and judgments can shorten or localize case names. The ECLI remains the stable identifier even when editorial naming conventions differ.
Translation control: Translate or reproduce the case name according to the project’s legal citation policy while preserving ECLI. Quality assurance: Search by ECLI when name variants make ordinary text search ambiguous.
32. Party names require a separate names policy
Court cases can contain personal names, company names, anonymized initials or pseudonyms. Those are not components of the ECLI and should be handled according to court practice, privacy rules and the translation brief.
Translation control: Do not correct or expand anonymized party names using external knowledge. Quality assurance: Compare the target caption with the official public version linked by ECLI.
33. Court names can have official target-language forms
EU institutions and some national courts publish official multilingual names. Using an official form improves consistency, but the court code inside ECLI remains unchanged regardless of the display language.
Translation control: Separate the institutional name authority from the identifier field. Quality assurance: Check official institutional terminology before inventing translated court names.
34. Legal citations can contain several identifiers at once
A scholarly footnote might include a case number, ECLI, CELEX, report citation, date and paragraph reference. Each piece answers a different question. Flattening them into one simplified target citation can remove useful traceability.
Translation control: Retain all source identifiers unless the citation style explicitly permits omission. Quality assurance: Map each citation element before translation and compare the target element by element.
35. A hyperlink label can be translated while the href remains stable
Web publishing separates visible anchor text from the link destination. This is ideal for legal translation: readers can see a natural target-language title while the underlying ELI or EUR-Lex URL remains technically correct.
Translation control: Translate anchor text only; keep the verified href unchanged. Quality assurance: Click every legal reference in the final rendered page rather than reviewing source HTML alone.
36. PDF links and copied identifiers need separate testing
A legal identifier may look correct in a PDF but copy with hidden line breaks or reordered punctuation. This is especially risky for long ELI URLs and colon-separated ECLIs.
Translation control: Prevent line breaks inside machine identifiers where practical. Quality assurance: Copy-paste the final identifier from PDF into a browser or legal search interface and confirm resolution.
37. Right-to-left legal layouts need directional isolation
Arabic or Hebrew translations can contain left-to-right ECLI, CELEX and URI strings. Poor bidirectional handling can scramble colons, slashes or numbers visually.
Translation control: Use appropriate direction isolation rather than reversing the identifier. Quality assurance: Test display, selection and clipboard output in the final format.
38. Localized digits should not rewrite legal identifiers
A target language may normally display different numeral glyphs, but machine-facing legal identifiers should remain in the representation required by the legal database. Localized prose dates can follow project rules separately.
Translation control: Protect all ECLI, CELEX and ELI values from digit shaping. Quality assurance: Compare the final code character by character with the official source.
39. OCR is risky for colon- and slash-heavy identifiers
Scanned judgments and journal articles can introduce OCR errors such as O/0, I/1, missing colons or broken slashes. A malformed ECLI may still look plausible to a human reader.
Translation control: Verify identifiers through authoritative databases before reusing OCR text. Quality assurance: Treat failed resolution as a data-quality exception, not as permission for guesswork.
40. Translation memory can propagate the wrong legal source
Legal writing repeats phrases such as pursuant to Regulation or in Case. A high translation-memory match can carry an old CELEX or ECLI into a new document if identifiers are not variable-protected.
Translation control: Mark legal identifiers as non-translatable variables. Quality assurance: Search the final target for ECLI and CELEX values absent from the current source.
41. Machine translation should receive masked identifiers
Language models generally do not need to process ECLI, ELI or CELEX strings. Masking them reduces the risk of punctuation changes, line-break insertion or accidental expansion.
Translation control: Restore identifiers from source-controlled data after translation. Quality assurance: Run exact source-target set comparison for all legal identifiers.
42. Generative AI must not invent missing legal identifiers
A model can infer a likely case, directive or regulation from surrounding text, but a plausible ECLI or CELEX is not evidence. Wrong identifiers are especially dangerous because they can direct readers to an unrelated legal authority.
Translation control: Leave missing identifiers missing or retrieve them from authoritative legal databases. Quality assurance: Require deterministic database resolution before adding any identifier absent from the source.
43. Do not infer CELEX from an act title alone without verification
Many EU acts have similar titles and may amend, recast or implement one another. A guessed CELEX based on a title can point to a related but different act.
Translation control: Search EUR-Lex and verify number, date and title before inserting a CELEX. Quality assurance: Cross-check the Official Journal reference where available.
44. Do not infer ECLI from a domestic case number alone
National ECLI assignment rules vary, and not every decision has an ECLI. A case number can help search but does not guarantee a mechanically derivable ECLI.
Translation control: Use the relevant ECLI search service or court database. Quality assurance: Record unresolved cases instead of fabricating a standardized identifier.
45. Legal quotations need source-level control
When a translation quotes legislation or a judgment, the identifier anchors the reader to the source, but the quoted target wording should come from an official translation where one exists or be clearly presented as the translator’s rendering where it does not.
Translation control: Distinguish official language versions from unofficial translations. Quality assurance: Check the quoted provision against the act or judgment resolved by the identifier.
46. Parallel EU language versions are a translation asset
EUR-Lex provides official multilingual versions for many EU documents. These can supply terminology, syntax and institutional names more reliably than generic translation resources.
Translation control: Use the preserved CELEX or ELI to retrieve the official target-language document. Quality assurance: Compare high-risk terms and entire cited provisions with the official version.
47. Official translations do not eliminate context checking
Even when an official target version exists, the translator must ensure the current source cites the same version, amendment state and subdivision. A consolidated text and original act can contain wording from different legal moments.
Translation control: Check document date and consolidation status before copying official target wording. Quality assurance: Record which version supplied the terminology.
48. Consolidation dates matter in compliance translation
A compliance manual may cite the law as consolidated at a particular date. Translating from a newer or older consolidated text can change obligations.
Translation control: Preserve the cited identifier and temporal context. Quality assurance: Confirm the consolidation date on EUR-Lex or the national legislation site.
49. Amendments should not be collapsed into the base act
An amending regulation has its own identity even when readers think of it mainly as a change to another act. Translators should preserve both the amending-act reference and the base-act reference when the source distinguishes them.
Translation control: Keep separate identifiers for each legislative document. Quality assurance: Trace the amendment relationship in the legal database.
50. Repeals and replacements need temporal clarity
A repealed act may still govern historical events. Replacing its CELEX with a successor act in a translation can create anachronistic law.
Translation control: Translate the historical source faithfully and add current-law context only when requested. Quality assurance: Check effective dates and repeal status independently from the identifier string.
51. Legal databases may display multiple identifiers together
A record can include ECLI, CELEX, Official Journal references, case numbers and ELI URIs. Those are complementary access paths, not duplicates to be simplified arbitrarily.
Translation control: Retain the source metadata according to the document’s citation purpose. Quality assurance: Test at least one lookup route for each identifier type in the final target.
52. Search intent: translate ECLI
A user searching this phrase may want to know what an ECLI means, how to cite it in another language, how to translate the court name or how to preserve it in a translated judgment. The answer begins by treating ECLI as non-translatable identity data.
Translation control: Explain the five components and translate only surrounding legal metadata. Quality assurance: Verify the identifier through EUR-Lex, e-Justice or the issuing jurisdiction.
53. Search intent: translate ELI
A user may encounter an ELI URI in legislation and wonder whether the path should be translated. The safe principle is to preserve the publisher-defined URI while translating the visible title and explanatory metadata.
Translation control: Treat the URI as code and the anchor text as language. Quality assurance: Resolve the final URI after publication.
54. Search intent: translate CELEX
A translator may need to understand a CELEX number, identify the act, retrieve an official target-language version or cite the same EU document in another language. The CELEX stays constant while the document language changes.
Translation control: Search the number directly on EUR-Lex and use the official target-language text where appropriate. Quality assurance: Check sector, year, descriptor and document identity before release.
55. Reference route: EUR-Lex ECLI guidance
EUR-Lex publishes detailed help on ECLI structure and examples, including the five mandatory components and the distinction between ECLI and CELEX.
Translation control: Use EUR-Lex ECLI guidance when validating judicial identifiers. Quality assurance: Record the database used when resolving disputed case references.
56. Reference route: EUR-Lex ELI guidance
EUR-Lex explains that ELI uses HTTP URIs and metadata to make legislation accessible, exchangeable and reusable across borders. It also documents EU-level examples for acts and subdivisions.
Translation control: Use EUR-Lex ELI guidance for URI and metadata interpretation. Quality assurance: Click final target links instead of relying on text comparison alone.
57. Reference route: EUR-Lex CELEX guidance
EUR-Lex documents CELEX sectors, years, document-type descriptors and document-number patterns. Because exceptions exist, the official help page is safer than a homemade parser based on one example.
Translation control: Use EUR-Lex CELEX guidance for validation. Quality assurance: Treat unfamiliar CELEX forms as lookup tasks rather than formatting errors.
58. Source versioning belongs in the citation record
A legal identifier can remain stable while the reader moves among language versions, consolidated states or publication formats. Good translation therefore records not only the identifier but also the version context used for terminology and quotation. This matters when later amendments change wording without changing the identity of the underlying legal act.
Translation control: Record language, consolidation date and retrieval context separately from the ECLI, ELI or CELEX value. Quality assurance: Reopen the exact source version used during translation before final legal review.
59. Connection to Vocabulary Learning and How English Works
Legal translation depends on unusually precise vocabulary and syntax: obligation, permission, exception, scope, condition, reference and hierarchy all matter. The protected Vocabulary Learning Hub and How English Works ecosystem support that language layer without replacing the specialist identifier work on this page.
Translation control: Use those resources for linguistic competence and this page for legal-reference integrity. Quality assurance: Keep internal links complementary so no broad translation hub is duplicated.
60. Connection to the master translation architecture
This specialist owner sits beneath eduKateSG’s Master Art of Translation — Technical Translation System. The master owns general specifications, terminology, QA and change control; this article owns ECLI, ELI and CELEX identity.
Translation control: Link upward for system-level translation practice rather than repeating the master architecture. Quality assurance: Keep the page focused on legal identifiers, citations and source traceability.
61. Release checklist
Before release, verify every ECLI, ELI and CELEX value against an authoritative legal source; keep ECLI distinct from CELEX and domestic case numbers; preserve court codes and years; test ELI URIs; confirm CELEX sector and document type; distinguish original, consolidated, amended and corrigendum texts; preserve article, paragraph, recital and annex references; protect identifiers from MT and translation memory; test right-to-left rendering and PDF copy-paste; and compare every legal identifier in the target with the source set.
Then perform legal-linguistic QA on titles, court names, party names, institutional terminology, modal verbs, dates and quoted provisions. Identifier integrity lets the reader find the law; translation quality lets the reader understand it. Both layers are required.
62. Final rule: translate the law’s language, preserve the law’s identity
Cross-border legal communication works best when readers can move confidently between languages without losing the source. ECLI keeps judicial decisions traceable, ELI gives legislation web-oriented identity and metadata, and CELEX anchors documents inside EUR-Lex. Translate the words that explain the authority, but keep the identifier that proves which authority you mean.