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 for guidelines and details before filling this form.)
See http://www.dkuug.dk/JTC1/SC2/WG2/docs/summaryform.html for latest Form.
See http://www.dkuug.dk/JTC1/SC2/WG2/docs/principles.html for latest Principles and Procedures document.
See http://www.dkuug.dk/JTC1/SC2/WG2/docs/roadmaps.html for latest roadmaps.

(Form number: N2352-F (Original 1994-10-14; Revised 1995-01, 1995-04, 1996-04, 1996-08, 1999-03, 2001-05, 2001-09)

A. Administrative

1. Title:  __________________________________________________

2. Requester's name: ________________________________________________________
3. Requester type (Member body/Liaison/Individual contribution): ____________
4. Submission date:                                           _______________
5. Requester's reference (if applicable): ___________________________________
6. (Choose one of the following:)
  This is a complete proposal:                                _______________
  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: ______________________________________________
2. Number of characters in proposal:                           ______________
3. Proposed category (see section II, Character Categories):   ______________
4. Proposed Level of Implementation (1, 2 or 3)
                    (see clause 14, ISO/IEC 10646-1: 2000):   _______________
  Is a rationale provided for the choice?                      ______________
   If Yes, reference: _______________________________________________________
5. Is a repertoire including character names provided?         ______________
  a. If YES, are the names in accordance with the 
    'character naming guidelines in Annex L of ISO/IEC 10646-1: 2000? _______
  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,
   e-mail, ftp-site, etc.) and indicate the tools used:
   __________________________________________________________________________
   __________________________________________________________________________
   __________________________________________________________________________
7. References:
  a. Are references (to other character sets, dictionaries, descriptive
     texts etc.) provided?                                     ______________
  b. Are published examples of use (such as samples from newspapers,
     magazines, or other sources) of proposed characters attached? __________
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)?
    _________________________________________________________________________
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 http://www.unicode.org for such information on other scripts. Also see Unicode Character Database http://www.unicode.org/Public/UNIDATA/UnicodeCharacterDatabase.html and 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? ____
  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.)?                                       ______________
   If YES, with whom? _______________________________________________________
     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: ______________________________________________________________
4. The context of use for the proposed characters (type of use;
   common or rare)                                             ______________
    Reference: ______________________________________________________________
5. Are the proposed characters in current use by the user community? ________
   If YES, where?  Reference: _______________________________________________
6. After giving due considerations to the principles in Principles and
   Procedures document (a WG 2 standing 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?                   ______________
   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? _____
   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?           ______________
   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 (see clauses 4.12 and 4.14
    in ISO/IEC 10646-1: 2000)?                                  _____________
   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?                       ______________
   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: ______________________________________________________

A.1 Submitter's Responsibilities

The national body or liaison organization (or any other organization or an individual) proposing new character(s) or a new script shall provide:

  1. Proposed category for the script or character(s), character name(s), and description of usage.
  2. Justification for the category and name(s).
  3. A representative glyph(s) image on paper:
    If the proposed glyph image is similar to a glyph image of a previously encoded ISO/IEC 10646 character, then additional justification for encoding the new character shall be provided.
    Note: Any proposal that suggests that one or more of such variant forms is actually a distinct character requiring separate encoding, should provide detailed, printed evidence that there is actual, contrastive use of the variant form(s). It is insufficient for a proposal to claim a requirement to encode as characters in the Standard, glyphic forms which happen to occur in another character encoding that did not follow the Character-Glyph Model that guides the choice of appropriate characters for encoding in ISO/IEC 10646.
    Note: WG 2 has resolved in Resolution M38.12 not to add any more Arabic presentation forms to the standard and suggests users to employ appropriate input methods, rendering and font technologies to meet the user requirements.
  4. Mappings to accepted sources, for example, other standards, dictionaries, accessible published materials.
  5. Computerized/camera-ready font:
    Prior to the preparation of the final text of the next amendment or version of the standard a suitable computerized font (camera-ready font) will be needed. Camera-ready copy is mandatory for final text of any pDAMs before the next revision. Ordered preference of the fonts is True Type or PostScript format. The minimum design resolution for the font is 96 by 96 dots matrix, for presentation at or near 22 points in print size.
  6. List of all the parties consulted.
  7. Equivalent glyph images:
    If the submission intends using composite sequences of proposed or existing combining and non-combining characters, a list consisting of each composite sequence and its corresponding glyph image shall be provided to better understand the intended use.
  8. Compatibility equivalents:
    If the submission includes compatibility ideographic characters, identify the equivalent unified CJK Ideograph character(s).
  9. Any additional information that will assist in correct understanding of the different characteristics and linguistic processing of the proposed character(s) or script.