Submitting Character Proposals

<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta http-equiv="Content-Language" content="en-us"> <meta name="keywords" content="Unicode Standard, proposals"> <title>Submitting Character Proposals</title> <link rel="stylesheet" type="text/css" href="https://www.unicode.org/webscripts/standard_styles.css"> </head> <body> <table width="100%" cellpadding="0" cellspacing="0" border="0">  <tr> <td colspan="2"> <table width="100%" border="0" cellpadding="0" cellspacing="0"> <tr> <td class="icon" style="width:38px; height:35px"> <a href="https://www.unicode.org/"> <img border="0" src="https://www.unicode.org/webscripts/logo60s2.gif" align="middle" alt="[Unicode]" width="34" height="33"></a> </td> <td class="icon" style="vertical-align:middle"> <a class="bar"> </a> <a class="bar" href="https://www.unicode.org/alloc/Pipeline.html"><font size="3">Character Proposals</font></a> </td> <td class="bar"> <a href="https://www.unicode.org/main.html" class="bar">Tech Site</a> | <a href="https://www.unicode.org/sitemap/" class="bar">Site Map</a> | <a href="https://www.unicode.org/search" class="bar">Search </a> </td> </tr> </table> </td> </tr> <tr> <td colspan="2" class="gray"> </td> </tr>  <tr> <td valign="top" width="25%" class="navCol"> <table class="navColTable" border="0" width="100%" cellspacing="4" cellpadding="0"> <tr> <td class="navColTitle">Contents</td> </tr> <tr> <td valign="top" class="navColCell"><a href="#General_Information"> General Information</a></td> </tr> <tr> <td valign="top" class="navColCell"><a href="#Proposal_Guidelines"> Proposal Guidelines</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="#Requirements_of_Proposal_Form_and_Process">Requirements of Proposal Form</a></td> </tr> <tr> <td valign="top" class="navColCell"><a href="#Proposal_Review_Process">Proposal Review Process</a></td> </tr> <tr> <td valign="top" class="navColCell"><a href="#Examples">Examples</a></td> </tr> <tr> <td valign="top" class="navColCell"><a href="#Interim_Solutions"> Interim Solutions</a></td> </tr> <tr> <td valign="top" class="navColCell"><a href="#Sending_Proposals"> Sending Proposals</a></td> </tr> </table> <table class="navColTable" border="0" width="100%" cellspacing="4" cellpadding="0"> <tr> <td class="navColTitle">Related Links</td> </tr> <tr> <td valign="top" class="navColCell"><a href="https://www.unicode.org/standard/where/">Where is my Character?</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/roadmaps/">Roadmaps</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/standard/unsupported.html">As Yet Unsupported Scripts</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/standard/supported.html">Supported Scripts</a></td> </tr> <tr> <td valign="top" class="navColCell"><a href="https://www.unicode.org/alloc/Pipeline.html"> Proposed New Characters (Pipeline Table)</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/alloc/nonapprovals.html">Archive of Nonapproval Notices</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/pending/about-sei.html">About the Script Encoding Initiative</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/policies/policies.html">Unicode Policies</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/consortium/utc.html">Unicode Technical Committee (UTC)</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/L2/meetings/utc-meetings.html">Unicode Technical Committee Minutes</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/policies/font_policy.html">Font Submissions Policy</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/L2/summary.html">Proposal Summary Form</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/pending/docsubmit.html">Submitting Documents</a></td> </tr> <tr> <td valign="top" class="navColCell"> <a href="https://www.unicode.org/pending/properties.html">Unicode Properties in Character Proposals</a></td> </tr> </table> </td>  <td> <table> <tr> <td class="contents" valign="top"> <blockquote> <h1 align="left">Submitting Character Proposals</h1> <h2><a name="General_Information">General Information</a></h2> <p>The Unicode Consortium accepts proposals for inclusion of new characters and scripts in the Unicode Standard. Those considering submitting a proposal should first determine whether or not a particular script or character has already been proposed.  Please see the <a href="https://www.unicode.org/alloc/Pipeline.html">Proposed New Characters -- Pipeline Table</a> page for information on additions to the Unicode Standard which are already under consideration. General guidelines for the preparation of a proposal appear below.</p> <table class="sidebar" align="right" width="50%"> <tr> <td class="sidebarTitle">Note:</td> </tr> <tr> <td class="sidebar">The Unicode Consortium is interested in obtaining information on known glyphs, minor variants, precomposed characters (including ligatures, conjunct consonants, and accented characters) and other such "non-characters," mainly for cataloging and research purposes; however, they are generally not acceptable for character proposals. </td> </tr> </table> <p>The Unicode Standard definition of character is stated in the <a href="https://www.unicode.org/glossary/">Glossary of Unicode Terms</a>. Before preparing a proposal, sponsors should note in particular the distinction between the terms character and glyph as therein defined. Because of this distinction, graphics such as ligatures, conjunct consonants, minor variant written forms, or abbreviations of longer forms are generally not acceptable as Unicode characters. Also see <a href="https://www.unicode.org/standard/where/">Where is my Character?</a></p> <h2><a name="Proposal_Guidelines">Proposal Guidelines</a></h2> <p>The sponsor(s) proposing the addition of a new character to the Unicode Standard should follow these guidelines.</p> <p>Proposals for new emoji need to meet different criteria, however. To propose new emoji, follow the <a href="https://www.unicode.org/emoji/proposals.html">Guidelines for Submitting Unicode Emoji Proposals</a> instead of the rest of this section.</p> <p> Before proceeding, determine that each proposed addition is a character according to the definition given in the Unicode Standard and that the proposed addition does not already exist in the Standard. Consult the <a href="https://www.unicode.org/alloc/Pipeline.html"> Proposed New Characters</a> page to see if the character is already on track to be encoded, and the <a href="https://www.unicode.org/alloc/nonapprovals.html">Archive of Nonapproval Notices</a> to see if the character has already been considered but was disapproved for some reason. </p> <p> Often a proposed character can be expressed as a sequence of one or more existing Unicode characters. Encoding the proposed character would be a duplicate representation, and is thus not suitable for encoding. (In any event, the proposed character would disappear when normalized.) For example, a g-umlaut character is not suitable for encoding, since it can already be expressed with the sequence <g, combining diaeresis>. For further information on such sequences see <i> <a href="https://www.unicode.org/standard/where/">Where is my Character</a></i> and the FAQ page <i> <a href="https://www.unicode.org/faq/char_combmark.html"> Characters, Combining Marks</a></i>. </p> <p> Ensure that documentation supporting the proposal states whether any Unicode characters were examined as possible equivalents for the proposed character and, if so, why each was rejected. Consult the <a href="https://www.unicode.org/policies/stability_policy.html">Unicode Character Encoding Stability Policy</a> to make sure that any associated change to existing characters is in accordance with Consortium policies. </p> <p> Determine and list the proposed (or recommended) character properties for each character being proposed, especially when proposing entire scripts for encoding. See the <a href="https://www.unicode.org/pending/properties.html">Unicode Properties in Character Proposals</a> for guidelines about character properties and a list of questions to help make determinations about appropriate property values. See also Chapter 4, Character Properties of <a href="https://www.unicode.org/versions/latest/">The Unicode Standard</a>. Even a <i>partial</i> list of properties will be helpful in the initial proposal. </p> <p> Proposals to include entire scripts (Egyptian hieroglyphics, for example) must cite modern, definitive sources of information regarding such scripts. Sponsorship by the relevant academic bodies (such as The International Association of Egyptologists) may be helpful in determining the proper scope for encoding of characters in such cases. Before submitting full script proposals, sponsors should also determine that a proposal does not already exist for that script, for example by consulting the <a href="https://www.unicode.org/roadmaps/">Roadmaps</a>.</p> <p> If a proposed character is part of a dead language or obsolete/rare script that is already encoded, cite the most important modern sources of information on the script and the proposed additions. Names, including academic affiliation, of researchers in the relevant field are welcomed. </p> <p> If the proposed characters exhibit shaping behavior (contextual shaping, ligatures, conjuncts, or stacking), provide a description of that behavior, preferably with glyph examples. It should be sufficient so that software engineers can produce a minimally acceptable rendering of the characters. </p> <p> <span>If the proposed characters are symbols, consult the <a href="https://www.unicode.org/pending/symbol-guidelines.html">Criteria for Encoding Symbols</a> to gain familiarity with some of the criteria that the UTC will consider when determining whether new symbols are appropriate for encoding. Research other already-encoded blocks of symbols in the standard to check that the types of symbols in the proposal have precedents. Also, because symbols often vary widely in appearance, check carefully that the symbol(s) in the proposal are not merely font-specific variant shapes of symbols already encoded in the standard.</span></p> <p> Information about the sorting order of proposed characters should also be provided, where known. For general information about sorting, see <a href="https://www.unicode.org/collation/">Collation</a>. In particular, consider the <a href="https://www.unicode.org/collation/ducet-criteria.html">UCA Default Table Criteria for New Characters</a>, which specifies the criteria the UTC uses for making initial determinations about collation weights for newly encoded characters. </p> <p> The Unicode Consortium works closely with the relevant committee responsible for ISO/IEC 10646, namely JTC1/SC2/WG2, in proposing additions as well as monitoring the status of proposals by various national bodies. Therefore, proposals may eventually be formulated as ISO/IEC documents and significant detailed information will be required. </p> <p> The standardized form "ISO/IEC JTC 1/SC 2/WG 2 PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646" has been designed for the purpose of obtaining detailed information for ISO purposes and for the Unicode Technical Committee. Use of this form is required for all proposals. It is available at the following URL: </p> <p> <a href="https://www.unicode.org/L2/summary.html"> https://www.unicode.org/L2/summary.html</a></p> <p>To complete the Proposal Summary Form, sponsors may wish to refer to the WG2 Principles and Procedures document, also accessible from that URL. That document contains context and explanations about the various questions on the Proposal Summary Form.</p> <p> Before "finally approving" additions, we require a font with an appropriate license for printing the standard (see <a href="https://www.unicode.org/policies/font_policy.html">Font Submissions Policy</a>). Even if approved, additions won't be published in a version of the standard unless suitable fonts are available.</p> <h2><a name="Requirements_of_Proposal_Form_and_Process">Requirements of Proposal Form</a></h2> <p>The proposal summary form requires the following information (paraphrased): </p> <ul> <li>the repertoire, including proposed character names;</li> <li>the name and contact information for a company or individual who would agree to provide a computerized font (True Type or PostScript) for publication of the standard;</li> <li>references to dictionaries and descriptive texts establishing authoritative information;</li> <li>names and addresses of appropriate contacts within national body or user organizations;</li> <li>the context within which the proposed characters are used (for example, current, historical, and so on);</li> <li>especially for sporadic additions, what similarities or relationships the proposed characters bear to existing characters already encoded in the standard.</li> </ul> <p>All proposals (whether successful or not) and related materials will be retained by the Unicode Consortium as a matter of record and may be used for any purpose.</p> <h2><a name="Proposal_Review_Process">Proposal Review Process</a></h2> <p>The international standardization of entire scripts requires a significant effort on the sponsor's part. It frequently takes years to move from an initial draft to final standardization, particularly because of the requirements to synchronize proposals with the work done in the ISO committee responsible for the development of ISO/IEC 10646.</p> <p>Experience has shown that it is often helpful to discuss preliminary proposals before submitting a detailed proposal. One option is to <a href="https://www.unicode.org/consortium/join.html">become a member</a> of the Unicode Consortium, and submit the proposal to the members-only email list. Alternatively, sponsors can contact the UC Berkeley鈥檚 <a href="http://linguistics.berkeley.edu/sei/">Script Encoding Initiative</a> for initial review. </p> <p>Each proposal received will be evaluated initially by technical officers of the Unicode Consortium and the result of this initial evaluation will be communicated to the sponsor(s) of the proposal. Once a proposal passes this initial screening, it will be reviewed by the <a href="https://www.unicode.org/consortium/utc.html">Unicode Technical Committee</a>.</p> <p>Sponsors, particularly of entire scripts, should be prepared to become involved at various times throughout the process -- perhaps revising their proposals more than once; collecting further detailed information; organizing on-line discussions or meetings to dispel controversy; or answering questions posed by committees or national bodies. Without such involvement, any proposal of more than a few characters is unlikely to be successful in the long-run.</p> <p>Sponsors can monitor the further progress of their proposals via the <a href="https://www.unicode.org/consortium/utc-minutes.html">public UTC minutes</a> as well as the <a href="https://www.unicode.org/alloc/Pipeline.html">Proposed New Characters -- Pipeline Table</a> page.</p> <h2><a name="Examples">Examples</a></h2> <p>Many good proposals can be found in the <a href="https://www.unicode.org/L2/all-docs.html">UTC document register</a>. <a href="http://repositories.cdlib.org/tlg/unicode/">Thesaurus Linguae Graecae</a> has prepared a number of successful proposals.</p> <p>For people interested in proposing a single symbol or a small set of symbols for encoding, there are also many successful proposals in the UTC document register. For example see the <a href="https://www.unicode.org/L2/L2014/14009r-power-symbol.pdf"> proposal for power symbols</a>.</p> <h2><a name="Interim_Solutions">Interim Solutions</a></h2> <p>There are ways for programmers and scholarly organizations to make use of Unicode character encoding, even if the script they want to use or transmit is not yet (or may never be) part of the Unicode Standard. Individual groups that make use of rare scripts or special characters can reach a private agreement about interchange and set aside part of the Private Use Area to encode their private set of characters. Individuals with interests in rare scripts or materials relating to them may sometimes be contacted through an electronic mail list which the Consortium maintains. For information about these mail lists, please <a href="https://www.unicode.org/reporting.html">contact the Unicode office</a>.<br> </p> <h2><a name="Sending_Proposals">Sending Proposals</a></h2> <p>To send completed proposals or to make further inquiries, please see the <a href="https://www.unicode.org/pending/docsubmit.html"> Document Submission Details</a> page.</p> <p>All proposals are required to be in one of the following forms:</p> <ul> <li>PDF format (preferred)</li> <li>HTML along with any needed GIF or JPEG images (a ZIP file or TAR archive should be made, including all of the required files)</li> </ul> <hr width="50%"> <div align="center"> <center> <table cellspacing="0" cellpadding="0" border="0"> <tr> <td><a href="https://www.unicode.org/copyright.html"> <img src="https://www.unicode.org/img/hb_notice.gif" border="0" alt="Access to Copyright and terms of use" width="216" height="50"></a></td> </tr> </table> </center> </div> </blockquote> </td> </tr> </table> </td> </tr> </table> </body> </html>

CINXE.COM

Submitting Character Proposals