w3c / w3c/csswg-drafts

[css-text-4] Dealing with unusual line-break/hyphenation rules

Open
#2,976 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-text-4 i18n-sealreq i18n-tlreq i18n-tracker
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

  1. Breaking Within Words
    https://drafts.csswg.org/css-text-4/#hyphenation

Certain features associated with line-breaking are unusual by western standards, and i'm not sure whether to class them as line-break rules, or specialised hyphenation rules.

Two examples are given in the last section of the following article, Other special rules.

The Javanese example might be closer to what we normally think of as hyphenation: a glyph that only appears when a word is broken, and isn't in the text stream. However, it only occurs in a specific situation.

The Tibetan example relates to situations where a single syllable followed by a shad is wrapped. In my mind, this may be more aligned with line-break rules than hyphenation.

The purpose of this issue is to ask whether anyone has any suggestion about how to treat things of this kind, and whether we should add anything to the CSS spec to either refer to or cover this kind of behaviour.

Contributor guide

Open the contributing guide

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 with section 8, “Breaking Within Words,” in the CSS Text Level 4 draft, then read the linked “Other special rules” article. Compare the Javanese and Tibetan examples and determine whether they belong under line-breaking or hyphenation. Done means the issue has a decided classification and a clear recommendation for whether the CSS specification should address it.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.