Field note · Typography
Equal weight,
not equal size.
Most bilingual identities in Cambodia treat Khmer as a translation — set in whatever font is to hand and bolted underneath the real logo. That is not laziness. It is that Khmer quietly breaks four assumptions Latin type lets you hold without noticing you hold them.
- Studio
- MONISM, Phnom Penh
- Words
- Khobi Tang
- Read
- 5 min
A brand needs its Khmer to work in the room it stands in and its Latin to work on the internet it lives on. The usual result is a lockup where one script is designed and the other is placed. You can see it on shopfronts all over Phnom Penh: a confident Latin wordmark, and beneath it a line of Khmer that floats, collides, or has been shrunk until it reads as a footnote to the brand rather than part of it.
Here is what is actually going wrong.
01Khmer has no capital letters
None. Thirty-three consonants and no case distinction anywhere in the script. Which means every move a Latin identity can make out of case has no Khmer counterpart: no all-caps wordmark, no small caps, no Title Case against sentence case, no shouting by capitalising.
If the entire character of your Latin mark comes from being set in capitals — and a great many do — there is simply nothing for the Khmer to match. The equivalence has to be found somewhere else: in weight, in width, in how much of the line the word fills.
Consequence
Decide what carries your brand's voice before you draw the Latin. If the answer is “capitals”, the Khmer can never agree with it.
02The height of a word is a property of the word
Khmer builds consonant clusters by stacking. Between two consonants sits a character called the coeng — Unicode U+17D2 — which has no visual form of its own and instead turns the consonant after it into a reduced subscript shape hanging beneath the first. Many of those subscript forms look substantially different from the full letter, not merely smaller.
Vowel signs then attach in four directions. Some sit above the base, some below, and — the one that surprises Latin designers — three appear to the left of the consonant they belong to, so reading order and drawing order come apart. Five vowel signs are single code points that visually wrap around the base on two sides at once.
Khmer sits on the same alphabetic baseline as Latin, but its subscripts and combining marks extend well past where Latin ascenders and descenders stop. So the bounding box of a Khmer word is not a constant of the typeface. It is a property of that particular word. A lockup tuned until it looks right on one name will break on the next.
03Matching the x-height is matching nothing
The instinct, coming from Latin, is to set the Khmer to the Latin x-height and call it balanced. But there is no x-height in Khmer. There is no lowercase for one to be measured from.
Match by measurement and one of two things happens: the Khmer floats above its own baseline looking undersized, or it grows to look right and its subscripts collide with whatever sits on the line below. What you match instead is optical weight — how much ink the two scripts lay down at the same reading distance.
Consequence
Equal weight, not equal size. It is a judgement made by eye, one lockup at a time, and it does not reduce to a ratio you can reuse.
04There are no spaces between words
Spaces in Khmer separate phrases, not words. Readers are expected to break lines at word boundaries — but nothing in the text marks where those boundaries are. No layout engine can reliably infer them, and stacks are never split, so a Khmer tagline in a browser breaks where the container runs out rather than where the sense does.
Consequence
If the Khmer matters, set its line breaks by hand. Do not let a viewport width make an editorial decision.
05The failure mode is silent
Because the coeng renders nothing, a font missing the shaping tables does not show an error. It shows the two consonants side by side instead of stacked. Still letters. Still looking like writing. Simply wrong — and wrong in a way a designer who does not read Khmer cannot see, and a reader who does will notice instantly.
This is the real reason Khmer gets treated as a translation. Not disrespect — invisibility. Every other part of a design system announces when it is broken. This one doesn't.
So what we actually do
One monogram, and two lockups drawn separately rather than one lockup translated twice — vertical and horizontal, each with its own spacing decided by eye. Khmer given a face chosen for it and a line-height set for the specific word, not inherited from the Latin. Line breaks declared. Clear space measured from the subscripts, not from the baseline.
It takes longer than setting a second line of type. It is the difference between a brand that speaks Khmer and a brand that has been subtitled.
This came out of a forty-page bilingual system for a café in Phnom Penh — delivered complete, never taken to market. The thinking holds either way.
Script mechanics sourced from the W3C Khmer orthography notes and Unicode TN61, not from memory.