Re: [clreq] 隔音符号的排版 (#351)

> 根据《汉语拼音方案》第五部分的规定，分词连写时需要根据实际情况添加隔音符号，如西安（Xī’ān）。

According to the fifth rule of Hanyu Pinyin, for words as the base units, apostrophes must be added as per actual conditions, for example, 西安 (Xī’ān).

> NOTE：尽管《汉语拼音方案》称隔音符号仅用在「如果音节的界限发生混淆」的情况，但是根据《现代汉语词典》、《GB/T 38207-2019 中国地理实体通名汉语拼音字母拼写规则标准》等实际操作来看，推荐「凡以 a，o，e开头的非第一音节，在 a，o，e 前宜用隔音符号隔开。」

Note: Even though Hanyu Pinyin states that apostrophes should only be used where there is potential for confusion at word boundaries, according to the Contemporary Chinese Dictionary, _Generic terms of geographical names in China--Chinese phonetic alphabet spelling rules_ (GB/T 38207-2019) and other use cases, it is recommended for any non-first syllables beginning with a, o or e should be separated with an apostrophe.

> 换行规则：
    6.1 分词连写标音时，基文宜尽量按词换行，拼音随基文；当分词连写标音时，且允许基文在词内换行时，拼音依照基文换行位置，按音节分开，并添加连接号，而不能在音节内部拆分；由于罗马标音的文字为西文，换行时添加的连接号宜使用西文连接号（hyphen）；
    6.2：若换行处遇到隔音符号，则应去掉将隔音符号，在前面音节后面加连接号；
    6.3：若换行处本来就有连接号，则在前行行尾加连接号的同时，在下行行首再加连接号。

Line breaking rules:
6.1 For words as the base units with annotations, line breaking of the base text should occur along word boundaries, with the annotations following the base text;  In the event of line breaking of the base text between word boundaries, annotations should follow the base text with the addition of a connector mark, the break must occur at the syllable boundary and not between syllables; As the romanized annotations are written in Western text, the connector mark used for the line break should be a hyphen
6.2 If an apostrophe is present at the line break, the apostrophe should be removed and a connector mark should be added behind the preceding syllable
6.3 If there is already a connector mark present at the line break, the connecting mark should appear at the end of the preceding line as well as at the start of the next line

---
@ryukeikun 添加的图案有caption吗？

-- 
GitHub Notification of comment by huijing
Please view or discuss this issue at https://github.com/w3c/clreq/issues/351#issuecomment-860512213 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 14 June 2021 08:49:17 UTC