Arabic Fonts, English Styles, CJK Typography, and Outlined Math Equations in InDesign
Apply language fonts, inline English character styles, Noto Sans CJK typography and outlined math equations in InDesign, then run guided final QA.
- Nine workflows chain in order: prepare, fonts, English styles, math outlining and transfer, CJK styles and rules, final QA.
- Install Noto Sans CJK SC, TC, JP, or KR before creating CJK styles, and a math font such as STIX Two Math for equations.
- Outlined equations transfer from source to target as vectors; corrections happen in the source, not in the outlines.
- Guided final QA provides checks and optional fixes - it does not replace visual review before delivery.
A localized InDesign document is several typographic systems sharing one layout: the target language's script and fonts, inline English fragments that need their own styling, occasional CJK runs with their own line-breaking law, and — in technical work — math equations that cannot simply reflow into a new font. BLoc InDesign addresses this as nine coordinated workflows on Windows, from document preparation and language-specific fonts through outlined math equations and CJK typography to a guided final QA. This guide explains when each workflow earns its place and how they chain into one production pass.
One document, several typographic systems
The naive approach to a localized InDesign file is to change the font, export, and hope — and hope fails in specific, repeatable ways. Arabic set with a Latin-first font loses shaping quality or falls back inconsistently. Inline English inside an Arabic paragraph inherits the paragraph's styling and looks like a mistake. CJK paragraphs composed with Latin rules break lines at the wrong points and space punctuation incorrectly. Math equations rebuilt in a text font lose their structure entirely — which is why equations get outlined as vector shapes, and why outlining needs a math font to begin with.
Each is a distinct defect class with a distinct fix, which is why a single "make it look right" pass fails and why the nine workflows exist as separate, reviewable steps. Running them separately also produces what a production team needs: reports, summaries, and warnings that say what changed and what still needs eyes.
The nine BLoc InDesign workflows at a glance
| Workflow | What it does | Review output |
|---|---|---|
| 1. Document preparation | Prepares a working document with selectable cleanup tasks | Changes plus a report to review |
| 2. Language-specific fonts | Chooses fonts for a selected language, optionally including digits | Font assignments to verify in the document |
| 3. English character styles | Applies English character styles within a localized document | Styling of inline English to inspect |
| 4. Math equation outlining | Outlines equations using an installed math font | Outlined equations; editable masters retained |
| 5. Equation transfer | Copies matching equations as outlines from source to target document | Matched equations in the target to check |
| 6. CJK style creation | Creates character styles for SC, TC, JP, or KR using installed Noto Sans CJK | Created styles and missing-font warnings |
| 7. CJK style application | Applies the matching CJK character styles | Summary plus warnings for missing styles |
| 8. CJK paragraph setup | Detects CJK paragraphs and applies composer, kinsoku, and mojikumi rules | Warnings for missing resources and text wrapping |
| 9. Guided final QA | Runs a guided document check with optional fixes | Findings and fixes to review visually |
The recommended CJK chain shows how the workflows order themselves: save a working copy, run Global 01 – Prepare Document, then CJK 01 – Create Styles, CJK 02 – Apply Styles, and CJK 03 – Paragraph Setup as needed, and finish with Global 02 – Final QA Check, reviewing each report before moving on. The ordering is not ceremonial — cleanup before styling, styles before paragraph rules — and the same discipline generalizes to non-CJK projects.
Document preparation and cleanup
Preparation is the workflow that makes the others safe: it prepares a working document with selectable cleanup tasks, then hands back the changes and a report to review. Its value is separation — cleanup problems such as legacy overrides and leftover artifacts are fixed before font and style decisions are layered on top, so a later QA finding is a language problem rather than an archaeological one.
Always run preparation on a working copy, never on the only instance of the file: save the copy first and review script reports, fonts, line breaks, and punctuation before delivery. A report listing unexpected changes is a finding, not noise — it usually means the source document carried more baggage than the team knew, better discovered now than after styles are applied on top.
Language fonts, digits, and inline English character styles
The language-font workflow chooses fonts for a selected language, with the option to include digits. A document may want target-language digits or must keep Western digits for technical consistency, and mixed-digit documents are a classic review failure — so decide digit policy once, in the font workflow, instead of improvising per paragraph.
Inline English is the mirror problem: inside a localized paragraph, English fragments — product names, API identifiers, acronyms — inherit surrounding formatting and read as typographic accidents. The English character style workflow applies consistent styling to those runs, so they are governed by a style rather than by accident. Both workflows produce reviewable outcomes: the operator verifies assignments and inspects the styling, and either can be re-run when decisions change.
Outlining math equations and transferring them between documents
Math is the least forgiving content in localization: equations rely on a math font's character inventory and positioning behavior, and rebuilding them in a text font destroys the layout they depend on. The outlining workflow converts equations into outlines — vector shapes — using an installed math font, so the rendered equation travels with the document independent of later font decisions. STIX Two Math is the documented house font, and the font choice is confirmed for your workflow.
The transfer workflow solves the localized-document case: choose a source and target document, and matching equations are copied as outlines into the target, keeping the localized edition's equations identical to the approved source versions instead of re-set and subtly different. Two boundaries apply: the math font must be installed on the machine doing the work, and corrections to an equation happen in the source and are re-transferred, not edited in the outline. The tools run in Windows InDesign with documented checks on InDesign 2025 — confirm compatibility before committing a delivery date.
CJK character styles and paragraph rules: SC, TC, JP, KR
CJK typography follows rules Latin composition does not have, and the workflows separate resource setup from application. Create Styles builds character styles for Simplified Chinese, Traditional Chinese, Japanese, or Korean using the matching installed Noto Sans CJK families — SC, TC, JP, or KR; the fonts must be installed first, because a style pointing at a missing font is a warning in the making. Apply Styles applies the matching styles and returns a summary with warnings for missing styles, resolved before continuing rather than after delivery.
Paragraph Setup detects CJK paragraphs and applies the rules that make CJK text read professionally: the paragraph composer, line-breaking rules (kinsoku, which forbid certain characters from starting or ending a line), and spacing rules (mojikumi, which govern punctuation spacing and stacking). Its warnings cover missing resources and text wrapping — a paragraph composed with the wrong rules looks almost right to non-readers and clearly wrong to the audience that matters. Review the warnings, and inspect mixed-script text, wrapping, and punctuation as part of the pass.
Guided final QA: what the nine checks cover and what they cannot
Global 02 – Final QA Check runs a guided document QA with optional fixes, then expects a visual review of the result. It is the capstone because it is only meaningful after the other workflows: QA on an unprepared document reports archaeology, QA on a prepared, styled document reports language quality. Work through the checks deliberately, choose which fixes to accept, and treat completing the dialog as progress — not as certification; finishing the dialog does not certify typography or layout for delivery.
What remains for humans is what should remain: the aesthetic and contextual judgments. Check the fonts actually applied, line breaks in the target script, punctuation behavior, mixed-script passages, and outlined equations against the source. For teams that hand off to PDF, the typeset result then goes through BLoc PDF QC for the review-and-correction loop described in turning translated PDF reviews into clear DTP corrections, with file preparation and XLIFF exchange covering the stage before typesetting.
Pre-delivery engineering checklist
- Save a working copy and run document preparation cleanup on the copy; review the report before anything else.
- Install the required fonts first: Noto Sans CJK SC, TC, JP, or KR for the CJK languages in scope, and a math font such as STIX Two Math for equations.
- Apply language-specific fonts with an explicit digit policy, and verify the assignments in the document.
- Apply English character styles to inline English runs and inspect representative paragraphs.
- Outline math equations and transfer matching equations from source to target; confirm the outlined results against the source document.
- Create and apply CJK character styles, resolving every missing-font and missing-style warning before proceeding.
- Run CJK paragraph setup and inspect composer, kinsoku, and mojikumi behavior on real paragraphs, including wrapping and punctuation.
- Run the guided final QA, choose fixes deliberately, and complete a visual review — fonts, line breaks, punctuation, mixed-script text — before delivery.
- Confirm your InDesign version (documented checks cover InDesign 2025) and archive the working copy with its reports.
Technical FAQ
Which math font do I need for outlining equations?
The workflow depends on an installed math font; STIX Two Math is the documented house font. Install it on the machine running the workflow and confirm the font choice before a production pass. Equations are outlined so rendering no longer depends on later font decisions, while editable masters are retained in the source.
Do I need the Noto Sans CJK fonts installed before creating styles?
Yes. Style creation for Simplified Chinese, Traditional Chinese, Japanese, and Korean uses the matching installed Noto Sans CJK SC, TC, JP, or KR families. Missing fonts are reported in the apply step's warnings — resolve them before delivery rather than letting substitution decide your typography.
Does completing the final QA dialog certify my document for delivery?
No. The final QA workflow offers guided document checks and optional fixes, and the result still needs a visual review. Completing the dialog does not certify typography or layout; it organizes the mechanical findings so your reviewers spend their time on the judgments machines cannot make.
Which InDesign versions do the tools support?
The tools run in Windows InDesign, with documented checks covering InDesign 2025. Confirm compatibility with your installed version before delivery, and keep the standard pass — working copy, script reports, fonts, line breaks, punctuation — regardless of version.
See the BLoc InDesign tool page for the full workflow list and the interactive walkthrough for a guided tour of the nine steps. For layout adaptation in other Adobe formats, continue with mirroring Illustrator artwork for Arabic RTL layouts, and for the preparation stage that feeds translation, read preparing design and Office files for XLIFF exchange.
Related guides
BLoc InDesign · InDesign layout
Ready to apply this workflow in production?
Prepare localized InDesign documents, apply language and CJK styles, set paragraph rules, run final checks, and handle math equations. Pricing: $10 / month or $100 / year.