CJK Fonts in InDesign: Chinese, Japanese and Korean

A translated heading can fit its frame and still look wrong: one shared Han character may appear in a Chinese form inside a Japanese paragraph, while a missing font silently changes the look of the rest of the line. InDesign CJK setup needs more than a font swap because glyph selection, language tagging and line composition all affect the finished page.

The practical goal is to separate those problems. First confirm the script and locale, then select and test fonts, set the composition rules, and proof the output in context. The steps below help translation teams, designers and production editors decide when to handle setup in-house and when to bring in a CJK-capable typesetter.

What the translated InDesign file needs¶

CJK means Chinese, Japanese and Korean, but the abbreviation can hide important differences. Chinese and Japanese both use Han ideographs; modern Korean is written almost entirely in Hangul, a script built from consonant and vowel jamo. Chinese characters occur mostly in older and traditional Korean literary materials, not ordinary modern Korean text. Unicode explains this distinction in its FAQ on Chinese and Japanese.

A layout handoff should identify the target language and locale, not just say “CJK.” Simplified Chinese, traditional Chinese, Japanese and Korean are not interchangeable typography settings. Unicode describes four broad East Asian glyph conventions: traditional Chinese, simplified Chinese, Japanese and Korean. The same encoded Han character can be drawn differently under those conventions.

That distinction matters in a translated document because character encoding and glyph design are separate things. Unicode encodes characters, not their specific shapes. A font can display the right character code while drawing a shape that looks unfamiliar to the intended readers. Unicode advises using a font intended for Japanese when setting Japanese text, rather than assuming that a Chinese font will provide the preferred Japanese form.

A useful handoff brief names the language and region, identifies the source file and output format, and states who will approve the final typography. Add the target font family if the client or brand guide specifies one. If no font is specified, ask whether the client expects a particular regional design or has an approved Pan-CJK font.

As Unicode puts it: “Unicode is designed to encode scripts and their characters, not their specific shapes, or glyphs.”

That sentence explains why “the characters are there” is not a complete quality check. A glyph can be present and still be the wrong regional form for the document.

For agency work, the scope also needs to distinguish translation from typesetting. A translated IDML or editable InDesign file may preserve structure, but it does not by itself prove that the target font has complete coverage or that line endings follow the target language’s conventions. Agree on whether the deliverable includes font setup, composition, PDF export and visual review.

A useful first-pass checklist:

The table is a production checklist, not a promise that every file needs a full redesign. A short label inserted into an otherwise finished layout can need only a targeted glyph and fit check. A document with recurring text, multiple fonts or vertical Japanese composition needs a more deliberate preflight.

For broader planning, compare how different file types affect production in InDesign vs Word for multilingual layout. If the source is a PDF rather than an editable layout, see how to translate a PDF without the InDesign source file.

Choose a font by locale and coverage, not by its name¶

A font-family label can suggest language coverage without proving that the font contains every glyph in the translation or uses the intended regional forms. Check the actual document text. A font that works for a familiar sample may still fail on a rare name, a technical term or punctuation introduced during translation.

Start by identifying the language and script in the translated copy. Chinese text usually needs a font appropriate to simplified or traditional Chinese, according to the project. Japanese text should use a font intended for Japanese glyph conventions. Korean body copy normally needs reliable Hangul support; Han characters may still appear in older, literary or specialist material. Unicode notes that one Han character alone generally cannot identify whether a passage is Chinese, Japanese or Korean. Context and language-level clues matter.

Unicode lists Pan-CJK fonts as one option for work that spans regional conventions. Such fonts can carry more than one glyph form for the same encoded character. Its examples include Noto Sans CJK, Noto Serif CJK, Source Han Mono, Source Han Sans and Source Han Serif. Check the current font release and the language-specific font files before production; the list is a starting point, not a guarantee about a particular installed file.

A practical font check has several parts:

1. Make a representative specimen. Copy real translated content from the file, including headings, names, punctuation, numbers and any unusual characters. Don’t test only a short generic sample.
2. Apply the intended font and style. Test the actual regular, bold, italic or other styles used in the layout. A family can have different coverage across its styles or files.
3. Look for missing glyphs and substitutions. Inspect the InDesign document and compare the result with the font and language requirements. A substituted glyph may look plausible at a glance.
4. Review regional forms. Ask a language reviewer to flag characters that look unfamiliar for the target locale. The underlying character can be correct even when the visible form is not.
5. Check the exported PDF. Proof the file that will be delivered, not only the editable view. Confirm that text remains legible and that the appearance matches the approved specimen.

