SC2/WG2 N3063

N _____N 1180ISO/IEC JTC 1/SC 2/WG 2/IRG
ISO/IEC JTC 1/SC 2/WG 23063

ISO/IEC JTC1/SC2/WG2/IRG

Ideographic Rapporteur Group(IRG)
TITLE:SOURCE:STATUS:
DISTRIBUTION:DATE:REFERENCE:ATTACHMENTS:

Proposed additions to the CJK Strokes block of theUCSIRG Rapporteur
Submission from the IRG to WG2Members of ISO/IEC JTC1/SC2/WG2
2006-4-3
WG2 N2807R, N2808R, IRG N1174
IRG N1181 (“Summary for Stroke submission”)

SummaryThis document proposes the addition of twenty new CJK Strokes to the CJKStrokes block of the UCS.
WG2 resolution M45.34 (N2754R) expanded the scope of IRG work to include CJKStrokes. The CJK Strokes block (U+31CO..U+31EF) now contains a total ofsixteen CJK Strokes (U+31C0..U+31CF), derived from HKSCS (ISO/IEC10646:2003/Amd.1).
The IRG formed ad-hoc groups to complete the repertoire of common CJK Strokes,
and finalized the repertoire in the IRG#25 meeting held in Berkeley, California,
U.S.A. The twenty new CJK Strokes are proposed for code points in the range(U+31D0..U+31E3). Information on naming conventions and collation is alsoprovided.

List of the proposed characters, character names and code positions
31C0123456789ABCD

31D31E㇀ ㇐ ㇠㇁ ㇑ ㇡㇂ ㇒ ㇢㇃ ㇓ ㇣㇄ ㇔㇅ ㇕㇆ ㇖

31C0

CJK STROKE T

31E0

CJK STROKE HXWG

31C1

CJK STROKE WG

31E1

CJK STROKE HZZZG

31C2CJK STROKE XG

31E2

CJK STROKE PG

31C3

CJK STROKE BXG

31E3CJK STROKE Q

31C4CJK STROKE SW

31C5CJK STROKE HZZ

31C6CJK STROKE HZG

31C7CJK STROKE HP

31C8CJK STROKE HZWG

31C9CJK STROKE SZWG

31CACJK STROKE HZT

31CB

CJK STROKE HZZP

31CCCJK STROKE HPWG

31CDCJK STROKE HZW

31CECJK STROKE HZZZ

31CFCJK STROKE N

31D0CJK STROKE H

31D1CJK STROKE S

31D2CJK STROKE P

31D3CJK STROKE SP

31D4CJK STROKE D

31D5CJK STROKE HZ

31D6CJK STROKE HG

31D7CJK STROKE SZ

31D8CJK STROKE SWZ

31D9CJK STROKE ST

31DACJK STROKE SG

31DBCJK STROKE PD

31DCCJK STROKE PZ

31DDCJK STROKE TN

31DE

CJK STROKE SZZ31DFCJK STROKE SWG

㇇ ㇗ ㇘㇉ ㇙㇊ ㇚㇋ ㇛㇌ ㇜㇍ ㇝E㇎ ㇞F㇏ ㇟

Stroke Type Naming Conventions
Stroke types have traditionally been named using combinations of Han charactersmeaning ‘horizontal’, ‘vertical’, ‘bent’, ‘curved’, etc.
These characters are conveniently represented by single letters of the alphabet,which are abbreviations for the Mandarin pronunciations of these characters. The
following table shows each abbreviation, in alphabetical order, followed by thecorresponding Hanyu Pinyin, Han character, and approximate meaning in
English. In all cases, the final alphabetic string in the character name may beconverted to the sequence of Han characters for that name, simply by substituting
a Latin letter in the following list for the corresponding Han character.
For example, "HZZZG" becomes 橫折折折鉤.
B

biǎn扁

‘flat’

Qquān圈

‘circle’Ddiǎn點‘dot’Sshù

豎‘vertical’

Ggōu

鉤

‘hook’

