linebender / linebender/parley

East Asian line breaking rules.

Open
#301 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
736
Forks
120
Avg merge
1d 3h
Merged PRs (30d)
53

Description

In major East Asian languages, particularly Chinese languages, Japanese, and Korean, there are standard rules for line breaking that are expected to be followed.

In Japanese, one subset of these rules is called 禁則処理 [kinsoku shori], and it is standardized in JIS X 4051. It essentially says that there are certain classes of character (usually punctuation, or kana that modify a previous kana to form a single mora e.g. the ョ in ギョ) that are not permitted at the end or the beginning of a line, such that a necessary line break should be moved to a previous or subsequent† non-prohibited character to prevent this.

There are standardized ways for doing something similar with Chinese languages, with some local variation between regions and specific languages.

In Korean, there are again similar rules.

† this may require negative tracking, smooshing characters together, which is common in high quality East Asian typesetting.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the issue's references to Japanese kinsoku shori and JIS X 4051, alongside the stated Chinese and Korean requirements. The payload names no implementation file, entry point, or test, so the work would first need a project-specific line-breaking location and testable scope; done would mean the agreed East Asian rules are handled consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
design, internationalization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.