Accumulated Feedback on PRI #316

This page is a compilation of formal public feedback received so far. See Feedback for further information on this issue, how to discuss it, and how to provide feedback.

Date/Time: Fri Jan 22 10:32:29 CST 2016
Name: Bobby Tung
Report Type: Public Review Issue
Opt Subject: #316 Add 30FB KATAKANA MIDDLE DOT as well

Hello, 

I think U+30FB should be added to change list as well. 

In Taiwan, middle dot is a formal punctuation called 間隔號(separation mark) for
many purpose, such like:

- as separator of translated foreign name, i.e. Steve Jobs = 史蒂夫・賈伯斯
- as separator of book's name and chapter's name, i.e. 詩經・國風
- as separator of month and date, i.e. 五・二〇

This mark should be full-width whether horizontal or vertical writing. But
code points mapped from BIG-5, middle dots mapped to U+00B7 and U+2027. Both
of them are not supposed to be full-width.

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.

Bobby Tung / W3C invited expert

Date/Time: Thu Feb 11 12:38:03 CST 2016
Name: Jungshik Shin
Report Type: Public Review Issue
Opt Subject: PRI 316

Hello, 

This is my feedback on PRI 316. 

For characters in group 1, their Script_Extension values are changed from
Han,Hangul,Hiragana,Katakana, Bopomofo to Han and Hangul in the proposal.

I don't see a good reason to keep Hangul while dropping Hiragana, Katakana,
and Bopomofo for them. Dropping Hangul would be equally (if not more)
justified for those characters. For instance, having Hangul for U+331B (
SQUARE ERA NAME HEISEI ) while dropping Hiragana and Katakana makes little
sense if any at all.

Dropping Hangul as well from Script_Extension values of those characters
(group 1) is also more consistent with what's proposed for characters in group
3.

For instance, U+3244 (CIRCLED IDEOGRAPH QUESTION) in group 3 will have 'Han'
only per this proposal. Keeping Hangul as well as Han for U+3291 (CIRCLED
IDEOGRAPH STOCK) while having only Han for U+3244 would be very hard to
justify.

Thank you for the consideration. 

Jungshik Shin

Date/Time: Fri May 6 22:29:50 CDT 2016
Name: John Cowan
Report Type: Feedback on an Encoding Proposal
Opt Subject: 16142-pri316-background.html

Looks to me like GETA MARK should be changed to Han only; it represents a 
missing ideograph, not a missing kana or bopomofo letter or Hangeul syllable.

Date/Time: Mon May 9 23:02:59 CDT 2016
Name: Alex DelPriore
Report Type: Public Review Issue
Opt Subject: PRI #316 Add U+3006 IDEOGRAPHIC CLOSING MARK

I would argue for the inclusion of 〆 U+3006 IDEOGRAPHIC CLOSING MARK among the
characters for which Hira and Kata should be removed from Script_Extensions.

The mark derives from the top portion of 占, and is used to abbreviate that
character, along with a few others (締/閉/絞) used to write the same word ("to
close," in various senses). The derivation of the mark from a particular
kanji, rather than, for instance, a ligature of the kana it is most often read
as (しめ), differentiates it from e.g. ゟ U+309F HIRAGANA DIGRAPH YORI, an
obvious ligature of two hiragana. I am also unaware of any examples of the
mark being used in pure-kana text.

Moreover, there exists the homoglyph 乄 U+4E44, a CJK Unified Ideograph, which
(as far as I can tell) was encoded purely for compatibility with JIS X
0208/0212 and should not be thought of as different semantically from its
counterpart in CJK Symbols and Punctuation. Wikipedia
(https://ja.wikipedia.org/wiki/%E3%80%86#.E7.AC.A6.E5.8F.B7.E4.BD.8D.E7.BD.AE)
notes the inconsistent usage of both characters, and specifically denies the
difference between the two as one of symbol vs. kanji, based on their General
Categories (both Lo).

Therefore, I think 〆 U+3006 IDEOGRAPHIC CLOSING MARK should be considered the
abbreviation of one of a set of Han characters, and not a part of the kana
scripts.