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

Inaccuracy regarding modern deprecation of "Proper noun marks" #505

Closed
ronaldtse opened this issue Nov 22, 2022 · 1 comment · Fixed by #508
Closed

Inaccuracy regarding modern deprecation of "Proper noun marks" #505

ronaldtse opened this issue Nov 22, 2022 · 1 comment · Fixed by #508
Assignees

Comments

@ronaldtse
Copy link

The current draft states:

U+FF3F FULLWIDTH LOW LINE [_] is positioned underneath proper nouns such as a person's name, the name of a place, etc. As with book title mark type A (wavy low lines), proper noun marks are rarely used in modern publications, but they can still be seen in some textbooks and ancient publications.

This paragraph contains two inaccuracies:

  1. "proper noun marks are rarely used in modern publications". I'm not sure how this text was accepted. The usage of the proper noun underline is extremely common in modern publications in Hong Kong. It goes without saying that academic, reference and education titles consider the proper noun underline a didactic requirement.

  2. "they can still be seen in ... ancient publications". "Ancient publications" presumably means books published before the Republic of China was established, i.e. 1911. Books published before 1911 are typically not published with modern punctuation marks. The proper noun underline is considered a modern punctuation mark, resulting from the RoC Chinese language reforms.

@xfq
Copy link
Member

xfq commented Dec 12, 2022

Discussions in the editors' call: https://www.w3.org/2022/11/29-clreq-minutes.html#t09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants