Hán Việt vs Pure Vietnamese Terms: A Tech and Finance Register Guide

💡 Vietnamese splits its vocabulary into two layers: Hán Việt (Sino-Vietnamese, derived from Chinese characters) and thuần Việt (native Vietnamese). In technical and financial writing, Hán Việt dominates at 70-90%. Any English, French, or Chinese team localizing into Vietnamese must specify which register their product needs - or risk getting an inconsistent mix of both in the same interface.

What is Hán Việt, and where did it come from?

Vietnamese vocabulary has two main etymological strata. Thuần Việt words are the native Austroasiatic core: everyday objects, basic actions, and kinship terms. Hán Việt (literally "Han-Vietnamese") words were absorbed from Literary Chinese over roughly a thousand years, most intensively during the Tang dynasty through the early 20th century, when Classical Chinese was the formal written language of Vietnamese court and scholarship.

The key feature for localizers: Hán Việt words have systematic phonological correspondences to their Chinese originals. Every Chinese character maps to a specific Sino-Vietnamese reading. This regularity explains why the proportion of Hán Việt rises steeply in formal writing: technical, legal, scientific, and financial texts all draw on the same Classical Chinese vocabulary, with Vietnamese tone marks and phonology applied.

How dominant is Hán Việt in tech and finance writing?

Overall estimates of the Hán Việt share in Vietnamese range from one-third to 60-70% of the lexicon, depending on counting method. The register effect is dramatic: in mathematical writing, studies have found over 84% of terms are Hán Việt compounds. Financial and legal texts show a similar profile. In informal spoken Vietnamese, the proportion falls well below 30%.

For a product team, the practical consequence is clear. If your product is a B2B SaaS platform, a fintech app, or a medical device interface, nearly every key UI label - menu items, field labels, documentation headings - will land on a Hán Việt term when translated by a skilled native specialist. If your product is a casual game or consumer social app, a lighter mix is acceptable and often preferred.

Which tech and finance terms are Hán Việt vs thuần Việt?

The table below shows common terms with their register classification. Use it as a starting checklist when auditing your Vietnamese glossary.

Core finance terms are almost entirely Hán Việt. Tech terms split: foundational computing vocabulary (algorithm, interface, data) is Hán Việt, but interface-layer terms like "software" (phần mềm) and "bug" (lỗi) are thuần Việt. Both registers coexist correctly in one product - the problem arises when they mix inconsistently across screens without a style guide.

Why does this register gap matter specifically for English and French teams?

Chinese-speaking teams have a navigational shortcut: because Hán Việt words derive from Chinese characters, a bilingual terminologist can often predict the correct Vietnamese equivalent by applying phonological rules. From 證券 to chứng khoán, the pattern holds. From 算法 to thuật toán, the same logic applies.

English and French teams have no equivalent shortcut. A translator given an under-specified brief may default to thuần Việt calques (more accessible, sometimes feels informal for B2B), full Hán Việt formalisms (correct for B2B, potentially cold for consumer UI), or an inconsistent mix (the most common outcome). Without a register specification, even experienced translators apply personal judgment - and if multiple translators work on the same file, consistency breaks across screens.

The fix is simple: add four lines to your localization brief. State the register, specify the second-person pronoun set ("bạn" for consumer apps, "Quý khách" for formal B2B), set the dialect baseline (Northern vi-VN for most B2B products), and provide a 30-50 term glossary annotated with register labels.

How do you spec the right register in your localization brief?

A concise register specification removes the single largest source of Vietnamese UI inconsistency for EN and FR source teams. Here is the four-line addition that covers the essentials:

1. Register: "Formal Hán Việt throughout (B2B/finance/medical)" or "Standard mixed register (consumer app, onboarding tooltips may use thuần Việt forms)."
2. Pronoun: "Use 'bạn' (consumer neutral) or 'Quý khách' (formal B2B) for the second person."
3. Dialect baseline: "Northern vi-VN standard unless primary market is Southern Vietnam."
4. Glossary lock: "See attached termbase - 40 core product terms, each tagged Hán Việt / thuần Việt / hybrid. Locked in Trados/memoQ/Crowdin."

If you use a cloud CAT platform: Crowdin and Smartcat support custom glossaries with mandatory review steps for high-stakes strings. Trados Studio and memoQ enforce term locks at the segment level for desktop translation workflows.

What can you handle in-house, and when is a Vietnamese specialist worth it?

In-house is viable for: choosing vi-VN as your locale setting, adding a register paragraph to your translation brief, and running a first MT pass to estimate string count and expansion ratio.

A Vietnamese specialist earns the investment when you need: the initial 30-50 term glossary built against authoritative domain sources (State Bank of Vietnam regulations for finance, WHO guidelines for medical), a full UI LQA pass to catch register inconsistencies introduced in earlier sprints, or regulatory copy where Hán Việt formalisms are legally required, not optional.

Machine translation handles common Hán Việt collocations reliably now. What MT cannot do is judge register fit in context: whether "dữ liệu cá nhân" or "thông tin cá nhân" is the right label for "personal data" depends on your product's legal vs. consumer framing. That judgment, applied consistently across thousands of strings, is where a native Vietnamese specialist pays off. For finance products specifically, the Vietnamese financial translation page covers SBV-aligned terminology and regulatory turnaround.

FAQ

Official Sources

• Wikipedia - Sino-Vietnamese vocabulary - proportion of Hán Việt by register and domain, historical origins, morpheme inventory. Verified Oct 2026.
• W3C i18n - Character encodings: Essential concepts - Vietnamese grapheme clusters and Unicode handling for diacritic-heavy text inputs and displays. Verified Oct 2026.
• W3C i18n - Approaches to line breaking - Vietnamese classified as a syllable-separator language, distinct from word-boundary languages. Verified Oct 2026.
• SEA Tongue - Vietnamese Localization Guide - formal register strategy, dialect baseline, and pronoun selection guidance for software localization. Verified Oct 2026.