The One Most Important Thing in Vietnamese Patent Translation
If we had to name a single priority, it is this: Preserve the claimed scope and its technical support/enablement exactly as in the source—do not broaden or narrow it. Every translation choice—terminology, claim syntax, numbers and units—must serve this goal.
1) Why “scope + support” is paramount
- Legal impact: scope defines rights. Loose wording can cause impermissible broadening or harmful narrowing.
- Enablement: the description must let a PHOSITA carry out the invention. Misrendered passages jeopardize feasibility.
- Examination reality: examiners cross-check description–drawings–claims; small inconsistencies trigger office actions.
2) Five pillars to keep scope intact
(A) Claims discipline
- comprising → “bao gồm” (open), consisting of → “gồm” (closed).
- configured/adapted/operable to → “được cấu hình/được thiết kế/khả dĩ để …” (avoid purpose-like “nhằm”).
- List with semicolons + line breaks; do not merge/split clauses.
- Preserve dependency, numbering, and cross-references exactly.
(B) Terminology consistency
- One concept = one term across description–claims–drawings.
- Choose by industry context (e.g., “cấu hình” for electronics; “kết cấu/tạo hình” for mechanics; IUPAC for chemistry).
(C) Numbers, units, symbols
- SI units; keep symbols (≤, ≥, ±, Δ).
- Decimal comma in Vietnamese: EN
2.5 cm → VI 2,5 cm.
- Ranges with en‑dash:
5–10%. No “rounding” or inferred scope changes.
(D) Drawings & references
- Preserve FIG. labels and reference numerals exactly; in text you may say “Hình X” but keep a 1‑to‑1 mapping.
- PattransVN Format 2.0 for drawing pages: i/N header, centered, 16 pt (e.g., 1/7, 2/7 …).
(E) Filing format (file‑ready)
- A4, 2 cm margins; Times New Roman 14 pt, 1.5 line spacing, justified, 1 cm first‑line indent.
- Order: Technical Field → Background → Summary → Brief Description of Drawings → Detailed Description → CLAIMS → ABSTRACT (last two in ALL CAPS, each on a new page).
3) A scope‑locking workflow
- Start with claims: mark essential elements, ranges, and conditions.
- Decide “difficult pairs” early (configured/adapted; range; at least one of…).
- Translate description with claims in view; stabilize terms as they appear.
- Technical review: check numerals, schematics, equations; verify each claim feature has support.
- Legal & linguistic review: comprising/consisting; listing syntax; “at least one of …”.
- Format check: layout, numbering, embedded fonts; decimal comma (
2,5 not 2.5).
- Final scope check: read claims → back to description; ensure every claim feature is backed.
4) Small mistakes with big costs
- Rendering comprising as “gồm” (closed) → scope shrink.
- Translating “configured to” as “nhằm” → purpose replaces structural capability.
- Numeric drift (2.5 ↔ 2,5; unit changes) → misinterpreted magnitudes.
- Broken mapping between “Hình” and FIG./numerals.
- Term inconsistency (multiple labels for one concept).
- Over‑editing (adding advantages not in the source).
5) Quick pre‑filing checklist (PattransVN)
- Claims: correct open/closed terms; dependencies clear; no scope alteration.
- Terminology consistent across description–claims–drawings.
- SI units; 2,5 instead of 2.5 in Vietnamese;
5–10%; symbols intact.
- Drawings: FIG./numerals 1‑to‑1 with text; drawing pages show i/N header (center, 16 pt) if applied.
- Format: A4; TNR 14 pt; 1.5; justified; 1 cm indent; CLAIMS/ABSTRACT in ALL CAPS on new pages.
- PDF with embedded fonts; Vietnamese diacritics render correctly.
Conclusion: “Right scope, full support” is the fulcrum of Vietnamese patent translation. With disciplined claims wording, context‑aware terminology, precise numbers/units, tight drawing mapping, and compliant formatting, your translation stays legally safe, examiner‑friendly, and file‑ready.