Ttí提‘rising’Hhéng橫‘horizontal’Wwān彎‘curved’Nnà捺‘right-falling’Xxié

斜‘slant’Ppiě撇‘left-falling’Zzhé折‘bent’

Variants and usage examples of CJK Strokes
The following table illustrates typical variant forms of each stroke type and Hancharacters encoded in ISO/IEC 10646 as examples of usage.
Stroke

㇐㇀

Name
H (橫)

Variants Usage examples

0

冰，淋，治，冶，冽，暴，氾，录，地，虫T (提)U+31C0㇑S (豎)一，三，丁，丞，丈，世，不，上，十，卅，七>丩，中，串，讧，乍，上，五，丑㇚㇒㇓㇔㇏

SG (豎鉤)爭，事，求，水P (撇)乂，爻，禾，毛，乏，乖，
釆，衣，八，行SP (豎撇)乃，月，用，齊，几，人，班，大D (點)U丸，义，永，冰，凡，丹，主，求，火，刃[大，人，天，入，走，边，廷，尺N (捺)U+31CFZg㇝㇕㇇TN (提捺)–尐，八，入, 廻

HZ (橫折)口，囗，田，品，吕，申，甲，圆，巪

HP (橫撇)又，双，叒，今HG (橫鉤)疋，了，予，矛，子，字，疏，写，冖

U+31C7㇖㇗

SZ (豎折)u

断，继，山，互，彙，牙，乐，东㇘㇄

SWZ (豎彎左)肅嘯蕭簫SW (豎彎)區，亡，妄，四ST (豎提)食，良，艮，很，狠，鄉，民

U+31C4㇙㇜㇛㇢㇁

PZ (撇折)}弘，公，翁PD (撇點)巡，獵，災，甾，女，巛

PG (撇鉤)乄WG (彎鉤)狐，嶽，貓，家，逐XG (斜鉤)戈，弋，戰，我BXG (扁斜鉤)

心，必，沁，惢，蕊

HZZ (橫折折)卍

HZW (橫折彎)殳，投，朵HZT (橫折提)讠，计，鳩U+31C1㇂
U+31C2

㇃
U+31C3

㇅
U+31C5

㇍
U+31CD㇊
U+31CA㇆HZG (橫折鉤)ü羽，习，包，勻，葡，用，青，甫，勺，月，也，乜

HZWG (橫折彎鉤)¢飞，风，瘋，九，几，气，虱´

亞，鼎，卐，吳，专，𧦮，𤓷，𤦡

U+31C6


U+31C8SZZ (豎折折)㇞Ø㇟㇎

SWG (豎彎鉤)乱，己，已，巳HZZZ (橫折折折)凸

HZZP (橫折折撇)建，及

HXWG (橫斜彎鉤)乙，氹，乞HPWG (橫撇彎鉤)阝，队，邮

SZWG (豎折彎鉤)号，亏，弓，强，丐，马，丂HZZZG (橫折折折鉤)

乃，孕，仍

Q (圈)

〇，㔔，㪳，㫈

U+31CE

㇋U+31CB㇠㇌
U+31CC㇉
U+31C9㇡㇣

Unicode Character Properties
All proposed characters should have the following Unicode properties so that they
match those of the encoded sixteen CJK Strokes.
So;0;ON;;;;;N;;;;;

