Hentaigana Proposal

Size: px

Start display at page:

Download "Hentaigana Proposal"

あゆみのえ
7 years ago
Views:

1 ISO/IEC JTC 1/SC 2/WG 2 PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC Please fill all the sections A, B and C below. Please read Principles and Procedures Document (P & P) from for guidelines and details before filling this form. Please ensure you are using the latest Form from See also for latest Roadmaps. A. Administrative 1. Title: A proposal for encoding the hentaigana characters 2. Requester's name: Jeroen Ruigrok van der Werven 3. Requester type (Member body/liaison/individual contribution): Individual contribution 4. Submission date: Requester's reference (if applicable): 6. Choose one of the following: This is a complete proposal: X (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: Name of the existing block: Historic Kana (U+1B000 U+1B0FF) 2. Number of characters in proposal: TBD 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): 3 Is a rationale provided for the choice? If Yes, reference: Follows hiragana. 5. Is a repertoire including character names provided? YES a. If YES, are the names in accordance with the character naming guidelines in Annex L of P&P document? TBD b. Are the character shapes attached in a legible form suitable for review? 6. Who will provide the appropriate computerized font (ordered preference: True Type, or PostScript format) for publishing the standard? If available now, identify source(s) for the font (include address, , ftp-site, etc.) and indicate the tools used: 7. References: a. Are references (to other character sets, dictionaries, descriptive texts etc.) provided? YES b. Are published examples of use (such as samples from newspapers, magazines, or other sources) of proposed characters attached? YES 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 Comment [JRW1]: Mojikyo has over 200, apparently. Comment [JRW2]: Since they re sort of hiragana s predecessor they should just follow hiragana s level. 9. Additional Information: Submitters are invited to provide any additional information about Properties of the proposed Character(s) or Script that 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 for such information on other scripts. Also see and associated Unicode Technical Reports for information needed for consideration by the Unicode Technical Committee for inclusion in the Unicode Standard. 1 Form number: N3002-F (Original ; Revised , , , , , , , , , , )

Please ensure you are using the latest Form from http://www.dkuug.dk/jtc1/sc2/wg2/docs/summaryform.html. See also http://www.dkuug.dk/jtc1/sc2/wg2/docs/roadmaps.html for latest Roadmaps. A.

2 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, user groups of the script or characters, other experts, etc.)? YES If YES, with whom? Andrew West, Rick McGowan, Nozumo Katoo If YES, available relevant documents: 3. Information on the user community for the proposed characters (for example: size, demographics, information technology use, or publishing use) is included? Reference: In discussions with various people, as well as based upon my own experiences, hentaigana is not gone from contemporary Japan. Shop signs (kisoba), magazines, newspapers, packaging materials, (dojo) certificates 4. The context of use for the proposed characters (type of use; common or rare) uncommon Reference: 5. Are the proposed characters in current use by the user community? YES If YES, where? Reference: Section TBD 6. After giving due considerations to the principles in the P&P document must the proposed characters be entirely in the BMP? If YES, is a rationale provided? If YES, reference: 7. Should the proposed characters be kept together in a contiguous range (rather than being scattered)? 8. Can any of the proposed characters be considered a presentation form of an existing character or character sequence? YES If YES, is a rationale for its inclusion provided? YES If YES, reference: Section TBD 9. Can any of the proposed characters be encoded using a composed character sequence of either existing characters or other proposed characters? NO 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) to an existing character? YES If YES, is a rationale for its inclusion provided? YES If YES, reference: Section TBD 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 control function or similar semantics? NO If YES, describe in detail (include attachment if necessary) 13. Does the proposal contain any Ideographic compatibility character(s)? NO If YES, is the equivalent corresponding unified ideographic character(s) identified? If YES, reference:

Andrew West, Rick McGowan, Nozumo Katoo If YES, available relevant documents: 3.

3 Section 1 Introduction The Japanese language had for a long period no real written language. At one point Japanese scholars started to use Chinese grammar and characters (kanji 漢字 ) along with diacritics to represent Japanese. This system is called kanbun ( 漢 ). Natural developments lead to using the phonetic rather than the semantic value of the kanji for representing Japanese. These phonetic values were taken from the Chinese reading of the kanji. This system is called manʼyougana ( 万葉仮名 ). Manʼyougana allowed for different kanji to be used to represent the same sound (mora). Often the choice of the kanji was made solely for stylistic purposes. From manʼyougana ultimately evolved both hiragana ( 平仮名ひらがな) and katakana ( 仮名カタカナ) as we know them today. Due to the many different kanji used for representing a specific sound there were many forms of hiragana at first. In 1900 Japan simplified the hiragana system to match one hiragana to a particular sound. The hiragana forms that were not selected are nowadays called hentaigana ( 変体仮名 ). Section 2 Current use Nowadays hentaigana are considered obsolete. There are, however, still current uses of hentaigana in daily life. Such examples include signs of shops (most notably kisoba shops), print on packaging materials, logos, official certificates (typically from a martial arts dojo), calligraphers, history and/or literature scholars, and possibly others. In Japan the use of hentaigana already led to encoding many glyphs in at least three separate projects, to name: Koin, Mojikyo, and TRON. As such there is a strong case to be made to encode hentaigana within Unicode. Section 3 JIS X 0213:2000 on hentaigana In the Japanese standard JIS X 0213:2000, section 4.5.5, the inclusion of a hentaigana repertoire was discussed and dropped. (Note: The JISC website has the JIS X 0213:2000 standard available for download in PDF, but for some reason it seems to end at page 505.) Suzuki-san was kind enough to send me a scan of a paper copy of page 512 of this standard which explains the rationale (in Japanese). I reproduce it here verbatim inline

Natural developments lead to using the phonetic rather than the semantic value of the kanji for representing Japanese. These phonetic values were taken from the Chinese reading of the kanji.

4 along with the translation into English (courtesy of Tom Donahue). Any errors in the Japanese text are most likely my mistake in typing when trying to reproduce it 変体仮名変体仮名は少数例ながら書道の教科書などから採取され採録の要望も出されていたしかしながら字セットとしての変体仮名のレパートリの確定が常に困難であると判断されたことと採取例などに基づきいくつかの変体仮名を追加することを想定した場合でも図形字として分に同定可能な安定した字形をすこと変体仮名とそのもととなった漢字の草書体とを明確に区別することなどが困難であり採録規準を満たせないと判断されたことから変体仮名は採録しないこととした Hentaigana Requests were received to include hentaigana, accompanied by a few examples taken from sources such as calligraphy textbooks. However, the [committee] decided not to include hentaigana because it was judged to be extremely difficult to finalize a repertoire of hentaigana as a character set. A further reason for rejection was that, even if the addition of a certain number of hentaigana were to be considered based on the examples that were collected and submitted to the committee, it was judged that it would be difficult to satisfy the requirements for addition that stipulate that glyphs must be stable and readily identifiable as the same graphic characters, and it must be possible to clearly distinguish hentaigana from the cursive kanji upon which they are based. Section 4 Technical Notes Since hentaigana are sousho ( 草書 ; cursive script) representation characters of certain kanji, it makes sense to encode various hentaigana variants of the same kanji as variation characters. These variation characters are not different in a semantic way, but they are different in their representation form and are needed to provide a proper means of reproducing existing materials. Admittedly they could, largely, be mapped directly as variation characters of the existing hiragana characters, but doing so would ignore the semantic separation between hiragana and hentaigana that took place in Japan around 1900.

として分に同定可能な安定した字形をすこと変体仮名とそのもととなった漢字の草書体とを明確に区別することなどが困難であり採録規準を満たせないと判断されたことから変体仮名は採録しないこととした 4.5.

5 Section 7 Glyphs Codepoint Character name Hentaigana reference glyph Variant hentaigana glyph forms Kanji derivation Corresponding hiragana 鐸安あ濁阿あ諾悪あ膳以い糎意い噌伊い塑移い舵宇う楕有う陀雲う宅江え托要え択盈え待怠於お騒加か像閑か増可か憎我か臓駕か蔵賀か

Corresponding hiragana 鐸安あ濁阿あ諾悪あ膳以い糎意い噌伊い塑移い

