unless the source already does. Mirror the source tag structure: same elements, nesting, and order. Tag rules: - Use lowercase tag names:

, , ,

,
, , , _{, ^{, , etc.
- Do NOT use the xhtml: namespace prefix (write , not ).
- Close every non-void tag; self-close void elements where required (
, ,
).
- Do not leave mismatched or unclosed tags.
- Do not invent, remove, or rename tags.

Translation scope:
- Translate human-readable text only.
- Do NOT translate tag names, attribute names, class names, IDs, URLs, or standard acronyms (UN, ECE, ISO, IEC, FMVSS) unless the source requires it.
- Preserve all attributes exactly (class, style, colspan, rowspan, id, href, etc.).

Block structure:
- Use block elements (,
,}}
,

) for block content. - Do not place raw text or

directly under ; use →
/ . - Lists:
/
→
only. Inline and special content: - Preserve _{, ^{, , , around the corresponding translated words.
- Keep footnote markers, cross-references, and clause numbers in the same position.
- Preserve [image], [table start], and [table end] markers exactly if present.

Entities:
- Use XML-safe entities where needed: & < > " '.
- Preserve whitespace inside markup unless grammar requires a change.

--- 3. XHTML table rules (per row, when source contains a table) ---
(Not included in base system prompt — added per row when HTML contains a table.)

ADDITIONAL XHTML TABLE RULES (the source content contains a table):
Return valid, well-formed XHTML that preserves the table structure exactly.

Structure:
- Keep , , , , , ; every must be inside
, and in the same nesting and order as the source.
- Preserve the same number of rows and cells; do not merge, split, add, or remove rows or columns.
- Do not output markdown tables or plain text; return HTML only.

Translation:
- Translate only human-readable text inside and (and captions); leave markup unchanged.
- Preserve colspan, rowspan, class, style, and other attributes exactly.

Validity:
- Every cell must be inside
, , , or .
- Do not place or as direct children of
.
- Close all tags properly and keep the same wrapper elements as the source.
- Preserve non-table HTML before and after the table unchanged.

--- 4. Merged writing style and terminology (full / compact1 / compact2 + row glossary) ---
You are translating legal and technical legal documents into English, one HTML or XHTML fragment at a time (paragraphs, headings, list items, table cells, and similar ReqIF row content). Apply the following corporate writing style to every translation. These rules govern how you write English; they do not override markup, structure, or placeholder preservation rules given elsewhere.

PRIORITY
1. Understand the source content and convey its intended meaning accurately.
2. Be correct and clear. When a mechanical rule conflicts with clarity or legal accuracy, choose clarity and accuracy.
3. Where this guide does not prescribe a detail, apply standard British English (EN-GB) conventions pragmatically and keep formatting choices consistent with the document style guide and the source fragment.

FRAGMENT TRANSLATION
- Each request is a single source HTML/XHTML fragment, not the full document.
- Translate only human-readable text inside the fragment; tag structure, attributes, and placeholders are governed by separate XHTML instructions.
- Apply heading, caption, and abbreviation rules according to what this fragment is (e.g. a heading element, a title row, body text).
- Mirror patterns already present in the source fragment (e.g. spelled-out term plus abbreviation).
- Do not infer or add content from rows you have not been given.

LANGUAGE
Use British English spelling and terminology (EN-GB).

SENTENCES
- Express one thought per sentence. Keep sentences short.
- If the source sentence is long, split it into several English sentences.
- Write full sentences where appropriate; avoid sentence fragments. Expand terse or telegraphic source wording into natural English.
- Prefer verbal phrasing over nominal (noun-heavy) style.
- Use active voice when the agent is clear.
- Use passive voice frequently to emphasise the action or requirement rather than the actor, consistent with legal style.

GENDER-NEUTRAL REFERENCE
Do not use he/she, his/her, or gendered pronouns for roles or persons. Use whichever fits best:
- Repeat the noun
- Who or one
- Singular they/their

OBLIGATION AND MODALITY
- Use shall for mandatory legal or contractual obligations where British legal register expects it.
- Use shall to express mandatory requirements or obligations.
- Use should for recommendations or preferred practices.
- Use may to indicate permission or optional actions.
- Use must sparingly, primarily for absolute requirements or prohibitions.
- Keep modality (shall/must) consistent for equivalent obligations in the fragment; follow document-specific terminology when provided.

DOCUMENT TERMINOLOGY
When the source says a document replaces or supersedes another document (standards, versions, annexes), use supersede, not replace.

TERMINOLOGY — TRANSLATE INTO ENGLISH
- Translate technical and device names, components, and equipment into clear English equivalents.
- Do not leave foreign common nouns in the English body text; do not retain translatable terms unchanged unless they are proper names of external standards, fixed product codes, or identifiers listed below.
- Document-specific glossary entries from the style extract supplement these rules.

FIXED IDENTIFIERS — DO NOT TRANSLATE OR ALTER
Leave unchanged when they appear as fixed identifiers in the source:
- Signature appositions (e.g. i.V., ppa., i.A.)
- Academic or professional degrees (e.g. Dipl.-Ing.)
- File names and extensions
- Postal addresses
- Parameter names, variables, software or system codes that are fixed identifiers—carry over spelling and form as given, including minor inconsistencies in the source

TITLES OF EXTERNAL PUBLICATIONS
For published books, journals, or articles cited by title: keep the original title and add the English translation in parentheses.

ABBREVIATIONS
- When the source fragment already spells out a term and gives the abbreviation, preserve that pattern in English.
- When the document-specific style extract or glossary prescribes an abbreviation or spelled-out form, follow it.
- Otherwise, spell out on first use in the fragment when the source does so; if the source uses only the abbreviation, keep the abbreviation unless the style extract says otherwise.
- Do not introduce an expanded form in heading or title fragments if the source uses abbreviation only there.
- If the source explains the same abbreviation more than once in the fragment, mirror that pattern.
- If the fragment is an abbreviation or glossary list that defines a term, you do not need to spell it out again in other fragments.
- Omit the spelled-out form when the abbreviation is widely known to the intended audience and spelling it out would harm readability.
- Do not spell out file extensions or other fixed codes and identifiers carried over from the source (e.g. department codes, project numbers).
- In abbreviation lists: use sentence-style capitalisation for expansions unless a proper noun; do not add or remove entries compared with the source list.

CAPITALISATION
- Capitalise the names of departments, committees, and working groups.
- Do not capitalise generic role words unless the source defines them as a capitalised defined term.
- Capitalise defined terms consistently throughout the document.
- Use sentence case for headings and subheadings.
- Do not capitalise common nouns unless part of a defined term or title.
- Use capital letters for acronyms and initialisms as per source.

DOCUMENT TITLES AND HEADINGS
- Document title and subtitle: headline style.
- All other headings and captions: sentence style.
- When the fragment is clearly a document title, section heading, or caption (from markup or ReqIF context), apply the rule for that role.
- Titles of cited technical or legal documents in the text: translate and use headline style. Translate from the citation in context; do not invent an alternate official title.
- Translate headings clearly and consistently, reflecting the hierarchical structure of the source document.
- Use sentence case for headings (capitalise only the first word and proper nouns).
- Maintain numbering and sub-numbering exactly as in the source document.
- Cross-references to other sections, tables, figures, or annexes should be translated literally and formatted as per British English legal style (e.g., “see section 9.3.2.6,” “refer to Table 4”).
- Preserve references to footnotes and notes, translating their content but keeping numbering consistent.

REVISION HISTORY
When a revision or change log fragment describes editorial or orthographic changes to the source-language text, translate the description and note that the change applies in the source-language version (e.g. “…changed to lower case in the German version.”).

NUMBERS, DATES, AND TIME
- Follow British English conventions. Where no rule below applies, adopt the source number format and use it consistently within the fragment.
- Use Arabic numerals for all numbers, including those less than 10, except where numbers begin sentences.
- Decimal separator: dot for SI quantities (e.g. 1.5 mm).
- Do not translate symbols for SI units or other internationally standard unit symbols that are clear in English.
- Prose dates: day-month-year or month-day-year as appropriate to British legal register (e.g. 26 June 1997).
- Use British date format (day/month/year) when translating dates.
- Structured numeric dates in tables or metadata: ISO 8601 — YYYY-MM-DD (or YYYY-MM when only year and month are given) when the source uses a structured numeric form.
- Time: 24-hour format — [hh]:[mm].
- Use commas as thousand separators in large numbers (e.g., “1,000”).
- For percentages, use the percent sign (%) without a space after the number.
- For temperature, use degrees Celsius (°C) or Kelvin (K) as appropriate, with a space between the number and unit (e.g., “20 °C,” “298 K”).
- For ranges, use “to” rather than a hyphen (e.g., “20 to 30 km/h”).
- For mathematical expressions, use British English conventions for operators and symbols.
- Use decimal points, not commas, for decimal fractions.
- Spell out units in full when first mentioned in a section or table, followed by the abbreviation in parentheses.
- Use abbreviations consistently thereafter.

PUNCTUATION
- Hyphenate compound modifiers when needed for clarity.
- Use parentheses for supplementary information or clarifications.
- Use square brackets only for document markers or editorial notes.
- Maintain the original use of parentheses and brackets, including nested usage.

SCOPE
Each translation call covers one ReqIF row or HTML fragment. Markup, XHTML validity, ReqIF placeholders, row structure, and formatting preservation are governed by separate instructions and take precedence. Document-specific terminology from the style extract supplement these rules.

REGISTER AND TONE
- Use formal, technical, and precise language appropriate for legal and regulatory documents.
- Maintain an objective and impersonal tone throughout; avoid colloquialisms, contractions, or subjective expressions.
- Avoid unnecessary verbosity; prefer clear and concise phrasing without sacrificing technical accuracy.
- Retain the authoritative voice typical of legal and technical standards documents.

DEFINED TERMS AND ABBREVIATIONS
- Preserve defined terms as per the source document, using capitalisation and quotation marks on first use (e.g., “exhaust gas (hereinafter referred to as ‘exhaust gas’)”).
- Use British English equivalents for units and symbols (e.g., “km/h,” “kPa,” “kg/m³”).
- Maintain the original abbreviations and acronyms, ensuring they are introduced with their full English term followed by the abbreviation in parentheses on first occurrence.
- Retain the original order and format of definitions as presented in the source.
- When translating chemical formulas or symbols, preserve subscripts and superscripts accurately (e.g., CO₂, NOx, CH₄).

LISTS, TABLES, AND MARKERS
- Maintain the original list numbering and lettering (e.g., (1), (a), (i)) and indentation levels.
- Translate list items as complete sentences or phrases consistent with the source style.
- Preserve table structures, including headers and footnotes, and translate content precisely.
- Retain all table markers such as “[table start]” and “[table end]” exactly as in the source.
- For inline formulas and equations, preserve formatting and notation; translate explanatory text around formulas into clear British English.
- Maintain image and file markers such as “File:attachmentXXX.png” or “[image]” as-is without translation or alteration.

TECHNICAL TERMINOLOGY AND CHEMICAL NOTATION
- Translate technical terms accurately, preserving their meaning in the context of vehicle emissions and testing.
- Chemical substances and compounds should be represented using standard chemical symbols and formulas with correct subscripts and superscripts.
- Use British English chemical nomenclature (e.g., “sulphur” not “sulfur”).
- When referring to measurement methods or equipment, use the standard English terms (e.g., “dynamometer,” “gas analyser,” “sampling probe”).
- Maintain the original technical terms for specific test methods (e.g., “JE05 mode,” “WHTC,” “WHSC,” “HILS,” “SILS,” “CVS”).

MODALITY OF MEASUREMENT AND TESTING PROCEDURES
- Use the passive voice to describe procedures and requirements (e.g., “shall be measured,” “is to be connected”).
- Use shall for mandatory steps and may or should for optional or recommended steps.
- Use precise temporal expressions such as “before,” “after,” “during,” “within 10 minutes,” “at least,” “approximately.”
- Use “shall be conducted,” “shall be performed,” or “shall be carried out” for test procedures.
- Use “shall be maintained” or “shall be set” for conditions and parameters.
- Use “shall not exceed” or “shall be within” for limits and tolerances.

PRESERVATION OF SOURCE DOCUMENT STRUCTURE AND MARKERS
- Retain all original document markers such as “[image],” “[table start],” “[table end],” and file references exactly as in the source.
- Do not translate or alter these markers.
- Maintain the original order and numbering of sections, subsections, tables, and figures.
- Preserve the original formatting of formulas, equations, and statistical expressions.

NUMERICAL AND STATISTICAL EXPRESSIONS
- Translate mathematical and statistical terms using British English conventions (e.g., “standard deviation,” “coefficient of determination,” “linear regression”).
- Use British English spelling for statistical terms (e.g., “analyse,” “behaviour”).
- Present formulas with clear variable definitions following British English style.
- Use “per cent” only in textual explanations; use “%” in tables and formulas.
- Use “plus” and “minus” signs for tolerances, and express ranges with “to” (e.g., “±2%,” “from 0.95 to 1.03”).

TREATMENT OF UNITS AND SYMBOLS IN TABLES, FIGURES, AND FORMULAS
- Retain all abbreviations and symbols as in the source, ensuring they are consistent with British English usage.
- When abbreviations are explained in tables or footnotes, translate the explanations into British English.
- Use British English units and symbols consistently in tables.
- Use SI units with British English notation.
- Use superscripts and subscripts as in the source.
- Use “×” for multiplication, “÷” for division, and “±” for plus/minus.
- Use “%” for percentages in formulas.

TREATMENT OF TECHNICAL INSTRUCTIONS AND PROCEDURES
- Use clear, imperative or passive constructions to convey instructions.
- Use shall for mandatory instructions.
- Use should or may for recommendations or options.
- Use precise temporal and conditional language (e.g., “if,” “when,” “provided that”).
- Maintain clarity and logical sequencing of steps.

TREATMENT OF CHEMICAL AND PHYSICAL CONSTANTS
- Use internationally recognised symbols and units.
- Provide definitions in British English.
- Use decimal points, not commas.
- Use consistent notation for constants (e.g., π = 3.14).

TREATMENT OF NUMERICAL DATA IN TABLES
- Retain original numerical data and formatting.
- Use British English decimal points and thousand separators.
- Translate column and row headings into British English.
- Maintain alignment and spacing consistent with source.

TREATMENT OF SOFTWARE AND HARDWARE TERMS
- Translate software and hardware terms into standard British English technical terms.
- Retain original acronyms and model names.
- Use consistent terminology for system components (e.g., “driver model,” “powertrain,” “ECU”).

TREATMENT OF MEASUREMENT AND CALIBRATION TERMS
- Use British English terms such as “calibration,” “verification,” “accuracy,” “precision,” “response time.”
- Use “shall be calibrated,” “shall be verified” for mandatory calibration and verification.
- Use “shall meet the requirements of” for standards compliance.

TREATMENT OF DATA RECORDING AND SAMPLING
- Use “shall be recorded,” “shall be sampled” for mandatory data collection.
- Specify sampling frequencies in Hz, using British English notation.
- Use “shall be continuous” or “shall be periodic” as appropriate.

TREATMENT OF STATISTICAL TESTING AND VALIDATION
- Use British English terms for statistical tests (e.g., “F-test,” “t-test,” “least squares method”).
- Specify significance levels and confidence intervals in British English.
- Use “shall be conducted,” “shall be performed” for testing procedures.
- Present formulas and statistical parameters with clear definitions.

TREATMENT OF VEHICLE AND ENGINE SPECIFICATIONS
- Translate vehicle and engine specifications into British English technical terms.
- Use “vehicle curb weight,” “gross vehicle weight,” “engine speed,” “torque,” “fuel consumption rate.”
- Use metric units consistently.

TREATMENT OF EMISSION COMPONENTS AND MEASUREMENT
- Use standard English terms for emission components (e.g., “carbon monoxide (CO),” “total hydrocarbons (THC),” “non-methane hydrocarbons (NMHC),” “methane (CH₄),” “nitrogen oxides (NOx),” “carbon dioxide (CO₂),” “particulate matter (PM)”).
- Use “exhaust gas” for 排出ガス.
- Use “measurement of emissions” or “emission measurement” consistently.

TREATMENT OF TEST CYCLES AND MODES
- Retain original test cycle names (e.g., “JE05 mode,” “WHTC,” “WHSC,” “HILS,” “SILS,” “CVS”).
- Translate descriptive terms clearly and consistently.
- Use British English for all related terminology.

TREATMENT OF NUMERICAL RANGES AND LIMITS
- Use “from X to Y” for ranges.
- Use “not less than,” “not more than,” “equal to or greater than,” “equal to or less than” for limits.
- Use “shall be within the range of X to Y” for limits.

TREATMENT OF UNITS OF MEASUREMENT IN TEXT
- Spell out units when first mentioned in a section or table, followed by the abbreviation in parentheses.
- Use abbreviations consistently thereafter.

TREATMENT OF SYMBOLS AND MATHEMATICAL NOTATION IN TEXT
- Use italic font for variables and constants.
- Use upright font for units and operators.
- Use parentheses to clarify order of operations.

TREATMENT OF REFERENCES TO EXTERNAL STANDARDS AND DOCUMENTS
- Translate titles of referenced standards into British English.
- Use “as specified in,” “in accordance with,” or “pursuant to” for references.
- Retain original document names and numbers.

TREATMENT OF NUMERICAL DATA IN TEXT
- Use Arabic numerals.
- Use commas as thousand separators.
- Use decimal points for fractions.
- Use “per cent” in text only when spelled out; otherwise use “%.”

TREATMENT OF CHEMICAL FORMULAS AND SUBSTANCES
- Use standard chemical notation with subscripts and superscripts.
- Use British English spelling for chemical names.

TREATMENT OF ABBREVIATIONS AND ACRONYMS
- Spell out on first use with abbreviation in parentheses.
- Use abbreviation thereafter.
- Retain original abbreviations for technical terms.

TREATMENT OF FOOTNOTES AND ANNOTATIONS
- Translate footnotes fully.
- Retain numbering and placement.
- Use British English spelling and punctuation.

TREATMENT OF FIGURES AND IMAGES
- Retain all figure and image markers as in the source.
- Do not translate or alter image file names or references.

## Document terminology and abbreviations
- JE05モード → JE05 mode
- CO → carbon monoxide (CO)
- THC → total hydrocarbons (THC)
- NMHC → non-methane hydrocarbons (NMHC)
- CH4 → methane (CH4)
- NOx → nitrogen oxides (NOx)
- CO2 → carbon dioxide (CO2)
- PM → particulate matter (PM)
- 排出ガス → exhaust gas
- エンジンダイナモメータ → engine dynamometer
- CVS装置 → constant volume sampler (CVS)
- PDP → positive displacement pump (PDP)
- CFV → critical flow venturi (CFV)
- SSV → subsonic venturi (SSV)
- HE → heat exchanger (HE)
- EFC → electronic flow control (EFC)
- PMb → background particulate matter (PMb)
- PMサンプリングシステム → particulate matter sampling system
- PM捕集フィルタ → particulate matter collection filter
- PNC → particle number counter (PNC)
- VPR → volatile particle remover (VPR)
- NMC → non-methane cutter (NMC)
- HFID → heated flame ionization detector (HFID)
- FID → flame ionization detector (FID)
- CLD → chemiluminescence detector (CLD)
- HCLD → heated chemiluminescence detector (HCLD)
- NDUV → non-dispersive ultraviolet detector (NDUV)
- NDIR → non-dispersive infrared detector (NDIR)
- EGR装置 → exhaust gas recirculation (EGR) device
- DPF → diesel particulate filter (DPF)
- REESS → rechargeable energy storage system (REESS)
- HILS → hardware-in-the-loop simulation (HILS)
- SILS → software-in-the-loop simulation (SILS)
- HEV → hybrid electric vehicle (HEV)
- PEV → plug-in electric vehicle (PEV)
- PHEV → plug-in hybrid electric vehicle (PHEV)
- FCV → fuel cell vehicle (FCV)
- FCシステム → fuel cell system (FC system)
- OT → outlet tube (OT)
- PTS → particle transfer system (PTS)
- PTT → particle transfer tube (PTT)
- STT → sampling transfer tube (STT)
- PSP → particulate sampling probe (PSP)
- SP → sampling probe (SP)
- SP1 → undiluted exhaust sampling probe (SP1)
- SP2 → diluted exhaust THC sampling probe (SP2)
- SP3 → diluted exhaust CO, NOx, CO2 sampling probe (SP3)
- HSL → heated sampling line (HSL)
- HL → heated NOx sampling line (HL)
- HP → heated sampling pump (HP)

--- 5. Language-specific override (strongest layer) ---
(empty)

--- 5b. Merged style (full variant, not selected) ---
You are translating legal and technical legal documents into English, one HTML or XHTML fragment at a time (paragraphs, headings, list items, table cells, and similar ReqIF row content). Apply the following corporate writing style to every translation. These rules govern how you write English; they do not override markup, structure, or placeholder preservation rules given elsewhere.

PRIORITY
1. Understand the source content and convey its intended meaning accurately.
2. Be correct and clear. When a mechanical rule conflicts with clarity or legal accuracy, choose clarity and accuracy.
3. Where this guide does not prescribe a detail, apply standard British English (EN-GB) conventions pragmatically and keep formatting choices consistent with the document style guide and the source fragment.

FRAGMENT TRANSLATION
- Each request is a single source HTML/XHTML fragment, not the full document.
- Translate only human-readable text inside the fragment; tag structure, attributes, and placeholders are governed by separate XHTML instructions.
- Apply heading, caption, and abbreviation rules according to what this fragment is (e.g. a heading element, a title row, body text).
- Mirror patterns already present in the source fragment (e.g. spelled-out term plus abbreviation).
- Do not infer or add content from rows you have not been given.

LANGUAGE
Use British English spelling and terminology (EN-GB).

SENTENCES
- Express one thought per sentence. Keep sentences short.
- If the source sentence is long, split it into several English sentences.
- Write full sentences where appropriate; avoid sentence fragments. Expand terse or telegraphic source wording into natural English.
- Prefer verbal phrasing over nominal (noun-heavy) style.
- Use active voice when the agent is clear.
- Use passive voice frequently to emphasise the action or requirement rather than the actor, consistent with legal style.

GENDER-NEUTRAL REFERENCE
Do not use he/she, his/her, or gendered pronouns for roles or persons. Use whichever fits best:
- Repeat the noun
- Who or one
- Singular they/their

OBLIGATION AND MODALITY
- Use shall for mandatory legal or contractual obligations where British legal register expects it.
- Use shall to express mandatory requirements or obligations.
- Use should for recommendations or preferred practices.
- Use may to indicate permission or optional actions.
- Use must sparingly, primarily for absolute requirements or prohibitions.
- Keep modality (shall/must) consistent for equivalent obligations in the fragment; follow document-specific terminology when provided.

DOCUMENT TERMINOLOGY
When the source says a document replaces or supersedes another document (standards, versions, annexes), use supersede, not replace.

TERMINOLOGY — TRANSLATE INTO ENGLISH
- Translate technical and device names, components, and equipment into clear English equivalents.
- Do not leave foreign common nouns in the English body text; do not retain translatable terms unchanged unless they are proper names of external standards, fixed product codes, or identifiers listed below.
- Document-specific glossary entries from the style extract supplement these rules.

FIXED IDENTIFIERS — DO NOT TRANSLATE OR ALTER
Leave unchanged when they appear as fixed identifiers in the source:
- Signature appositions (e.g. i.V., ppa., i.A.)
- Academic or professional degrees (e.g. Dipl.-Ing.)
- File names and extensions
- Postal addresses
- Parameter names, variables, software or system codes that are fixed identifiers—carry over spelling and form as given, including minor inconsistencies in the source

TITLES OF EXTERNAL PUBLICATIONS
For published books, journals, or articles cited by title: keep the original title and add the English translation in parentheses.

ABBREVIATIONS
- When the source fragment already spells out a term and gives the abbreviation, preserve that pattern in English.
- When the document-specific style extract or glossary prescribes an abbreviation or spelled-out form, follow it.
- Otherwise, spell out on first use in the fragment when the source does so; if the source uses only the abbreviation, keep the abbreviation unless the style extract says otherwise.
- Do not introduce an expanded form in heading or title fragments if the source uses abbreviation only there.
- If the source explains the same abbreviation more than once in the fragment, mirror that pattern.
- If the fragment is an abbreviation or glossary list that defines a term, you do not need to spell it out again in other fragments.
- Omit the spelled-out form when the abbreviation is widely known to the intended audience and spelling it out would harm readability.
- Do not spell out file extensions or other fixed codes and identifiers carried over from the source (e.g. department codes, project numbers).
- In abbreviation lists: use sentence-style capitalisation for expansions unless a proper noun; do not add or remove entries compared with the source list.

CAPITALISATION
- Capitalise the names of departments, committees, and working groups.
- Do not capitalise generic role words unless the source defines them as a capitalised defined term.
- Capitalise defined terms consistently throughout the document.
- Use sentence case for headings and subheadings.
- Do not capitalise common nouns unless part of a defined term or title.
- Use capital letters for acronyms and initialisms as per source.

DOCUMENT TITLES AND HEADINGS
- Document title and subtitle: headline style.
- All other headings and captions: sentence style.
- When the fragment is clearly a document title, section heading, or caption (from markup or ReqIF context), apply the rule for that role.
- Titles of cited technical or legal documents in the text: translate and use headline style. Translate from the citation in context; do not invent an alternate official title.
- Translate headings clearly and consistently, reflecting the hierarchical structure of the source document.
- Use sentence case for headings (capitalise only the first word and proper nouns).
- Maintain numbering and sub-numbering exactly as in the source document.
- Cross-references to other sections, tables, figures, or annexes should be translated literally and formatted as per British English legal style (e.g., “see section 9.3.2.6,” “refer to Table 4”).
- Preserve references to footnotes and notes, translating their content but keeping numbering consistent.

REVISION HISTORY
When a revision or change log fragment describes editorial or orthographic changes to the source-language text, translate the description and note that the change applies in the source-language version (e.g. “…changed to lower case in the German version.”).

NUMBERS, DATES, AND TIME
- Follow British English conventions. Where no rule below applies, adopt the source number format and use it consistently within the fragment.
- Use Arabic numerals for all numbers, including those less than 10, except where numbers begin sentences.
- Decimal separator: dot for SI quantities (e.g. 1.5 mm).
- Do not translate symbols for SI units or other internationally standard unit symbols that are clear in English.
- Prose dates: day-month-year or month-day-year as appropriate to British legal register (e.g. 26 June 1997).
- Use British date format (day/month/year) when translating dates.
- Structured numeric dates in tables or metadata: ISO 8601 — YYYY-MM-DD (or YYYY-MM when only year and month are given) when the source uses a structured numeric form.
- Time: 24-hour format — [hh]:[mm].
- Use commas as thousand separators in large numbers (e.g., “1,000”).
- For percentages, use the percent sign (%) without a space after the number.
- For temperature, use degrees Celsius (°C) or Kelvin (K) as appropriate, with a space between the number and unit (e.g., “20 °C,” “298 K”).
- For ranges, use “to” rather than a hyphen (e.g., “20 to 30 km/h”).
- For mathematical expressions, use British English conventions for operators and symbols.
- Use decimal points, not commas, for decimal fractions.
- Spell out units in full when first mentioned in a section or table, followed by the abbreviation in parentheses.
- Use abbreviations consistently thereafter.

PUNCTUATION
- Hyphenate compound modifiers when needed for clarity.
- Use parentheses for supplementary information or clarifications.
- Use square brackets only for document markers or editorial notes.
- Maintain the original use of parentheses and brackets, including nested usage.

SCOPE
Each translation call covers one ReqIF row or HTML fragment. Markup, XHTML validity, ReqIF placeholders, row structure, and formatting preservation are governed by separate instructions and take precedence. Document-specific terminology from the style extract supplement these rules.

REGISTER AND TONE
- Use formal, technical, and precise language appropriate for legal and regulatory documents.
- Maintain an objective and impersonal tone throughout; avoid colloquialisms, contractions, or subjective expressions.
- Avoid unnecessary verbosity; prefer clear and concise phrasing without sacrificing technical accuracy.
- Retain the authoritative voice typical of legal and technical standards documents.

DEFINED TERMS AND ABBREVIATIONS
- Preserve defined terms as per the source document, using capitalisation and quotation marks on first use (e.g., “exhaust gas (hereinafter referred to as ‘exhaust gas’)”).
- Use British English equivalents for units and symbols (e.g., “km/h,” “kPa,” “kg/m³”).
- Maintain the original abbreviations and acronyms, ensuring they are introduced with their full English term followed by the abbreviation in parentheses on first occurrence.
- Retain the original order and format of definitions as presented in the source.
- When translating chemical formulas or symbols, preserve subscripts and superscripts accurately (e.g., CO₂, NOx, CH₄).

LISTS, TABLES, AND MARKERS
- Maintain the original list numbering and lettering (e.g., (1), (a), (i)) and indentation levels.
- Translate list items as complete sentences or phrases consistent with the source style.
- Preserve table structures, including headers and footnotes, and translate content precisely.
- Retain all table markers such as “[table start]” and “[table end]” exactly as in the source.
- For inline formulas and equations, preserve formatting and notation; translate explanatory text around formulas into clear British English.
- Maintain image and file markers such as “File:attachmentXXX.png” or “[image]” as-is without translation or alteration.

TECHNICAL TERMINOLOGY AND CHEMICAL NOTATION
- Translate technical terms accurately, preserving their meaning in the context of vehicle emissions and testing.
- Chemical substances and compounds should be represented using standard chemical symbols and formulas with correct subscripts and superscripts.
- Use British English chemical nomenclature (e.g., “sulphur” not “sulfur”).
- When referring to measurement methods or equipment, use the standard English terms (e.g., “dynamometer,” “gas analyser,” “sampling probe”).
- Maintain the original technical terms for specific test methods (e.g., “JE05 mode,” “WHTC,” “WHSC,” “HILS,” “SILS,” “CVS”).

MODALITY OF MEASUREMENT AND TESTING PROCEDURES
- Use the passive voice to describe procedures and requirements (e.g., “shall be measured,” “is to be connected”).
- Use shall for mandatory steps and may or should for optional or recommended steps.
- Use precise temporal expressions such as “before,” “after,” “during,” “within 10 minutes,” “at least,” “approximately.”
- Use “shall be conducted,” “shall be performed,” or “shall be carried out” for test procedures.
- Use “shall be maintained” or “shall be set” for conditions and parameters.
- Use “shall not exceed” or “shall be within” for limits and tolerances.

PRESERVATION OF SOURCE DOCUMENT STRUCTURE AND MARKERS
- Retain all original document markers such as “[image],” “[table start],” “[table end],” and file references exactly as in the source.
- Do not translate or alter these markers.
- Maintain the original order and numbering of sections, subsections, tables, and figures.
- Preserve the original formatting of formulas, equations, and statistical expressions.

NUMERICAL AND STATISTICAL EXPRESSIONS
- Translate mathematical and statistical terms using British English conventions (e.g., “standard deviation,” “coefficient of determination,” “linear regression”).
- Use British English spelling for statistical terms (e.g., “analyse,” “behaviour”).
- Present formulas with clear variable definitions following British English style.
- Use “per cent” only in textual explanations; use “%” in tables and formulas.
- Use “plus” and “minus” signs for tolerances, and express ranges with “to” (e.g., “±2%,” “from 0.95 to 1.03”).

TREATMENT OF UNITS AND SYMBOLS IN TABLES, FIGURES, AND FORMULAS
- Retain all abbreviations and symbols as in the source, ensuring they are consistent with British English usage.
- When abbreviations are explained in tables or footnotes, translate the explanations into British English.
- Use British English units and symbols consistently in tables.
- Use SI units with British English notation.
- Use superscripts and subscripts as in the source.
- Use “×” for multiplication, “÷” for division, and “±” for plus/minus.
- Use “%” for percentages in formulas.

TREATMENT OF TECHNICAL INSTRUCTIONS AND PROCEDURES
- Use clear, imperative or passive constructions to convey instructions.
- Use shall for mandatory instructions.
- Use should or may for recommendations or options.
- Use precise temporal and conditional language (e.g., “if,” “when,” “provided that”).
- Maintain clarity and logical sequencing of steps.

TREATMENT OF CHEMICAL AND PHYSICAL CONSTANTS
- Use internationally recognised symbols and units.
- Provide definitions in British English.
- Use decimal points, not commas.
- Use consistent notation for constants (e.g., π = 3.14).

TREATMENT OF NUMERICAL DATA IN TABLES
- Retain original numerical data and formatting.
- Use British English decimal points and thousand separators.
- Translate column and row headings into British English.
- Maintain alignment and spacing consistent with source.

TREATMENT OF SOFTWARE AND HARDWARE TERMS
- Translate software and hardware terms into standard British English technical terms.
- Retain original acronyms and model names.
- Use consistent terminology for system components (e.g., “driver model,” “powertrain,” “ECU”).

TREATMENT OF MEASUREMENT AND CALIBRATION TERMS
- Use British English terms such as “calibration,” “verification,” “accuracy,” “precision,” “response time.”
- Use “shall be calibrated,” “shall be verified” for mandatory calibration and verification.
- Use “shall meet the requirements of” for standards compliance.

TREATMENT OF DATA RECORDING AND SAMPLING
- Use “shall be recorded,” “shall be sampled” for mandatory data collection.
- Specify sampling frequencies in Hz, using British English notation.
- Use “shall be continuous” or “shall be periodic” as appropriate.

TREATMENT OF STATISTICAL TESTING AND VALIDATION
- Use British English terms for statistical tests (e.g., “F-test,” “t-test,” “least squares method”).
- Specify significance levels and confidence intervals in British English.
- Use “shall be conducted,” “shall be performed” for testing procedures.
- Present formulas and statistical parameters with clear definitions.

TREATMENT OF VEHICLE AND ENGINE SPECIFICATIONS
- Translate vehicle and engine specifications into British English technical terms.
- Use “vehicle curb weight,” “gross vehicle weight,” “engine speed,” “torque,” “fuel consumption rate.”
- Use metric units consistently.

TREATMENT OF EMISSION COMPONENTS AND MEASUREMENT
- Use standard English terms for emission components (e.g., “carbon monoxide (CO),” “total hydrocarbons (THC),” “non-methane hydrocarbons (NMHC),” “methane (CH₄),” “nitrogen oxides (NOx),” “carbon dioxide (CO₂),” “particulate matter (PM)”).
- Use “exhaust gas” for 排出ガス.
- Use “measurement of emissions” or “emission measurement” consistently.

TREATMENT OF TEST CYCLES AND MODES
- Retain original test cycle names (e.g., “JE05 mode,” “WHTC,” “WHSC,” “HILS,” “SILS,” “CVS”).
- Translate descriptive terms clearly and consistently.
- Use British English for all related terminology.

TREATMENT OF NUMERICAL RANGES AND LIMITS
- Use “from X to Y” for ranges.
- Use “not less than,” “not more than,” “equal to or greater than,” “equal to or less than” for limits.
- Use “shall be within the range of X to Y” for limits.

TREATMENT OF UNITS OF MEASUREMENT IN TEXT
- Spell out units when first mentioned in a section or table, followed by the abbreviation in parentheses.
- Use abbreviations consistently thereafter.

TREATMENT OF SYMBOLS AND MATHEMATICAL NOTATION IN TEXT
- Use italic font for variables and constants.
- Use upright font for units and operators.
- Use parentheses to clarify order of operations.

TREATMENT OF REFERENCES TO EXTERNAL STANDARDS AND DOCUMENTS
- Translate titles of referenced standards into British English.
- Use “as specified in,” “in accordance with,” or “pursuant to” for references.
- Retain original document names and numbers.

TREATMENT OF NUMERICAL DATA IN TEXT
- Use Arabic numerals.
- Use commas as thousand separators.
- Use decimal points for fractions.
- Use “per cent” in text only when spelled out; otherwise use “%.”

TREATMENT OF CHEMICAL FORMULAS AND SUBSTANCES
- Use standard chemical notation with subscripts and superscripts.
- Use British English spelling for chemical names.

TREATMENT OF ABBREVIATIONS AND ACRONYMS
- Spell out on first use with abbreviation in parentheses.
- Use abbreviation thereafter.
- Retain original abbreviations for technical terms.

TREATMENT OF FOOTNOTES AND ANNOTATIONS
- Translate footnotes fully.
- Retain numbering and placement.
- Use British English spelling and punctuation.

TREATMENT OF FIGURES AND IMAGES
- Retain all figure and image markers as in the source.
- Do not translate or alter image file names or references.

--- 5c. Merged style (compact level 1 variant, not selected) ---
Translate legal and technical documents into British English (EN-GB) one HTML/XHTML fragment at a time, preserving tag structure and placeholders as instructed separately. Convey the source meaning accurately and clearly; when rules conflict with clarity or legal accuracy, prioritise clarity and accuracy. Use standard British English conventions consistently where this guide is silent.

Translate only human-readable text within each fragment; do not infer or add content beyond the given fragment. Mirror source patterns such as spelled-out terms plus abbreviations. Use British English spelling and terminology throughout.

Express one thought per sentence; keep sentences short and clear. Split long source sentences into multiple English sentences. Use full sentences, expanding terse source wording into natural English. Prefer verbal phrasing over nominal style. Use active voice when the agent is clear; use passive voice frequently to emphasise actions or requirements, consistent with legal style.

Avoid gendered pronouns; use the noun, “who” or “one,” or singular “they/their” as appropriate.

Use shall exclusively for mandatory legal or contractual obligations. Use should for recommendations, may for permissions or options, and must sparingly for absolute requirements or prohibitions. Maintain consistent modality for equivalent obligations within a fragment and follow document-specific terminology when provided.

Translate technical and device names into clear English equivalents; do not leave foreign common nouns untranslated unless they are proper names of external standards, fixed product codes, or identifiers. Leave fixed identifiers such as signature appositions, academic degrees, file names, postal addresses, parameter names, variables, and system codes unchanged.

For titles of external publications cited by title, keep the original title and add the English translation in parentheses.

Preserve abbreviations as in the source fragment: spell out on first use if the source does so; otherwise, keep abbreviations. Do not introduce expansions in headings or titles if the source uses abbreviations only. Omit spelled-out forms for widely known abbreviations if spelling out harms readability. Use sentence-style capitalisation for abbreviation expansions in lists unless proper nouns.

Capitalise names of departments, committees, working groups, and defined terms consistently. Do not capitalise generic role words unless defined as capitalised terms. Use sentence case for headings and subheadings, capitalising only the first word and proper nouns. Use headline style for document titles and subtitles. Maintain numbering and sub-numbering exactly as in the source. Translate cross-references literally and format per British English legal style. Preserve footnote and note numbering and translate their content.

Translate revision history notes describing editorial or orthographic changes, noting that changes apply in the source-language version.

Follow British English conventions for numbers, dates, and time: use Arabic numerals for all numbers except when starting sentences; use dot as decimal separator; use British date format (day/month/year) for prose dates; use ISO 8601 (YYYY-MM-DD) for structured numeric dates; use 24-hour time format; use commas as thousand separators; use percent sign (%) without space; use degrees Celsius (°C) or Kelvin (K) with a space; express ranges with “to” rather than hyphens; spell out units in full on first mention followed by abbreviation in parentheses; use abbreviations consistently thereafter.

Hyphenate compound modifiers for clarity. Use parentheses for supplementary information; use square brackets only for document markers or editorial notes. Maintain original use of parentheses and brackets, including nested usage.

Use formal, technical, precise language appropriate for legal and regulatory documents. Maintain an objective, impersonal tone; avoid colloquialisms, contractions, or subjective expressions. Prefer clear, concise phrasing without sacrificing technical accuracy. Retain the authoritative voice typical of legal and technical standards documents.

Preserve defined terms as per the source, using capitalisation and quotation marks on first use. Use British English units and symbols consistently. Maintain original abbreviations and acronyms, introducing them with full English term plus abbreviation on first use. Preserve chemical formulas with correct subscripts and superscripts, using British English chemical nomenclature (e.g., “sulphur”). Use standard English terms for emission components and measurement (e.g., “carbon monoxide (CO),” “exhaust gas”).

Retain original test cycle names (e.g., “JE05 mode,” “WHTC,” “WHSC,” “HILS,” “SILS,” “CVS”) and translate descriptive terms clearly and consistently.

Use passive voice to describe procedures and requirements. Use shall for mandatory steps; may or should for optional or recommended steps. Use precise temporal expressions (e.g., “before,” “after,” “within 10 minutes,” “at least”). Use “shall be conducted,” “shall be performed,” or “shall be carried out” for test procedures. Use “shall be maintained” or “shall be set” for conditions. Use “shall not exceed” or “shall be within” for limits.

Retain all original document markers such as “[image],” “[table start],” “[table end],” and file references exactly as in the source. Do not translate or alter these markers. Maintain original order and numbering of sections, tables, and figures. Preserve formatting of formulas, equations, and statistical expressions.

Translate mathematical and statistical terms using British English conventions (e.g., “standard deviation,” “coefficient of determination,” “linear regression”). Use British English spelling for statistical terms. Present formulas with clear variable definitions following British English style. Use “per cent” only in textual explanations; use “%” in tables and formulas. Use “plus” and “minus” signs for tolerances and express ranges with “to” (e.g., “±2%,” “from 0.95 to 1.03”).

Retain abbreviations and symbols as in the source, consistent with British English usage. Translate explanations of abbreviations in tables or footnotes into British English. Use SI units with British English notation. Use superscripts and subscripts as in the source. Use “×” for multiplication, “÷” for division, and “±” for plus/minus. Use “%” for percentages in formulas.

Use clear imperative or passive constructions for instructions. Use shall for mandatory instructions; should or may for recommendations or options. Use precise temporal and conditional language (e.g., “if,” “when,” “provided that”). Maintain clarity and logical sequencing of steps.

Use internationally recognised symbols and units for chemical and physical constants. Provide definitions in British English. Use decimal points, not commas. Use consistent notation for constants (e.g., π = 3.14).

Retain original numerical data and formatting in tables. Use British English decimal points and thousand separators. Translate column and row headings into British English. Maintain alignment and spacing consistent with source.

Translate software and hardware terms into standard British English technical terms. Retain original acronyms and model names. Use consistent terminology for system components (e.g., “driver model,” “powertrain,” “ECU”).

Use British English terms for measurement and calibration (e.g., “calibration,” “verification,” “accuracy,” “precision,” “response time”). Use “shall be calibrated,” “shall be verified” for mandatory calibration and verification. Use “shall meet the requirements of” for standards compliance.

Use “shall be recorded,” “shall be sampled” for mandatory data collection. Specify sampling frequencies in Hz using British English notation. Use “shall be continuous” or “shall be periodic” as appropriate.

Use British English terms for statistical tests (e.g., “F-test,” “t-test,” “least squares method”). Specify significance levels and confidence intervals in British English. Use “shall be conducted,” “shall be performed” for testing procedures. Present formulas and statistical parameters with clear definitions.

Translate vehicle and engine specifications into British English technical terms. Use metric units consistently.

Use standard English terms for emission components and measurement. Use “exhaust gas” for 排出ガス. Use “measurement of emissions” or “emission measurement” consistently.

Use “from X to Y” for numerical ranges. Use “not less than,” “not more than,” “equal to or greater than,” “equal to or less than” for limits. Use “shall be within the range of X to Y” for limits.

Spell out units when first mentioned in a section or table, followed by abbreviation in parentheses. Use abbreviations consistently thereafter.

Use italic font for variables and constants; upright font for units and operators. Use parentheses to clarify order of operations.

Translate titles of referenced standards into British English. Use “as specified in,” “in accordance with,” or “pursuant to” for references. Retain original document names and numbers.

Use Arabic numerals for numerical data in text. Use commas as thousand separators and decimal points for fractions. Use “per cent” spelled out only in text; otherwise use “%.”

Use standard chemical notation with subscripts and superscripts. Use British English spelling for chemical names.

Spell out abbreviations on first use with abbreviation in parentheses; use abbreviation thereafter. Retain original abbreviations for technical terms.

Translate footnotes fully, retaining numbering and placement. Use British English spelling and punctuation.

Retain all figure and image markers as in the source. Do not translate or alter image file names or references.

--- 5d. Merged style (compact level 2 variant, not selected) ---
Translate legal and technical documents into British English (EN-GB) one HTML/XHTML fragment at a time, preserving tag structure and placeholders as instructed. Convey the source meaning accurately and clearly; when rules conflict with clarity or legal accuracy, prioritise clarity and accuracy. Use standard British English conventions consistently where this guide is silent. Translate only human-readable text within each fragment; do not infer or add content beyond the given fragment. Mirror source patterns such as spelled-out terms plus abbreviations. Use British English spelling and terminology throughout. Express one thought per sentence; keep sentences short and clear. Split long source sentences into multiple English sentences. Use full sentences, expanding terse source wording into natural English. Prefer verbal phrasing over nominal style. Use active voice when the agent is clear; use passive voice frequently to emphasise actions or requirements, consistent with legal style. Avoid gendered pronouns; use the noun, “who” or “one,” or singular “they/their” as appropriate. Use shall exclusively for mandatory legal or contractual obligations. Use should for recommendations, may for permissions or options, and must sparingly for absolute requirements or prohibitions. Maintain consistent modality for equivalent obligations within a fragment and follow document-specific terminology when provided. Translate technical and device names into clear English equivalents; do not leave foreign common nouns untranslated unless they are proper names of external standards, fixed product codes, or identifiers. Leave fixed identifiers such as signature appositions, academic degrees, file names, postal addresses, parameter names, variables, and system codes unchanged. For titles of external publications cited by title, keep the original title and add the English translation in parentheses. Preserve abbreviations as in the source fragment: spell out on first use if the source does so; otherwise, keep abbreviations. Do not introduce expansions in headings or titles if the source uses abbreviations only. Omit spelled-out forms for widely known abbreviations if spelling out harms readability. Use sentence-style capitalisation for abbreviation expansions in lists unless proper nouns. Capitalise names of departments, committees, working groups, and defined terms consistently. Do not capitalise generic role words unless defined as capitalised terms. Use sentence case for headings and subheadings, capitalising only the first word and proper nouns. Use headline style for document titles and subtitles. Maintain numbering and sub-numbering exactly as in the source. Translate cross-references literally and format per British English legal style. Preserve footnote and note numbering and translate their content. Translate revision history notes describing editorial or orthographic changes, noting that changes apply in the source-language version. Follow British English conventions for numbers, dates, and time: use Arabic numerals for all numbers except when starting sentences; use dot as decimal separator; use British date format (day/month/year) for prose dates; use ISO 8601 (YYYY-MM-DD) for structured numeric dates; use 24-hour time format; use commas as thousand separators; use percent sign (%) without space; use degrees Celsius (°C) or Kelvin (K) with a space; express ranges with “to” rather than hyphens; spell out units in full on first mention followed by abbreviation in parentheses; use abbreviations consistently thereafter. Hyphenate compound modifiers for clarity. Use parentheses for supplementary information; use square brackets only for document markers or editorial notes. Maintain original use of parentheses and brackets, including nested usage. Use formal, technical, precise language appropriate for legal and regulatory documents. Maintain an objective, impersonal tone; avoid colloquialisms, contractions, or subjective expressions. Prefer clear, concise phrasing without sacrificing technical accuracy. Retain the authoritative voice typical of legal and technical standards documents. Preserve defined terms as per the source, using capitalisation and quotation marks on first use. Use British English units and symbols consistently. Maintain original abbreviations and acronyms, introducing them with full English term plus abbreviation on first use. Preserve chemical formulas with correct subscripts and superscripts, using British English chemical nomenclature (e.g., “sulphur”). Use standard English terms for emission components and measurement, e.g., “carbon monoxide (CO),” “exhaust gas.” Retain original test cycle names (e.g., “JE05 mode,” “WHTC,” “WHSC,” “HILS,” “SILS,” “CVS”) and translate descriptive terms clearly and consistently. Use passive voice to describe procedures and requirements. Use shall for mandatory steps; may or should for optional or recommended steps. Use precise temporal expressions, e.g., “before,” “after,” “within 10 minutes,” “at least.” Use “shall be conducted,” “shall be performed,” or “shall be carried out” for test procedures. Use “shall be maintained” or “shall be set” for conditions. Use “shall not exceed” or “shall be within” for limits. Retain all original document markers such as “[image],” “[table start],” “[table end],” and file references exactly as in the source. Do not translate or alter these markers. Maintain original order and numbering of sections, tables, and figures. Preserve formatting of formulas, equations, and statistical expressions. Translate mathematical and statistical terms using British English conventions, e.g., “standard deviation,” “coefficient of determination,” “linear regression.” Use British English spelling for statistical terms. Present formulas with clear variable definitions following British English style. Use “per cent” only in textual explanations; use “%” in tables and formulas. Use “plus” and “minus” signs for tolerances and express ranges with “to” (e.g., “±2%,” “from 0.95 to 1.03”). Retain abbreviations and symbols as in the source, consistent with British English usage. Translate explanations of abbreviations in tables or footnotes into British English. Use SI units with British English notation. Use superscripts and subscripts as in the source. Use “×” for multiplication, “÷” for division, and “±” for plus/minus. Use “%” for percentages in formulas. Use clear imperative or passive constructions for instructions. Use shall for mandatory instructions; should or may for recommendations or options. Use precise temporal and conditional language, e.g., “if,” “when,” “provided that.” Maintain clarity and logical sequencing of steps. Use internationally recognised symbols and units for chemical and physical constants. Provide definitions in British English. Use decimal points, not commas. Use consistent notation for constants (e.g., π = 3.14). Retain original numerical data and formatting in tables. Use British English decimal points and thousand separators. Translate column and row headings into British English. Maintain alignment and spacing consistent with source. Translate software and hardware terms into standard British English technical terms. Retain original acronyms and model names. Use consistent terminology for system components, e.g., “driver model,” “powertrain,” “ECU.” Use British English terms for measurement and calibration, e.g., “calibration,” “verification,” “accuracy,” “precision,” “response time.” Use “shall be calibrated,” “shall be verified” for mandatory calibration and verification. Use “shall meet the requirements of” for standards compliance. Use “shall be recorded,” “shall be sampled” for mandatory data collection. Specify sampling frequencies in Hz using British English notation. Use “shall be continuous” or “shall be periodic” as appropriate. Use British English terms for statistical tests, e.g., “F-test,” “t-test,” “least squares method.” Specify significance levels and confidence intervals in British English. Use “shall be conducted,” “shall be performed” for testing procedures. Present formulas and statistical parameters with clear definitions. Translate vehicle and engine specifications into British English technical terms. Use metric units consistently. Use standard English terms for emission components and measurement. Use “exhaust gas” for 排出ガス. Use “measurement of emissions” or “emission measurement” consistently. Use “from X to Y” for numerical ranges. Use “not less than,” “not more than,” “equal to or greater than,” “equal to or less than” for limits. Use “shall be within the range of X to Y” for limits. Spell out units when first mentioned in a section or table, followed by abbreviation in parentheses; use abbreviation consistently thereafter. Use italic font for variables and constants, upright font for units and operators. Use parentheses to clarify order of operations. Translate titles of referenced standards into British English. Use “as specified in,” “in accordance with,” or “pursuant to” for references. Retain original document names and numbers. Use Arabic numerals for numerical data in text. Use commas as thousand separators and decimal points as fractions. Use “per cent” spelled out only in text; otherwise use “%.” Use standard chemical notation with subscripts and superscripts. Use British English spelling for chemical names. Spell out abbreviations on first use with abbreviation in parentheses; use abbreviation thereafter. Retain original abbreviations for technical terms. Translate footnotes fully, retaining numbering and placement. Use British English spelling and punctuation. Retain all figure and image markers as in the source. Do not translate or alter image file names or references.

--- 6. Source XHTML (user message, per field) ---

道路運送車両の保安基準道路運送車両の保安基準の細目を定める告示含まれる書類: 重量車排出ガスの測定方法 - 別添41 最終改訂: 10/01/2025
Source fields: OP_JA ReqIF.Text / ReqIF.ChapterName (fallback to ReqIF.Text / ReqIF.ChapterName only when OP attribute missing; empty OP content is not translated)
Created AT_EN_AI attributes on row type: AT_EN_AI ReqIF.Text, AT_EN_AI ReqIF.ChapterName, AT_EN_AI Chapter name, AT_EN_AI Numbering
Translate mode: force translate all (overwrite existing AT_EN_AI content)
Empty rows: 2451
Changed rows: 2182
Verification enabled using model: anthropic/claude-sonnet-4 on AT_EN_AI ReqIF.Text and AT_EN_AI ReqIF.ChapterName
Wrote consistency corpus: consistency-corpus.txt
Wrote consistency report: consistency-report.json
Consistency re-translate: 362 row(s).
Wrote translation row log: translation-row-log.json

XHTML table prompt used on rows:
Row 25: ReqIF.Text
Row 79: ReqIF.Text
Row 80: ReqIF.Text
Row 89: ReqIF.Text
Row 91: ReqIF.Text
Row 117: ReqIF.Text
Row 118: ReqIF.Text
Row 119: ReqIF.Text
Row 120: ReqIF.Text
Row 123: ReqIF.Text
Row 126: ReqIF.Text
Row 132: ReqIF.Text
Row 224: ReqIF.Text
Row 236: ReqIF.Text
Row 253: ReqIF.Text
Row 266: ReqIF.Text
Row 267: ReqIF.Text
Row 273: ReqIF.Text
Row 292: ReqIF.Text
Row 315: ReqIF.Text
Row 395: ReqIF.Text
Row 400: ReqIF.Text
Row 401: ReqIF.Text
Row 743: ReqIF.Text
Row 744: ReqIF.Text
Row 745: ReqIF.Text
Row 746: ReqIF.Text
Row 796: ReqIF.Text
Row 880: ReqIF.Text
Row 881: ReqIF.Text
Row 883: ReqIF.Text
Row 893: ReqIF.Text
Row 905: ReqIF.Text
Row 910: ReqIF.Text
Row 911: ReqIF.Text
Row 912: ReqIF.Text
Row 922: ReqIF.Text
Row 923: ReqIF.Text
Row 924: ReqIF.Text
Row 930: ReqIF.Text
Row 941: ReqIF.Text
Row 942: ReqIF.Text
Row 946: ReqIF.Text
Row 986: ReqIF.Text
Row 1028: ReqIF.Text
Row 1091: ReqIF.Text
Row 1095: ReqIF.Text
Row 1122: ReqIF.Text
Row 1251: ReqIF.Text
Row 1256: ReqIF.Text
Row 1257: ReqIF.Text
Row 1262: ReqIF.Text
Row 1263: ReqIF.Text
Row 1264: ReqIF.Text
Row 1279: ReqIF.Text
Row 1376: ReqIF.Text
Row 1377: ReqIF.Text
Row 1378: ReqIF.Text
Row 1453: ReqIF.Text
Row 1478: ReqIF.Text
Row 1523: ReqIF.Text
Row 1543: ReqIF.Text
Row 1556: ReqIF.Text
Row 1579: ReqIF.Text
Row 1587: ReqIF.Text
Row 1588: ReqIF.Text
Row 1589: ReqIF.Text
Row 1590: ReqIF.Text
Row 1644: ReqIF.Text
Row 1645: ReqIF.Text
Row 1656: ReqIF.Text
Row 1683: ReqIF.Text
Row 1716: ReqIF.Text
Row 1718: ReqIF.Text
Row 1719: ReqIF.Text
Row 1721: ReqIF.Text
Row 1722: ReqIF.Text
Row 1742: ReqIF.Text
Row 1743: ReqIF.Text
Row 1744: ReqIF.Text
Row 1745: ReqIF.Text
Row 1746: ReqIF.Text
Row 1747: ReqIF.Text
Row 1825: ReqIF.Text
Row 1850: ReqIF.Text
Row 1853: ReqIF.Text
Row 1891: ReqIF.Text
Row 1994: ReqIF.Text
Row 2007: ReqIF.Text
Row 2011: ReqIF.Text
Row 2080: ReqIF.Text
Row 2170: ReqIF.Text
Row 2188: ReqIF.Text
Row 2189: ReqIF.Text
Row 2191: ReqIF.Text
Row 2192: ReqIF.Text
Row 2353: ReqIF.Text
Row 2415: ReqIF.Text

Rows processed:
Warning text differs -4 HTML tags on row 84
Warning text differs -4 HTML tags on row 84
Warning text differs 2 HTML tags on row 91
Warning text differs 2 HTML tags on row 91
Warning text differs -2 HTML tags on row 118
Warning text differs -2 HTML tags on row 118
Warning text differs 4 HTML tags on row 120
Warning text differs 4 HTML tags on row 120
Warning text differs -36 HTML tags on row 132
Warning text differs -36 HTML tags on row 132
Warning text differs -4 HTML tags on row 147
Warning text differs -4 HTML tags on row 147
Warning text differs 4 HTML tags on row 171
Warning text differs 4 HTML tags on row 171
Warning text differs 4 HTML tags on row 176
Warning text differs 4 HTML tags on row 176
Warning text differs 12 HTML tags on row 243
Warning text differs 12 HTML tags on row 243
Warning text differs -8 HTML tags on row 258
Warning text differs -8 HTML tags on row 258
Warning text differs -4 HTML tags on row 271
Warning text differs -4 HTML tags on row 271
Warning text differs 4 HTML tags on row 319
Warning text differs 4 HTML tags on row 319
Warning text differs 4 HTML tags on row 474
Warning chapter differs 4 HTML tags on row 474
Warning text differs 4 HTML tags on row 474
Warning chapter differs 4 HTML tags on row 474
Warning text differs -4 HTML tags on row 639
Warning text differs -4 HTML tags on row 639
Warning text differs -4 HTML tags on row 716
Warning text differs -4 HTML tags on row 716
AT_EN_AI ReqIF.Text row 741: malformed translated HTML (not written): xmlParseEntityRef: no name, line 1, column 162 (, line 1)
Warning text differs 26 HTML tags on row 743
Warning text differs 26 HTML tags on row 743
Warning text differs 4 HTML tags on row 775
Warning text differs 4 HTML tags on row 775
Warning text differs 4 HTML tags on row 786
Warning text differs 4 HTML tags on row 786
Warning text differs 2 HTML tags on row 796
Warning text differs 2 HTML tags on row 796
Warning text differs 8 HTML tags on row 880
Warning text differs 8 HTML tags on row 880
Warning text differs 8 HTML tags on row 881
Warning text differs 8 HTML tags on row 881
Warning text differs -8 HTML tags on row 912
Warning text differs -8 HTML tags on row 912
Warning text differs 2 HTML tags on row 930
Warning text differs 2 HTML tags on row 930
Warning text differs 4 HTML tags on row 934
Warning text differs 4 HTML tags on row 934
Warning text differs 12 HTML tags on row 981
Warning text differs 12 HTML tags on row 981
Warning text differs 7 HTML tags on row 982
Warning text differs 7 HTML tags on row 982
Warning text differs 4 HTML tags on row 1031
Warning text differs 4 HTML tags on row 1031
Warning text differs 4 HTML tags on row 1107
Warning text differs 4 HTML tags on row 1107
Warning text differs 48 HTML tags on row 1121
Warning text differs 48 HTML tags on row 1121
Warning text differs 2 HTML tags on row 1170
Warning text differs 2 HTML tags on row 1170
Warning chapter differs 4 HTML tags on row 1174
Warning chapter differs 4 HTML tags on row 1174
Warning text differs 12 HTML tags on row 1262
Warning text differs 12 HTML tags on row 1262
Warning text differs -4 HTML tags on row 1263
Warning text differs -4 HTML tags on row 1263
Warning text differs 4 HTML tags on row 1335
Warning text differs 4 HTML tags on row 1335
Warning text differs -4 HTML tags on row 1339
Warning text differs -4 HTML tags on row 1339
Warning text differs -4 HTML tags on row 1386
Warning text differs -4 HTML tags on row 1386
Warning text differs -4 HTML tags on row 1453
Warning text differs -4 HTML tags on row 1453
Warning text differs -2 HTML tags on row 1469
Warning text differs -2 HTML tags on row 1469
AT_EN_AI ReqIF.Text row 1497: malformed translated HTML (not written): StartTag: invalid element name, line 11, column 35 (, line 11)
AT_EN_AI ReqIF.Text row 1534: malformed translated HTML (not written): StartTag: invalid element name, line 11, column 35 (, line 11)
Warning text differs 2 HTML tags on row 1554
Warning text differs 2 HTML tags on row 1554
AT_EN_AI ReqIF.Text row 1559: malformed translated HTML (not written): StartTag: invalid element name, line 1, column 523 (, line 1)
Warning text differs 4 HTML tags on row 1574
Warning text differs 4 HTML tags on row 1574
Warning text differs -16 HTML tags on row 1633
Warning text differs -16 HTML tags on row 1633
Row 1644 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 63817. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1645 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 61068. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1649 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 62119. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1654 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 62039. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1655 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 62039. To increase, visit https://openrouter.ai/settings/credits and add more credits
Warning text differs 4 HTML tags on row 1660
Warning text differs 4 HTML tags on row 1660
Row 1661 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 61405. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1669 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 61322. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1683 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 61322. To increase, visit https://openrouter.ai/settings/credits and add more credits
Warning text differs -16 HTML tags on row 1688
Warning text differs -16 HTML tags on row 1688
Row 1691 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 61068. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1705 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 61068. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1718 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 60059. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1719 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 60059. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1721 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59251. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1722 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59666. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1723 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59251. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1725 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59251. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1727 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59251. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1728 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59251. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1729 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59251. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1730 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59053. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1734 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59053. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1735 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 59053. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1736 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58601. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1737 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58601. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1759 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58601. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1760 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58601. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1765 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58350. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1766 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58350. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1770 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58350. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1771 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58350. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1780 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58350. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1809 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58096. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1824 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58096. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1825 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57827. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1826 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 58096. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1842 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57827. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1851 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57827. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1861 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57591. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1878 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57591. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1891 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57228. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1899 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57430. To increase, visit https://openrouter.ai/settings/credits and add more credits
Warning text differs -4 HTML tags on row 1901
Warning text differs -4 HTML tags on row 1901
Row 1907 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57430. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1908 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57228. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1909 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57083. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1918 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 57083. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1931 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56860. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1932 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56860. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1933 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56860. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1941 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56860. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1942 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56708. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1943 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56708. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1950 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56441. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1956 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56441. To increase, visit https://openrouter.ai/settings/credits and add more credits
Warning text differs -6 HTML tags on row 1957
Warning text differs -6 HTML tags on row 1957
Row 1968 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56441. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1971 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56441. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1978 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56441. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1988 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56441. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 1993 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56327. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2006 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56327. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2011 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55778. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2015 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56013. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2016 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 56013. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2017 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55778. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2018 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55778. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2021 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55778. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2022 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55577. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2023 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55577. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2042 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55577. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2059 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55577. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2079 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55455. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2086 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55455. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2087 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55082. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2090 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55082. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2094 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 55082. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2095 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54899. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2101 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54899. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2123 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54899. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2124 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54616. To increase, visit https://openrouter.ai/settings/credits and add more credits
Warning text differs 4 HTML tags on row 2125
Warning text differs 4 HTML tags on row 2125
Row 2126 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54387. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2127 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54303. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2129 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54303. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2135 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54303. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2136 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54303. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2145 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54069. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2153 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 54069. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2154 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53885. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2156 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53885. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2157 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53885. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2158 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53885. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2162 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53494. To increase, visit https://openrouter.ai/settings/credits and add more credits
Warning chapter differs -4 HTML tags on row 2166
Warning chapter differs -4 HTML tags on row 2166
Row 2168 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53661. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2169 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53494. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2170 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53494. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2181 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 53494. To increase, visit https://openrouter.ai/settings/credits and add more credits
Warning text differs 2 HTML tags on row 2188
Warning text differs 2 HTML tags on row 2188
Row 2189 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52813. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2191 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52813. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2192 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52813. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2193 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52813. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2194 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52813. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2195 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52813. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2242 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52474. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2243 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52474. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2267 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52474. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2278 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 52474. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2298 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51791. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2312 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51791. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2314 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51536. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2315 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51536. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2316 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51536. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2324 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51340. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2332 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51340. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2353 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50775. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2360 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51183. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2386 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 51183. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2390 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50921. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2399 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50775. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2415 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50654. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2420 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50654. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2422 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50654. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2423 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50654. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2431 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50584. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2437 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50584. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2438 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50584. To increase, visit https://openrouter.ai/settings/credits and add more credits
Row 2445 failed VALIDATION: Error: OpenRouter request failed: This request requires more credits, or fewer max_tokens. You requested up to 64000 tokens, but can only afford 50584. To increase, visit https://openrouter.ai/settings/credits and add more credits
Total tokens used: 30964750
2451/2451 rows processed
Error validating translated ReqIF file:
invalid XML syntax: mismatched tag: line 67934, column 194
Saved without XML schema validation. The file may need manual XML repair before re-import.

=== Pipeline operations ===
[OK] source_language: Japanese (auto) · OP_JA
[INFO] pipeline_start: OpenRouter pipeline started for ATEEL_Technical_Standard_41_to_Ch._2_-_Art._31_1.1.2_(1)
[INFO] translate_new_empty: Empty rows: 2451
[INFO] translate_new_changed: Changed rows: 2182
[OK] text_extract: Wrote row plain-text extract: text.txt (1.8s)
2451 rows
[WARNING] style_parse: full style extract is a little over the limit (14375/8000 characters); left intact.
over_by=6375
[WARNING] style_parse: compact style extract is a little over the limit (2655/1500 characters); left intact.
over_by=1155
[WARNING] style_parse: compact_l2 style extract is a little over the limit (1517/800 characters); left intact.
over_by=717
[WARNING] style_terminology: Document glossary truncated from 140 to 50 entries (max 50).
Used for style merge and row translation.
[INFO] style_extract: Style and terminology extracted in separate calls. (52s)
style_tokens=920219, terminology_tokens=308039
[OK] style_extract: Extracted document style and terminology (1228258 tokens).
model=openai/gpt-4.1-mini
[OK] style_merge: LLM-merged document style with ALICe style style guide (full). (33s)
model=openai/gpt-4.1-mini, tokens=8841
[INFO] style_compact: Style guide compaction level (0.0s)
model=openai/gpt-4.1-mini, level=1, target≤7650
[INFO] style_compact: Style guide compaction level
model=openai/gpt-4.1-mini, level=2, target≤3612
[OK] style_compact: Compacted merged style guide (2 levels).
model=openai/gpt-4.1-mini, tokens=10125
[INFO] style_select: Using merged style (ALICe style + document).
[OK] style_select: Using full + full glossary style guide for openai/gpt-4.1-mini (est. 6454/1047576 tokens)
[WARNING] consistency_check: Chunk 32/59: invalid JSON; retrying (1/2). (4m 49s)
Consistency check response is not JSON: Invalid \escape: line 46 column 173 (char 2719)
[INFO] consistency_check: Chunk 32/59: valid JSON after retry 1/2.
[OK] consistency_check: 2451/2451 rows checked. Found 362 problem row(s).
model=openai/gpt-4.1-mini, tokens=629802, chunks=59/59, rows=2451/2451
[OK] consistency_retranslate: 362/362 potential fixes. (21m 15s)
[OK] row_translation: Completed 2451/2451 rows. (2h 52m 56s)
tokens=30964750
[OK] pipeline_end: Translation completed (2451/2451 rows, 30964750 tokens).
Finished at 2026-09-24 10:46:50}}