Collation of CJK Strokes
Because the HKSCS strokes were added to the block before the more complete
repertoire was developed, the strokes in the block are out of order, in terms of thetraditional stroke classification. CJK Strokes are divided into five broad types, inMandarin called the five 札 zhá types, since the Han character “札” exhibits each ofthe types: ㇐㇑㇒㇔㇠ ( héng shù piě diǎn zhé ). The collation order proposed here
assigns each stroke to one and only one of the five types, and further sub-classifies
each stroke according to its specific features (see IRG N987). The following is an XML
representation of the collation data for the proposed CJK Strokes block, in accordancewith CLDR guidelines.
<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE ldml SYSTEM "http://www.unicode.org/cldr/dtd/1.4/ldml.dtd"><ldml><identity><version number="$Revision: 1.00 $"/>
<generation date="$Date: 2005/12/12 12:12:12 $"/>
<language type="root" /> <!-- since this is a pan-language ordering of CJK --></identity><collations> <!-- removing the valid sublocales until a complete list is available --><collation type="IRG-Strokes" > <!-- or whatever name would be most descriptive --><rules><!-- 札 zhá type 1 --><!-- h; t --><pc> ㇐㇀</pc><!--札 zhá type 2--><!-- s; sg --><pc>㇑㇚</pc><!--札 zhá type 3--><!-- p; sp --><pc>㇒㇓</pc><!--札 zhá type 4--><!-- d; n; tn --><pc>㇔㇏㇝</pc><!--札 zhá type 5--><!-- hz; hp; hg; sz; swz; sw; st; pz; pd; pg; wg; xg; bxg; hzz; hzw; hzt; hzg; hxg; szz; swg; hzzz; hzzp;hxwg; hpwg; szwg; hzzzg; q --><pc>㇕㇇㇖㇗㇘㇄㇙㇜㇛㇢㇁㇂㇃㇅㇍㇊㇆㇈㇞㇟㇎㇋㇠㇌㇉㇡㇣</pc></rules></collation></collations></ldml>Rationale for proposed repertoire
The repertoire of strokes proposed for addition to the existing CJK Strokes block isderived from the stroke types occurring in representative forms of currently encoded
UCS Ideographs. All of these proposed strokes are currently missing from the CJKStrokes block. Representative forms of some proposed CJK Strokes are similar inappearance to representative forms of some single-stroke CJK Ideographs currently
encoded in various UCS blocks (URO, Ext A, Ext B, Kangxi Radicals, CJK Radicals
Supplement). However, single-stroke CJK Ideographs do not have the properties ofCJK Strokes, and single-stroke CJK Ideographs may in some cases exhibit a range ofvariation in their representative glyphs which conflates necessary distinctions for theCJK Strokes block. For example, the proposed CJK Strokes ㇒ “CJK STROKE P”(U+31D2) vs. ㇓ “CJK STROKE SP” (U+31D3) are conflated in the representativeforms currently used for ⼃ “KANGXI RADICAL SLASH” (U+2F03) and 丿 “CJKUNIFIED IDEOGRAPHS-4E3F” (U+4E3F). The proposed strokes complete the set ofmost commonly seen stroke types. The precise definition of the CJK Strokes block andclear differentiation of it from the blocks of CJK Ideographs and Radicals serves anessential purpose in the indexing and collation of encoded and unencoded CJK
Ideographs and Radicals. It is anticipated that some very rare strokes may be
proposed for future addition to this set.

