Improve line spacing for Korean documents

[eupthere]

I’d like to suggest increasing the line spacing for Korean text across the website.

Current behavior

The current line spacing for Korean content feels too tight. In many cases, the vertical spacing between lines is similar to the horizontal spacing between words, which makes it harder for the eye to naturally track lines of text.

This issue is more noticeable in Korean, probably because of the glyph difference. Some fonts allocate less vertical space for Korean glyphs (because Korean characters don't have descenders like latin alphabet), which can make the default line height feel visually compressed.

Suggested improvement

Increasing the line spacing (line height) would improve readability. For example:

This can be done by adding following CSS rule to styles/markdown.scss

// Korean text needs more line spacing for readability
html[lang="ko"] .rendered-markdown {
  line-height: 1.8;
}

[ksen0]

I support this, though adding some documentation for the difference would be good, as part of docs for translation.

In this case, would bigger line spacing also improve the appearance of Chinese translations cc @lirenjie95 ?

Also, what do you think @doradocodes @Nwakaego-Ego?

(Along with language-specific CSS, here's also a particular regex for Hindi punctuation that would be good to document somewhere that includes technical notes for different locale support - @Divyansh013 @aashishpanthi sharing this with you for visibility, in case it's useful for any proposals on translation contributor docs)

[Nwakaego-Ego]

The repo has a docs/localization_hi.md file for Hindi translators, and issue #1323 is proposing the same for Korean. That pattern makes sense, but as more languages are added, having these files sitting alongside technical overview files in docs/ in the long run could get hard to navigate.
What if we organised translation documentation under a dedicated docs/translation/ folder? Something like:
docs/
translation/
glossary/
localization_hi.md
localization_ko.md
localization_zh.md
language_specification/
hi.md
ko.md
zh.md
localization.md
The glossary/ folder would hold translation glossaries for each language e.g #1323, localization_hi.md...., while the language_specification/ folder would be a separate home for language-specific documentation e.g #1376

Korean needs increased line-height for readability
Hindi needed a specific punctuation regex fix (PR #1156)
Chinese may have the same line spacing need as Korean

None of this is currently documented anywhere a translation contributor would find it before starting work. A dedicated folder would give all of that a permanent home.

[lirenjie95]

Hi @ksen0, from what I know, Chinese is an ideographic writing system rather than a phonetic alphabet (while Korean is actually a phonetic script). Although Chinese characters may look similar to Korean at first glance, each Chinese character can convey its own independent meaning. Adjusting paragraph spacing won’t make much of a noticeable difference visually.

[ksen0]

Thanks for the input everyone.

@eupthere Do you want to make a PR to add line spacing in Korean, or should this be opened to another volunteer?

@Nwakaego-Ego Thanks for the summary an the idea of docs/translation/ - the specific contents of that directory I think should be as simple and flat as possible. There are already many docs in many places. I would propose a README at the top that describes what's in this documentation (Glossary + locale-specific style points + locale-specific technical exceptions and where to find them), and 1 .md file per language with all the above. If that sounds ok, please feel free to make a PR to introduce the reorganization; but if we need to discuss it more then maybe we can create a separate issue (or a draft PR). Do you want to work on that or would you prefer to make it an open task for volunteers?

[Nwakaego-Ego]

@ksen0, I would love to take this on. I will open a draft PR.

[eupthere]

@ksen0 I opened a PR (#1392), as I wanted to fix one more typesetting issue here.

Should I open a seperate PR for 2.0 branch as well? I am not familiar with how those two branches are synced in this repo.

[eupthere]

I just found this Korean translation document on p5.js repository.

Would it make sense to point to it from the README? It's about FES error translation, but also includes great tips and resources about translation.