Please fill Sections A, B and C below. Section D will be filled by SC 2/WG 2.

For instructions and guidance for filling in the form please see the document " Principles and Procedures for Allocation of New Characters and Scripts" (

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 (see clause 15, ISO/IEC 10646-1):
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 K of ISO/IEC 10646-1?
b. Are the character shapes attached in a reviewable form?

6. Who will provide the appropriate computerized font (ordered preference: True Type, PostScript or 96x96 bit-mapped 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 (such as samples from newspapers, magazines, or
other sources) of use 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):

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?

4. The context of use for the proposed characters (type of use; common or rare)

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 N 1352 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 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:

10. Does the proposal include use of combining characters and/or use of composite sequences (see clause 4.11 and 4.13 in ISO/IEC 10646-1)?
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:

11. 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)

D. SC 2/WG 2 Administrative (To be completed by SC 2/WG 2)

1. Relevant SC 2/WG 2 document numbers:

2. Status (list of meeting number and corresponding action or disposition):

3. Additional contact to user communities, liaison organizations etc:

4. Assigned category and assigned priority/time frame: