[Unicode]  Roadmaps to Unicode Home | Site Map | Search

Roadmaps to Unicode

These pages present proportional maps of actual and proposed allocations to Unicode and ISO/IEC 10646. The following conventions are used in the table to help the user identify the status of the proposals here.

  • Bold text indicates an allocated (that is, published) character collection. For blocks containing assigned graphic or format characters, there is a link to the charts on the Unicode web site.
  • (Bold text between parentheses) indicates scripts which have been formally accepted by UTC or WG2 for processing toward inclusion in the standard. There is generally a link to a mature proposal for the script.
  • (Text between parentheses) indicates scripts for which proposals have been formally submitted to the UTC or to WG2. There is generally a link to the formal proposal.
  • ┬┐Text between question marks? indicates scripts for which detailed proposals have not yet been written. There may be a link to an exploratory code table.
  • ??? in a block indicates that no suggestion has been made regarding the block allocation.
  • Color highlighting is used to indicate blocks and unassigned ranges which default to right-to-left character behavior.
  • Grey shading is used to indicate ranges of control characters and noncharacters.

NOTE: When scripts are actually proposed to the UTC or to WG2, the practice is to "front" them in the zones to which they are tentatively allocated, and to adjust the block size with regard to the allocation proposed.

The size and location of the unallocated script blocks are merely proposals based on the current state of planning. The size and location of a script may change during final allocation of the script.

NOTE: In most cases, scripts are allocated so as not to cross 128-code-point boundaries (that is, they fit in ranges nn00..nn7F or nn80..nnFF). For supplementary characters, an additional constraint not to cross 1,024-code-point boundaries is also applied (that is, scripts fit in ranges nn000..nn3FF, nn400..nn7FF, nn800..nnBFF, or nnC00..nnFFF). The reason for such constraints is to enable better optimizations for tasks such as building tables for access to character properties.

The Roadmap Committee maintains and updates this document as a service to the Unicode Technical Committee and to ISO/IEC JTC1/SC2/WG2.