Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

間隔號採用 katakana middle dot #43

Closed
hfhchan opened this issue May 13, 2016 · 4 comments
Closed

間隔號採用 katakana middle dot #43

hfhchan opened this issue May 13, 2016 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@hfhchan
Copy link

hfhchan commented May 13, 2016

Unicode 的 middle dot 與 hyphenation point 都是半形,但 CNS11643 與 HKSCS 分別將後者與前者訂為全形,但字體一於少理。

建議一律改用 U+30FB katakana middle dot。在任何支援該字的字體,均顯視為全形。

@sparanoid sparanoid self-assigned this Dec 22, 2016
@sparanoid sparanoid added the enhancement New feature or request label Dec 22, 2016
@sparanoid
Copy link
Owner

感覺一律使用 katakana middle dot 這種「用日文標點強制全形」的做法有點「矯枉過正」了,可能需要一個更好的解決方案

@hfhchan
Copy link
Author

hfhchan commented Dec 22, 2016

In the end of 2015, Ministry of Education Taiwan hold several meetings to
publish new version of "Handbook of Punctuations". The new version will add
Unicode code points to punctuations. We have a proposal to use U+30FB for
separation mark, encourage font foundries to include this glyph in Traditional
Chinese font, and input method developers to map to it.

請參見 http://www.unicode.org/review/pri316/

@xfq
Copy link

xfq commented Oct 24, 2021

供参考:在W3C的中文排版需求里,这个码位目前是不推荐使用的。

@lumynou5
Copy link

從語義(不是中文標點)來看有點怪,但為了排版維持全形可能可以接受。

Repository owner locked and limited conversation to collaborators Jul 27, 2023
@sparanoid sparanoid converted this issue into discussion #196 Jul 27, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants