N3___
L2/09-___
Date: 2009-Aug-05
Authors:
Markus Scherer, Mark Davis, Kat Momoi, Darick Tong (Google Inc.)
Yasuo Kida, Peter Edberg (Apple Inc.)
We propose adding 10 UCS characters for round-trip conversion with extended versions of Shift-JIS or ISO-2022-JP used by the Japanese cell phone carriers KDDI and Softbank.
These 10 characters are in very common use, and are interchanged with many other systems. They were included, with different proposed character names, in the Proposal for Encoding Emoji Symbols (N3583 = L2/09-026R) but left out of the consensus document from the 2009-April WG2 meeting after discussion and an inconclusive, three-way "straw poll".
Proposed characters:
1F565 EMOJI COMPATIBILITY SYMBOL-6
* represents KDDI Emoji #703
* represents Softbank Emoji #430
= e-4ED
1F566 EMOJI COMPATIBILITY SYMBOL-7
* represents KDDI Emoji #700
* represents Softbank Emoji #425
= e-4E8
1F567 EMOJI COMPATIBILITY SYMBOL-8
* represents KDDI Emoji #366
* represents Softbank Emoji #428
= e-4EB
1F568 EMOJI COMPATIBILITY SYMBOL-9
* represents KDDI Emoji #499
* represents Softbank Emoji #424
= e-4E7
1F569 EMOJI COMPATIBILITY SYMBOL-10
* represents KDDI Emoji #702
* represents Softbank Emoji #427
= e-4EA
1F56A EMOJI COMPATIBILITY SYMBOL-11
* represents KDDI Emoji #701
* represents Softbank Emoji #426
= e-4E9
1F56B EMOJI COMPATIBILITY SYMBOL-12
* represents KDDI Emoji #237
* represents Softbank Emoji #422
= e-4E5
1F56C EMOJI COMPATIBILITY SYMBOL-13
* represents KDDI Emoji #704
* represents Softbank Emoji #431
= e-4EE
1F56D EMOJI COMPATIBILITY SYMBOL-14
* represents KDDI Emoji #367
* represents Softbank Emoji #429
= e-4EC
1F56E EMOJI COMPATIBILITY SYMBOL-15
* represents KDDI Emoji #90
* represents Softbank Emoji #423
= e-4E6
Proposed glyphs: Dashed boxes with text, similar to U+FFFC and U+1680. In each dashed box, the text should be on two lines, "EC" on top and the number 6..15 on the bottom.
Properties: Standard symbols properties, with Bidi_Mirroring=False, for example
1F565;EMOJI COMPATIBILITY SYMBOL-6;So;0;ON;;;;;N;;;;;
Proposal Summary Form
ISO/IEC JTC 1/SC 2/WG 2
PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS
FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646
Please fill all the sections A, B and C below.
Please read Principles and Procedures Document (P & P) from
http://www.dkuug.dk/JTC1/SC2/WG2/docs/principles.html for guidelines and details before filling this form.
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.
Form number: N3452-F (Original 1994-10-14; Revised 1995-01, 1995-04, 1996-04, 1996-08, 1999-03, 2001-05, 2001-09, 2003-11, 2005-01, 2005-09, 2005-10, 2007-03, 2008-05) |
A. Administrative| | | | | | | | | | | | | | | | | | | | | | 1. Title: | Proposal for Encoding 10 Emoji Compatibility Symbols
| |
| 2. Requester's name: | Markus Scherer, Google Inc.
| | 3. Requester type (Member body/Liaison/Individual contribution): | Individual contribution
| | 4. Submission date: | 2009-Aug-05
| | 5. Requester's reference (if applicable): | | | 6. Choose one of the following: | | | This is a complete proposal: | Yes | | | (or) More information will be provided later: | No |
|
B. Technical - General| | | | | | | | | | | | | | | | | | | | | | 1. Choose one of the following: | | | a. This proposal is for a new script (set of characters): | No | | | Proposed name of script: | | | | b. The proposal is for addition of character(s) to an existing block: | Proposed Block
| | | Name of the existing block: | Emoji Compatibility Symbols
| | 2. Number of characters in proposal: | 10
| | 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. Is a repertoire including character names provided? | Yes
| | | a. If YES, are the names in accordance with the "character naming guidelines" | Yes | | | b. Are the character shapes attached in a legible form suitable for review? | No | | 5. Who will provide the appropriate computerized font (ordered preference: True Type, or PostScript format) for | | | publishing the standard? | Apple | | If available now, identify source(s) for the font (include address, e-mail, ftp-site, etc.) and indicate the tools | | | used: | | | 6. 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 (same as for N3582=L2/09-025R2)
| | 7. Special encoding issue | | | 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)? | No
| | | | | 8. 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 athttp://www.unicode.org for such information on other scripts. Also see http://www.unicode.org/Public/UNIDATA/UCD.htmland associated Unicode Technical Reports for information needed for consideration by the Unicode Technical Committee for inclusion in the Unicode Standard. |
|
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, available relevant documents: | Search engine and email/chat vendors are involved
| | 3. Information on the user community for the proposed characters (for example: | | | size, demographics, information technology use, or publishing use) is included? | Originally Japan
| | | Reference: | These symbols are available to all Japanese KDDI and Softbank cell phone users
| | 4. The context of use for the proposed characters type of use; common or rare) | common | | | Reference: | | | 5. Are the proposed characters in current use by the user community? | Yes | | | If YES, where? Reference: | Japanese cell phone networks, Google Talk, Google Mail
| | 6. After giving due considerations to the principles in the P&P document must the proposed characters be entirely | | | in the BMP? | No
| | | 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)? | Yes | | 8. Can any of the proposed characters be considered a presentation form of an existing | | | character or character sequence? | No | | | 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 | | | 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? | No
| | | If YES, is a rationale for its inclusion provided? | | | | 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 | | | 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: | | | |
|
|