Two designs, not one translation

A bilingual site is two designs wearing the same layout, and the layout is usually drawn for the shorter language first.

Georgian sets wider than Latin at the same size. A headline that fits one line in English arrives a third longer, and a line that was a neat two-liner under a service name becomes three. None of that is a font problem. It is a measurement that was taken once, in one language, and never taken again.

Then there is case. Georgian has no capitals to fall back on, so emphasis that leans on uppercase — a nav item, a button, a small label — has nothing to do in the second language. Mtavruli exists, but it is a mode with its own voice, not a synonym for bold.

And the words move. A verb that ends the English sentence can land in the middle of the Georgian one, which matters the moment a line is split across two styled spans, or a number sits inside a sentence with a unit after it.

The practical answer is unglamorous. Build every fixed-size box in the longer language and check the shorter one second. Keep a real sentence of each language in the file while designing, rather than a placeholder that is always the wrong width.