A common production puzzle is a character that displays, but looks wrong. That is not automatically an encoding error. Unicode explains that a missing preferred regional glyph can be a font selection or coverage issue; a rare kanji, for example, may display in an undesired regional form if the font doesn’t provide the preferred one.

Google Fonts maintains a CJK typesetting guide that can help teams compare type design across Chinese, Japanese and Korean. Use locale-appropriate specimens and inspect punctuation and Latin-CJK mixing. Don’t approve a typeface based only on its name or on one attractive sample.

Unicode advises Japanese users to choose “a CJK font intended for Japanese” in its Chinese and Japanese FAQ.

The practical implication is simple: a font that supports Chinese isn’t automatically the right Japanese font. If the document has a client-mandated family, test its actual coverage and appearance before applying it throughout the file.

What if the Character panel doesn’t list the language?¶

Language assignment and glyph display are related but separate checks. An Adobe Community user asked why Chinese or Japanese wasn’t available in InDesign’s Character panel language list in a 2022 discussion. Another user asked how to type Japanese characters in InDesign for an English-to-Japanese translation in a 2019 discussion. Those posts illustrate practical workflow questions; they are not current product documentation.

If a language option is missing, don’t infer that the font cannot display the script. Check the installed InDesign edition and available language features, then test the document’s font coverage separately. If a paragraph can display characters but has no suitable language setting, the team still needs to validate the composition behavior rather than treating the visible text as proof that setup is complete.

For agencies passing files between production teams, record the InDesign version, font files and language settings that the receiving team needs. The checklist in what to send when an IDML has missing fonts can help make that handoff explicit.

Select the composition setup and review the line breaks¶

A composer determines how text fits inside a frame. For CJK text, the important question isn’t simply whether the paragraph fills the available space. The composition rules need to suit the language, punctuation and design.

Unicode’s line-breaking algorithm identifies possible places where a line can break. The software still needs to choose actual breaks based on the available line width and display context. Unicode’s UAX #14 also notes that behavior can vary by implementation and local or stylistic preference. A generic wrap pattern isn’t automatically acceptable for every language or publication.

Japanese text typically wraps at individual characters in a mora-based pattern, rather than only at spaces as Latin text often does. A mora is a unit used to describe the timing of spoken Japanese. The W3C overview of line breaking notes that Japanese wrapping is mora-based and that a line can break within a spoken sequence such as きょう. That does not mean any break is visually acceptable: punctuation and other line-start or line-end restrictions still need review.

Korean text has a different choice. Modern Korean uses spaces between words, and text may wrap by whole words or by syllable. W3C describes syllable-based wrapping as common in fully justified text, while ragged-right paragraphs often wrap by whole words, depending on author preference. The design and editorial brief should say which behavior is wanted.

A production workflow should therefore separate the composer setting from the proofing decision:

• Choose the language-appropriate InDesign composition options available in the installed setup.
• Apply the settings consistently through paragraph styles where possible, rather than fixing isolated paragraphs by hand.
• Inspect the first and last characters on each line, especially around punctuation.
• Review headings, captions, narrow columns and table cells separately from body copy.
• Ask a language reviewer to approve unusual breaks and any justified text.

Japanese kinsoku rules describe restrictions on punctuation at line beginnings and endings. The exact behavior depends on the composition setup, so don’t assume that a paragraph that looks evenly spaced has correct kinsoku handling. Check punctuation around brackets, quotation marks and sentence marks in the actual page proof.

W3C characterizes Japanese as “mora-based wrapping” in its line-breaking overview.

That distinction matters when a layout team imports text from a workflow designed around Latin spaces. A Japanese paragraph can have valid breaks that don’t align with a word-by-word model, but the typesetter still needs to apply the publication’s rules and check the resulting line endings.

The same proofing principle applies to Korean. A ragged-right paragraph with whole-word wrapping may be the intended choice; a fully justified paragraph may use syllable-based breaks. Don’t “correct” a line by inserting arbitrary spaces or breaks until the language reviewer has checked the style.

For a deeper explanation of punctuation and line-breaking mechanics, use the guide to CJK line breaking in translated documents. Japanese text set vertically brings additional constraints, covered in vertical Japanese text and layout challenges.

Compare production options before the file reaches final layout¶

