Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

直立的标点符号 #519

Open
xfq opened this issue Feb 10, 2023 · 1 comment
Open

直立的标点符号 #519

xfq opened this issue Feb 10, 2023 · 1 comment
Labels
i:punctuation_etc Phrase & section boundaries i:writing_mode Writing mode

Comments

@xfq
Copy link
Member

xfq commented Feb 10, 2023

https://www.w3.org/TR/clreq/#n022

Unicode编码中有如U+FE41 PRESENTATION FORM FOR VERTICAL LEFT CORNER BRACKET等直立的符号,但作者不适宜直接使用该符号,而是通过其他机制替代使用。

几点建议:

  1. 可以和上文一样,让读者知道这个符号长什么样,即用U+FE41 PRESENTATION FORM FOR VERTICAL LEFT CORNER BRACKET [﹁]的方式来体现
  2. 「作者」可能会被误解为本文档的作者,可以考虑换一个词
  3. 这里没有提到「直排」,可以明确提一下
  4. 「而是通过其他机制」可以考虑改为「应通过其他机制」
@ryukeikun
Copy link
Contributor

ryukeikun commented Feb 21, 2023

这段行文比较随意,需要修改:

  1. 讨论的对象,并不是U+FE41 这一个字符,而至少要包括「竖排字形」区块里 U+FE10U+FE1F以及「CJK兼容字形」区块里 U+FE30U+FE4F这十几个名称带有 PRESENTATION FORM FOR VERTICAL... 的标点

  2. 这属于 Unicode 即编码范围的问题,但本文档的确有必要提一下。Unicode 的《核心规范》对此已经由清晰、准确的描述,可以考虑引用或者适当改写即可。

CJK vertical forms are compatibility characters encoded for compatibility with legacy implementations that encode these characters explicitly when Chinese text is being set in vertical rather than horizontal lines. The preferred Unicode approach to representation of such text is to simply use the nominal characters that correspond to these vertical variants. Then, at display time, the appropriate glyph is selected according to the line orientation.

@xfq xfq added i:writing_mode Writing mode i:punctuation_etc Phrase & section boundaries labels Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i:punctuation_etc Phrase & section boundaries i:writing_mode Writing mode
Projects
None yet
Development

No branches or pull requests

2 participants