w3c / w3c/clreq

Handling long annotations over adjacent characters in Chinese

Open
#124 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

問題/question
Dominant language
HTML
Stars
809
Forks
66
Avg merge
19m
Merged PRs (30d)
1

Description

3.3.4.1 Basic Requirements 基本规则
http://w3c.github.io/clreq/#h-basic-requirements

只要不侵犯最小间距,可允许注文伸展到相邻基字上方。
Annotations are allowed to extend to the top of adjacent base text as long as the minimum spacing is ensured.

Is it possible to get some more detail on how this works? In JLReq annotations can overlap kana or punctuation, and then there are specific distances to be considered, but cannot overlap kanji. It sounds like romanized annotations can overlap adjacent hanzi characters in Chinese as well as punctuation. Is that correct? Are there any limitations (other than the need to separate the annotation by a minimum 1/4em space from adjacent ones)?

CLReq mentions that tracking may need to be adjusted where adjacent annotations are long enough to run into each other. Is this tracking meant to be for all characters on a line/in a paragraph/on a page? Or is it referring to just adding space around the affected characters?

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 CLReq section 3.3.4.1, “Basic Requirements,” and compare its annotation-overlap and tracking guidance with the linked JLReq behavior. Clarify which adjacent Chinese characters or punctuation annotations may overlap, the spacing limitations, and whether tracking applies locally or more broadly; update the specification text once the requirements are agreed.

Written by the indexing model from the issue text.

Assessment

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