CJK typography verification set

A localization owner runs this before a Japan or Korea launch. The worry is line breaking and font fallback on a card that already has a lot of type. You need to see what the exported image actually does with Japanese and Korean, using the fonts that will ship.

This is a check before those locales go out. You are not making a new campaign. You are proving a text-heavy artboard you already have can hold CJK type. The fonts have to be the ones in _fonts/, because those are the fonts export embeds.

The job is a small set of PNGs from that artboard, once with Japanese data and once with Korean data. You look at line breaks. You look at fallback. You do that before the launch, not after a card has already gone out.

Give Lerret a React component under .lerret/ and optional data. export writes a PNG. Same component, data swapped. Fonts in _fonts/ are embedded at export. There is no batch product, no queue, no orchestrator.

The component is any text-heavy artboard you already have. This case does not add a new file. You reuse a card that has enough type to show wrapping and fallback. A title-only tile will not tell you much. A card with a headline, a body, and a line of small print will.

The data is locales/ja.json and locales/ko.json. Two files, two runs over the same artboard. Japanese first, then Korean, or the other way around. That is bulk pattern 1: re-run export with a different --data file each time. Same component, new values, new images. --data applies to the run and is never written back into .lerret/.

The images are PNGs used to check line breaking and font fallback. Line breaking is whether Japanese and Korean wrap where you expect. Font fallback is whether a missing glyph silently swaps to another face. You review both on the PNG, not in a browser preview.

Fonts in _fonts/ are embedded at export, so what you review is exactly what ships. There is no “it looked fine on my machine” font substitution. The PNG is the record you take into the review.

npx @lerret/cli@latest export --data locales/ja.json

Then the same command with locales/ko.json.

Start a project with npx create-lerret@latest. More in the use cases index.