KHZ ART

If you are shipping a multilingual Framer site, the translation is the easy half.

The hard half is what happens to the layout afterwards. German runs long and breaks your buttons. Japanese has no spaces and breaks your line endings. Thai has no spaces either and breaks differently again.

We only solved the CJK side of that, because it is the side nobody else has: https://khz-art.com/en/framer-japanese

In Japanese typesetting there is a rule that a line may not begin with a closing bracket, a small kana, or a full stop. Print has followed it for a century. The web ignores it.

The result is the thing you cannot unsee once you have seen it: a single punctuation mark alone at the start of a line, or one character stranded on the last line of a paragraph.

If you are building a Japanese page in Framer, this is what to look for first: https://khz-art.com/en/framer-japanese

One detail decides whether a Japanese page reads expensive or cheap: the quarter-em of space between Japanese characters and Latin ones.

Type has always put it there. Browsers never have. So a line like 2026年のKHZ ARTの映像 comes out jammed, and readers feel it without being able to name it.

It is a small fix and it changes the whole page. Free plugin, no account: https://khz-art.com/en/framer-japanese

Japanese is the language that breaks quietly. You run a translation plugin, the copy comes back correct, and the page looks fine at a glance — but the browser has split a person's name across two lines, and one lonely character is sitting by itself at the bottom of a paragraph.

Nothing in Framer stops that. Japanese has no spaces, so the line breaks land wherever the box happens to end.

We wrote three small plugins for the things that break after translation: line breaking, the quarter-em of air between Japanese and Latin characters, and readings set above a word. The whole problem is written out here, with before and after: https://khz-art.com/en/framer-japanese

Three things a browser will not do with Japanese type.

1. Line breaking. A browser breaks a Japanese line anywhere it likes. Japanese typesetting says a line cannot start with 。or 」and cannot end with 「. Without those rules, the first character of a line is a closing bracket, and every reader sees it.

2. Furigana. The small readings printed above kanji. It is not a font feature. It needs its own markup, and a browser will not add it for you.

3. The space between scripts. Japanese and Latin set side by side need a quarter-em gap. Without it, the words touch — and the page reads as a translation rather than a design.

We built three plugins for these and put every case on one page, before and after, so you can see what actually changes:

https://khz-art.com/en/framer-japanese

Japanese breaks lines wherever it likes. A browser will split a person's name in half, or leave one character alone on the last line, and nothing in Framer stops it.

We wrote three plugins for it — Kumihan for line breaking, Rubi for readings above a word, Waei for the quarter-em between Japanese and Latin — and a template that assumes all three are there.

If you are building the Japanese side of a site, the whole problem is written out here: https://khz-art.com/en/framer-japanese