w3c / w3c/clreq

行首行尾禁则和目前的CSS/Unicode的不同

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

Nobody has claimed this yet.

i:line_breaking
Dominant language
HTML
Stars
809
Forks
66
Avg merge
19m
Merged PRs (30d)
1

Description

目前的CSS标准(以及Unicode)包含了一些CLReq的行首行尾禁则没有提到的内容,如:

  • 如果书写系统是中文或日文,在normalloose时允许在〜 (U+301C)゠ (U+30A0)之前断行,其他情况下禁止。

  • 如果前一个字符属于表意文字,在loose时允许在‐ (U+2010)– (U+2013)之前断行,其他情况下禁止。


  • 如果书写系统是中文或日文,在loose时允许在某些标点符号之前断行:
    • ・ (U+30FB)
    • : (U+FF1A)
    • ; (U+FF1B)
    • ・ (U+FF65)
    • ‼ (U+203C)
    • ⁇ (U+2047)
    • ⁈ (U+2048)
    • ⁉ (U+2049)
    • ! (U+FF01)
    • ? (U+FF1F)
    • 具有 Unicode 换行类 PO(数字后缀)和东亚宽度属性为AmbiguousFullwidthWide的字符,如:
      • ‰ (U+2030)℃ (U+2103)% (U+FF05)
    • 具有 Unicode 换行类 PR(数字前缀)和东亚宽度属性为AmbiguousFullwidthWide的字符,如:
      • ¥ (U+20AC)№ (U+2116)$ (U+FF04)

其他情况下禁止。


另外,CSS里没有对应CLReq中「GB法」的规则。

我们需要讨论一下这些规则是否合理,是否需要修订需求文档或者CSS标准。

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 the CSS Text line-break specification and Unicode TR35 links cited in the issue, then compare their rules with the CLReq line-head and line-end prohibitions. Determine whether the listed differences and the missing GB rule should change the requirements document or be raised against the CSS standard; done requires a documented decision on the proposed rules.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation, internationalization
Issue type
Documentation
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.