6 贈歌か造哥か叩但き達幾き辰幾き奪起き脱貴き巽喜き態久く戴倶く替具く泰求く黛介け鯛計け代遣け台氣け大希け鷹こ滝瀧許こ卓故こ啄古こ茸凧佐さ

7 蛸散さ只斜さ坦志し担四し探之し旦新し歎事し暖す檀春す段男須す談数す値壽す壇世せ弾勢せ断聲せ族続曽そ卒袖所そ其楚そ揃處そ捉當た束堂た測足多た

8 早曹チち巣知ち槍地ち槽遅ち存川つ孫徒つ尊都つ損津つ拓天て沢停て濯亭て琢轉て託弖て想東と捜掃登と挿度と掻等と操と他多奈な太汰那な詑難な蘇仁に

9 訴阻爾に遡に鼠ニに僧児に糟怒ぬ総努ぬ村禰ね遜年ね騨乃の体堆対能の耐濃の岱農の帯廼の狙疏者は疎波は礎盤は祖盤は租半は粗ハは素葉は組頗は炭ひ

10 短ひ端箪ひ綻悲ひ耽ひ第不ふ醍婦ふ題布ふ爽部の旁へ宋倍へ層遍へ匝弊へ惣邊へ創寶ほ双叢保ほ倉喪壮本ほ奏報ほ苔袋末ま貸万ま退満ま逮萬ま隊真ま

11 鱈三み樽み誰丹美み単微み嘆み妥無む惰牟む打舞む柁武む谷め狸免め胆蛋も誕も鍛裳も団茂も滞耶や胎夜や腿屋や竪由ゆ辿遊ゆ棚游ゆ促側與よ

12 則代よ即餘よ息余よ唾良ら堕羅ら漕燥利り争梨り痩り相離り窓理り綜留る聡累る草流る荘類る速禮れ俗連れ属賊麗れ岨呂ろ措婁ろ曾樓ろ曽路ろ楚露ろ

13 送王わ遭輪わ鎗和わ霜倭わ駄井ゐ淡恵ゑ湛衛ゑ葬蒼乎を藻遠を装越を走尾を知地ん迢迪ゝゝ Section 9 Proposed code points and properties

14 Section 10 References Taken from [retrieved ] 商品番号 BK-5660 変体仮名速習課題較的よく使される変体仮名 96 字について原字とともに観峰先に本をしていただいた教本で要領よく学ぶことができます

jpg Taken from http://www.kampo.co.jp/kampo-college/kccproducts/books-a2.

15 Taken from [retrieved ] 只今準備中のなかから春琴抄表紙が漆塗り! 本は変体仮名の草書体 Taken from [Retrieved ] 吉野葛表紙にはなんと崎が吉野から集めてきた葛の葉が貼り込まれている

16 Taken from [Retrieved ] そこで本物とニセ物の分けも伝授しておこう写真上のの太のぼりが本物で下のふのりえでくいたらぬがニセ物である後者の本物はふのりは( 把 )でと書かれていたがニセ物絵師ははの変体仮名が読めずはを字にまとめてえとしてしまい意味が通じなくなった

17 Taken from 画像 :Hyakuninisshu_057.jpg [Retrieved ] BE%5D

word=*%5b%ca%d1%c2%ce%b2%be%cc% BE%5D http://www.asahi-net.or.jp/~qm4h-iim/ktb_s01.htm http://www2s.biglobe.ne.jp/~tico/tokyo/kana/kana.

html http://www.matsudaisoba.co.jp/syohin/m02.html http://www.soba-udon.com/free_9_14.html http://s-dog.

Microsoft Word - Japanese Translation of Document N3582.doc

Microsoft Word - Japanese Translation of Document N3582.doc ISO/IEC JTC1/SC2/WG2 N3621 L2/09-xxx 2009-04-17 訳目注的 :このに日本翻語訳に文訳はしたものです ISO/WG2 に従 Unicodeコンソーシアムよりってこれは正式な提案文書提ではありませんあくまで出された英文の原文の便内宜容上をより用意多されたものですくの人