Is there a way to enforce no line breaks in the middle of CN/JP words?

[enigmaticgale]

I’m working on a vault with information on various Chinese mythological figures and some of their Japanese adaptations. Most of my text is in English since that’s what I speak, but I am including their original names as it’s relevant information. These names are between 2-6 characters in length. I’m running into an issue where, if a name runs up against the end of a line, Obsidian chops it in half instead of bumping the entire name down to the next line. I’ve attached a couple screenshots of this happening:

Is there any way to force Obsidian to not do this/recognise the names as one word instead of a string of separate characters? Playing with my font sizes, line length, and theme fixes it for one note, but messes it up on another. The only thing I could find when I looked were plugins designed to help select single words from Chinese/Japanese sentences instead of the entire sentence when you double click, which isn’t really relevant to my problem.

I know it’s purely a visual issue, but it’s been bothering me a lot. Since it’s just a visual issue and dependent on things like font size and line length, I don’t know if there even is a solution. I would really enjoy not being bothered by it every time I open the vault, though, so I wanted to ask just in case. Thanks in advance for any insight!

[dafontfree]

Obsidian’s renderer treats every CJK character as a legal break point, so it has no way of knowing those characters belong together as one name. The most dependable fix is to wrap each name in a span such as <span class="cjk-name">孫悟空</span> and add a CSS snippet with .cjk-name { white-space: nowrap; }, which pushes the whole name onto the next line as a unit. If you’d rather not tag every name, word-break: keep-all on the editor and reading view stops breaks between CJK characters everywhere, though it will also affect any longer Chinese or Japanese passages you add later. With names of only 2 to 6 characters, the nowrap span is the safer option and behaves the same in Reading view and Live Preview.

[enigmaticgale]

Thank you so much!! You’re a lifesaver, seriously.