The right workflow depends on the source material, the skills available and the type of output the client needs. A translation team that can edit InDesign and review CJK typography can handle a direct layout workflow. A team without CJK composition experience may want a specialist typesetter to take responsibility for font and line-break review. An online document workflow can help with text extraction or an editable handoff, but it doesn’t replace final InDesign composition.

An in-house workflow can be efficient when the source file is structured, the target language is familiar to the team and the client has clear font requirements. Build time for font checks and proofreading into the estimate. A paragraph that overflows after translation may need reflow, but reflow alone doesn’t reveal whether the glyph shapes are regionally appropriate.

A freelance specialist can help when the job includes Japanese vertical text, extensive CJK copy, complex tables or a font setup the internal team hasn’t handled. Give the typesetter the source file, translated text, locale, font rules and the desired output. Ask them to identify any missing font files or unsupported characters before they start detailed page adjustments.

A document workflow can be useful when the team needs a structured editable file rather than text pasted into a blank document. For example, ChatsControl can return an InDesign-oriented translation as IDML with threaded text, real tables, paragraph styles and pictures. The IDML doesn’t include fonts, so the receiving designer still needs to identify and install the required fonts, verify CJK coverage and proof the final layout. The translation file is a handoff aid, not a substitute for language-specific typesetting.

A separate capability matters during review: a bilingual side-by-side view can help a translator compare source and translated text while checking names, terminology and omissions. That comparison helps with text review, but it doesn’t judge whether a Japanese glyph looks regionally appropriate or whether a Korean line break matches the layout brief. Keep visual proofing in the production workflow.

The choice isn’t always one option for the entire project. An agency might translate and check the text internally, then send only the final composition pass to a CJK typesetter. A small document might need no specialist involvement if a qualified reviewer can approve the language, font and PDF. Decide based on the actual text and risk, not simply on the presence of CJK characters.

Step-by-step: set up and proof the translated file¶

A repeatable workflow gives the translator, designer and reviewer clear responsibilities. Use the sequence below before approving a translated InDesign document.

1. Confirm the language and locale. Write down whether the copy is simplified Chinese, traditional Chinese, Japanese or Korean. Note any mixed-language sections and whether Japanese text is horizontal or vertical.
2. Inspect the source layout. Identify paragraph styles, text frames, tables, captions, repeated labels and any overset text. Record which elements are translated and which must remain unchanged.
3. Confirm fonts and availability. Ask the client or design lead for approved families and the files needed by the production team. Test representative translated text, including names and unusual characters, before formatting the whole document.
4. Set language and composition behavior. Apply the available language and composer settings to the right paragraph styles. Choose the wrapping approach according to the language and layout brief.
5. Place or import the translated content. Keep text in the appropriate frames and styles. Avoid solving every overflow with manual line breaks before the composition rules are set.
6. Review the layout by element. Check body paragraphs, headings, footnotes, tables, narrow frames, punctuation and Latin-CJK mixtures. Ask a language reviewer to assess regional glyph forms and questionable breaks.
7. Export and inspect the proof. Review the PDF that will go to the client or printer. Confirm font appearance, page flow, clipping, missing glyphs and final line endings before delivery.

The sequence is deliberately conservative. Font choice comes before detailed line adjustment because changing a font after manual composition can alter widths and break previously approved lines. Language and paragraph settings come before one-off fixes because inconsistent settings can make adjacent paragraphs behave differently.

The handoff can be kept compact. Attach the translated text, font list, target locale, source file and a note identifying who approves language and who approves layout. If the team uses an IDML exchange, include the InDesign version and any missing-font warnings. A designer shouldn’t have to guess whether a Chinese-looking glyph in a Japanese paragraph was intentional.

ChatsControl’s translation brief can carry domain, audience, tone and preferred terminology through its translation workflow. That can help keep names and terms consistent before the text reaches InDesign. The brief doesn’t select a CJK font or decide line breaks, so the typesetting and visual proof remain separate checks.

For more on the full file exchange, see a safe InDesign IDML round-trip workflow. A structured handoff makes it easier to tell whether an issue came from the source file, the translation or the final layout stage.

Pitfalls: what a clean-looking page can hide¶

A page can look finished while still carrying problems that only appear under review or after the file moves to another workstation. The safest approach is to name each risk and test for it directly.

