When Krita 5.3 wraps Chinese, Japanese, Korean, or Ethiopian text unexpectedly, check the paragraph’s Language first, then distinguish Line Break from Word Break. Do not begin with letter spacing: Letter Spacing changes the space between visible character clusters, while the two break controls affect where wrapping may occur. The official Text Properties Docker documentation states that Line Break is mainly for CJK scripts and requires Language to be set, while Word Break controls whether text may break at characters or only at word boundaries.
Diagnosis And Steps
Use this order when the text is editable and is actually wrapping inside a text shape:
- Select the paragraph with the Text Tool and reveal the relevant properties in the Text Properties Docker. Set Language to the intended locale using a valid BCP 47 code, such as a suitable Chinese or Korean locale. If the script cannot be inferred reliably, inspect the Script field as well. Language is not a cosmetic label: Krita documents it as an input to line breaking and other language-sensitive behavior.
- Keep the text, font, text-frame width, font size, and line height unchanged. Confirm that there are no intentional hard returns. This isolates wrapping behavior from a manually inserted line break or a changed font metric.
- Adjust Line Break to compare the available strictness choices. Use this control when the issue concerns the algorithm’s treatment of CJK line breaking. It is a different decision from whether a word may be split.
- Adjust Word Break separately. Use the character-breaking behavior when breaks inside words or clusters are acceptable; use Keep-all when the requirement is to preserve word boundaries. The documentation specifically identifies this control as useful for Korean or Ethiopian text.
- Only after the break behavior is understood should you inspect Letter Spacing. If the text merely looks too loose or too tight without a different wrap point, spacing may be relevant. Changing it to force a line break mixes two separate causes.
Acceptance Worksheet
The following is an author-designed comparison method, not a guarantee of a particular rendering result. Use one fixed text object and record observations rather than assuming that a setting must produce a specified number of lines.
| Case | Fixed sample and width | Language | Line Break | Word Break | Observation to record | Decision |
|---|---|---|---|---|---|---|
| A | Hypothetical Chinese sample: “春风又绿江南岸”,160 px frame | Chinese locale, set for every row | Record the exact option shown in the interface; hold constant | Hold constant | Record the actual wrap boundary | Baseline for this sample; do not infer behavior from an unset Language value |
| B | Same Chinese sample, same frame and text properties | Same Chinese locale | Change only this property; record its exact displayed value | Hold constant | Record the actual boundary and whether punctuation is involved | Compare Line Break only; omit unsupported Loose |
| C | Hypothetical Korean sample: “크리타에서 한글 줄바꿈 확인”,same font and frame within this comparison | Korean locale, set for every row | Record the exact option shown; hold constant | Record the exact displayed value for character breaking | Record whether a word or cluster is divided | Compare Word Break only |
| D | Same Korean sample, same frame and text properties | Same Korean locale | Hold constant | Keep-all | Record whether the break moves to a word boundary or the line becomes longer | Compare with C; prefer if intact words are required |
| E | Hypothetical Ethiopian-script sample: “ሰላም ዓለም”,fixed frame within this comparison | Record the chosen locale; keep it fixed | Record the exact displayed option; hold constant | Record the exact displayed value for character breaking, then Keep-all | Record the observed breaks and word separators | An author-suggested observation, not a documented outcome guarantee |
For each row, save the visible result and the exact property values. The table does not infer a hidden width algorithm, a universal line count, or a guaranteed “correct” break. The official documentation describes the roles of the controls, while this worksheet supplies a repeatable way to compare them.
Limits And Next Step
Krita’s documentation explicitly says that Loose is currently unsupported for Line Break. Do not list Loose as an available repair or treat its absence as a setting that can be enabled through another control. If the required result depends on Loose behavior, choose a supported Line Break option, revise the frame or approved line arrangement, or continue the typography work in an editor whose documented rules meet the requirement.
If setting Language and comparing the two break controls does not explain the result, check whether the text is using a hard line break, whether the selected range inherits different properties, and whether font fallback changes the visible metrics. These are diagnostic possibilities, not claims that the documentation assigns them a particular outcome. If the problem is only visual spacing, review Letter Spacing separately; if the problem is the wrap location, return to Language, Line Break, and Word Break. No local software test was performed for this guide.
Three Short Questions
Should I change Letter Spacing first? No. Change it only when the spacing itself is wrong. It is not the control for choosing word-boundary versus character-boundary wrapping.
Are Line Break and Word Break interchangeable? No. Line Break selects strictness for the line-breaking algorithm and depends on Language. Word Break governs whether breaking at characters is allowed in addition to word-boundary breaks.
Can Loose solve a CJK result that looks too restrictive? Not in the documented Krita 5.3 behavior. The manual marks Loose as unsupported, so it is not an executable fix in this workflow.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.