ATTACHEMENTS: IRG N1181 “Summary for Stroke submission”
A. Administrative
1. Title:
Summary for Stroke submission
2. Requester's name:
IRG Rapporteur
3. Requester type (Member body/Liaison/Individual contribution):
IRG
4. Submission date:
2006-4-35. Requester's reference (if applicable):
IRG N1174
6. Choose one of the following:This is a complete proposal:
Yes(or) More information will be provided later:
B. Technical – General
1. Choose one of the following:a. This proposal is for a new script (set of characters):
Proposed name of script:
b. The proposal is for addition of character(s) to an existing block:Yes
Name of the existing block:CJK Strokes
2. Number of characters in proposal:
20
3. Proposed category (select one from below - see section 2.2 of P&P document):
A-Contemporary
B.1-Specialized (small collection)
X
B.2-Specialized (large collection)
C-Major extinct
D-Attested extinct
E-Minor extinct
F-Archaic Hieroglyphic or Ideographic
G-Obscure or questionable usage symbols
4. Proposed Level of Implementation (1, 2 or 3) (see Annex K in P&P document):
1
Is a rationale provided for the choice?
NoIf Yes, reference:
5. Is a repertoire including character names provided?
Yesa. If YES, are the names in accordance with the “character naming guidelines”
in Annex L of P&P document?
Yesb. Are the character shapes attached in a legible form suitable for review?
Yes
6. Who will provide the appropriate computerized font (ordered preference: True Type, or PostScript format) for
publishing the standard?
Beijing Founder Electronic Co.,Ltd.
If available now, identify source(s) for the font (include address, e-mail, ftp-site, etc.) and indicate the tools
used:
9, No. 5 street, Shangdi, Information Industry Base, Haidian District, Beijing 100085, P.R. China;
yjh@founder.com.cn; http://www.foundertype.com
7. References:a. Are references (to other character sets, dictionaries, descriptive texts etc.) provided?
Yes (IRG N1174)
b. Are published examples of use (such as samples from newspapers, magazines, or other sources)of proposed characters attached?
Yes; see “Variants and usage examples of CJK Strokes” sectionin IRG N1180.
8. Special encoding issues:
Does the proposal address other aspects of character data processing (if applicable) such as input,presentation, sorting, searching, indexing, transliteration etc. (if yes please enclose information)?
Yes
9. Additional Information:
Submitters are invited to provide any additional information about Properties of the proposed Character(s) or Scriptthat will assist in correct understanding of and correct linguistic processing of the proposed character(s) or script.
Examples of such properties are: Casing information, Numeric information, Currency information, Display behaviour
information such as line breaks, widths etc., Combining behaviour, Spacing behaviour, Directional behaviour, Default
Collation behaviour, relevance in Mark Up contexts, Compatibility equivalence and other Unicode normalization
related information. See the Unicode standard at http://www.unicode.org for such information on other scripts. Also
see http://www.unicode.org/Public/UNIDATA/UCD.html and associated Unicode Technical Reports for informationneeded for consideration by the Unicode Technical Committee for inclusion in the Unicode Standard.
HTUHTUUTHUTH

C. Technical - Justification
1. Has this proposal for addition of character(s) been submitted before?
No
If YES explain
2. Has contact been made to members of the user community (for example: National Body,
Yes
user groups of the script or characters, other experts, etc.)?
IRGandIdeographicexperts
If YES, with whom?
IRG N987, IRG N1081, IRG N1086A, IRG N1096, IRG
If YES, available relevant documents:

N1097, IRG N1138
3. Information on the user community for the proposed characters (for example:
size, demographics, information technology use, or publishing use) is included?

Users of Hancharacters

Reference:
4. The context of use for the proposed characters (type of use; common or rare)commonReference:
5. Are the proposed characters in current use by the user community?
Yes
Yes; see the representative glyphs in the published ISO/IEC 10646
If YES, where? Reference:
Standard.
6. After giving due considerations to the principles in the P&P document must the proposed characters be entirelyYesin the BMP?
Yes
If YES, is a rationale provided?
IRG
N1180
If YES, reference:
7. Should the proposed characters be kept together in a contiguous range (rather than being scattered)?
Yes
8. Can any of the proposed characters be considered a presentation form of an existing
Nocharacter or character sequence?
If YES, is a rationale for its inclusion provided?
If YES, reference:
9. Can any of the proposed characters be encoded using a composed character sequence of either
Noexisting characters or other proposed characters?
If YES, is a rationale for its inclusion provided?
If YES, reference:
10. Can any of the proposed character(s) be considered to be similar (in appearance or function)Yes
to an existing character?
Yes
If YES, is a rationale for its inclusion provided?
See “Rationale for proposed repertoire” section in IRG N1180
If YES, reference:
11. Does the proposal include use of combining characters and/or use of composite sequences?
No
If YES, is a rationale for such use provided?
If YES, reference:
Is a list of composite sequences and their corresponding glyph images (graphic symbols) provided?
If YES, reference:
12. Does the proposal contain characters with any special properties such as
Nocontrol function or similar semantics?
If YES, describe in detail (include attachment if necessary)

13. Does the proposal contain any Ideographic compatibility character(s)?
If YES, is the equivalent corresponding unified ideographic character(s) identified?
If YES, reference:No