A shared Han character looks subtly wrong. The character may be encoded correctly while a font supplies a glyph form associated with another regional convention. Compare the character with a locale-appropriate specimen and ask a language reviewer to confirm it. Unicode notes that rare kanji can show an undesired regional glyph when a font lacks the preferred form. Treat the problem as a font coverage or selection question before blaming the text encoding.

The font is installed, but the preferred style isn’t available. A font-family name doesn’t prove that every style used in the layout has the same glyph coverage. Check the actual family files used for regular and bold text, and review the exported PDF. A substitution can change the visual weight or the shape of characters even when the paragraph still fits.

A missing language option gets mistaken for missing glyph support. InDesign’s language list and the font’s character coverage answer different questions. The Adobe Community discussions from 2019 and 2022 show that users have asked about Japanese input and Chinese or Japanese language options, but those questions aren’t product documentation. Check the installed setup and the actual font separately.

Latin spaces are used to force Japanese wrapping. Japanese typically wraps at individual characters in a mora-based pattern. Inserting spaces or manual breaks to imitate English word wrapping can create awkward spacing and make future edits fragile. Set the appropriate composition behavior, then make only deliberate, reviewed adjustments.

Korean wrapping is treated as one fixed rule. Korean text has spaces between words, but line wrapping can happen by whole word or by syllable. The preferred choice depends on the paragraph and design. Specify the style in the brief rather than assuming that every Korean paragraph should wrap the same way.

The PDF is proofed only for overflow. A text frame without overset copy can still have unsuitable glyph forms, punctuation at an awkward line edge or inconsistent font substitution. Review the page as a language artifact, not just as a container that holds all the text.

A converted file is treated as print-ready. An editable IDML can preserve document structure and still require font installation, composition setup and proofing. If fonts aren’t included in the handoff, the receiving team must identify them rather than accepting substitutions by default.

The character alone is used to identify the language. Unicode cautions that a Han character by itself generally can’t establish whether text is Chinese, Japanese or Korean. Use the document context, language metadata and a reliable review process. A font picker shouldn’t have to infer the locale from one shared character.

The failure pattern is often a chain: the brief says only “CJK,” the wrong regional font gets applied, a designer adjusts line breaks manually, and the PDF then looks tidy but fails language review. A precise locale brief and a specimen check interrupt that chain early.

Before sign-off, ask the reviewer to confirm four things: the intended language is clear, the font forms look right for that locale, line breaks and punctuation suit the composition, and the final PDF matches the approved InDesign file. That check is more useful than a general “looks okay” note.

W3C notes that Korean authors can choose between two wrapping approaches in its line-breaking overview: “Korean is unusual in that words in modern hangul text are normally separated by spaces, but the writing system allows content authors to choose one of two ways for that text to be wrapped.”

For production teams, the quote is a reminder to put the wrapping decision in the brief. A reviewer can’t judge a layout against a rule that the project never selected.

FAQ¶

Which InDesign composer should I use for Japanese translated text?¶

Use a Japanese-capable composition setup when the installed InDesign edition and font support it, then inspect the actual line breaks and punctuation. Unicode and W3C describe Japanese wrapping as mora-based, not ordinary Latin word wrapping.

Why do Chinese characters look different in Japanese or Korean fonts in InDesign?¶

Unicode characters don’t prescribe one glyph shape. Fonts can draw the same Han character according to traditional Chinese, simplified Chinese, Japanese or Korean conventions.

How do I check whether an InDesign font supports all translated CJK characters?¶

Test the actual translated text in the chosen font, inspect missing-glyph warnings and substitutions, and review the exported PDF. A family name alone can’t prove complete character and regional-glyph coverage.

Do I need a CJK version of InDesign to typeset Chinese, Japanese, or Korean?¶

Not every workflow requires a separate regional edition, but language-specific composition features and font availability can differ. Check the installed edition, the required composer options and the recipient’s InDesign setup.

How should I proof line breaks in an InDesign CJK translation?¶

Proof each target-language paragraph in context, paying particular attention to punctuation, Japanese kinsoku restrictions, Korean word or syllable wrapping, and Latin text mixed with CJK characters.

Can I use one Pan-CJK font for Chinese, Japanese and Korean?¶

A Pan-CJK font can include glyph forms for multiple regional conventions, but you still need to confirm that the correct language-specific forms are selected and that every required character is covered.

Does translating an InDesign file guarantee that the final layout is ready to print?¶

No. Translation and file conversion don’t replace font checks, target-language composition, editorial review or final PDF proofing. The production team still needs to verify the exported pages.