Japanese and Korean

Decide what the text is meant to follow

• Which of the two paragraph languages is actually intended?
• Does the finding concern an actual composed line boundary?
• Have the surrounding characters and composition settings been reviewed by a competent reader?

Interpret the example in context

The model records separate supported quote forms and East Asian policy. Japanese prose is not treated as ordinary space-delimited Latin prose for the relevant punctuation-after check. Review the exact supported finding; the registry is not a complete Japanese or Korean editorial certification.

Inspect the current plugin model

These fields describe the built-in plugin defaults. Read Language & rules for the policy actually used in your inspection; a custom team profile can differ. The defaults are not a universal style guide and do not promise equal rule coverage. Expand a specific locale to compare its expectations.

Use the language evidence deliberately

1. Check paragraph-language attributes, intended publication convention and actual active policy.
2. Inspect representative text and read the resolved language and coverage in the panel.
3. Review complete quotations, numeric source values and relevant line boundaries before any edit.
4. Apply intended policy changes and inspect again. Retain intentional source differences and obtain competent language review where needed.

Review the relevant topics

Continue with the current workflow

• 12. Language policy and locale reference
• 24. Typography policy, protected profiles and semantic evidence

Compare two locale models → · Choose a language policy →