Source: Michael Everson
Title: Committee draft for the revision of ISO 2375
Date: 1999-11-05
Status: Committee draft
TITLE PAGE
To be provided by ITTF
© ISO/IEC CD for ISO/IEC 2375:2000 (E).CD for ISO/IEC 2375:2000 (E)
ii
Contents
Page
Foreword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Field of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
3 Normative references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
5 Registration Authority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
6 Sponsoring Authorities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
7 Registration procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
8 Review procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
9 Withdrawal procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
10 Correction procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
11 Revision procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
12 Appeal procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Annex A Registration Authority . . . . . . . . . . . . . . . . . . . . . . . . . 4
Annex B International Register . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Annex C Criteria for the allocation of ESC F s sequences. . . . . 7
Annex D The Registration Authority’s Joint Advisory
Committee (RA-JAC). . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Annex E Layout of code tables . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Annex F Flowchart showing the registration process . . . . . . 13
Annex G Example registration. . . . . . . . . . . . . . . . . . . . . . . . . . 13
Annex H Principal differences between this fourth edition
of ISO/IEC 2375 (2000-xx-xx) and the third edition
of ISO 2375 (1985-11-01). . . . . . . . . . . . . . . . . . . . . . . 14
© ISO/IEC 2000
All rights reserved. Unless otherwise specified, no part of this publication may be
reproduced or utilized in any form or by any means, electronic or mechanical,
including photocopying and microfilm, without permission in writing from the publisher.
ISO/IEC Copyright Office • Case Postale 56 • CH-1211 Genève 20 • Switzerland
Printed in Switzerland.Foreword
ISO (the International Organization for Standardization) and IEC (the
International Electrotechnical Commission) form the specialized system
for worldwide standardization. National bodies that are members of ISO
or IEC participate in the development of International Standards through
technical committees established by the respective organization to deal
with particular fields of technical activity. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international
organizations, governmental and nongovernmental, in liaison with ISO
and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a
joint technical committee, ISO/IEC JTC1. Draft International Standards
adopted by the joint technical committee are circulated to the member
bodies for voting. Publication as an International Standard requires
approval by at least 75% of the national bodies casting a vote.
International Standard ISO/IEC 2375 was prepared by Joint Technical
Committee ISO/IEC JTC1, Information technology, Subcommittee SC2,
Coded character sets.
© ISO/IEC CD for ISO/IEC 2375:2000 (E)
iii.Introduction
International standard codes (coded character sets) have been adopted
for the interchange of information between information processing
systems and within message transmission systems. However,
circumstances occur where applications require additional characters not
included in international standard codes, or require them with variant
code positions.
Provision for additional characters is made by code extension techniques
in which the additional characters or character sets are identified by
escape sequences. The procedures for code extension and the structure
and use of escape sequences are fully documented in ISO/IEC 2022,
which defines classes of escape sequences, but does not assign specific
meanings to individual escape sequences. Instead, it depends on
ISO/IEC 2375 to assign the meanings.
This International Standard specifies the procedures to be followed in
preparing and maintaining a register of specific escape-sequence
meanings. The registry associates escape sequences to specific coded
character sets. The purpose of this register is to inform all concerned of
coded character sets already developed and of the specific escape
sequences assigned to them.
The publication of the register should promote compatibility in
international information interchange and avoid duplication of effort in
developing application-oriented coded character sets. Registration
provides a standardized identifier for a coded character set but it should
not be regarded as procedure to standardize a coded character set – it is
not a standardization procedure. Nevertheless, as a matter apart from
registration the coded character set may, but need not, be the subject of
an international, national, or other standard. When such a standard is
prepared subsequent to the registration of an escape sequence, it would
be appropriate to specify the escape sequence identifying the coded
character set in the standard.
CD for ISO/IEC 2375:2000 (E) © ISO/IEC
iv.Information technology —
Procedure for registration of escape sequences and
coded character sets
COMMITTEE DRAFT © ISO/IEC CD for ISO/IEC 2375:2000 (E)
1
1 Scope
This International Standard specifies the pro-cedures
to be followed by a Registration Authority
in preparing, maintaining, and publishing a register
of escape sequences and of the coded character
sets they identify.
2 Field of application
2.1 ISO/IEC 2022 describes the escape
sequences referenced in this International
Standard, with the exception of escape sequences
described in ISO/IEC 2022 but reserved for private
use.
2.2 The use of these escape sequences
includes code extension, that is, the provision of
additional sets of characters, or of additional
control functions in accordance with ISO/IEC 2022.
2.3 An escape sequence registered in
accordance with this International Standard shall
serve as an identification of the character, the set
of characters, or the control function associated
with it in the register.
3 Normative references
The following standards contain provisions which,
through reference in this text, constitute provisions
of ISO/IEC 2375. At the time of publication, the
editions indicated were valid. All standards are
subject to revision, and parties to agreements based
on ISO/IEC 2375 are encouraged to investigate the
possibility of applying the most recent editions of the
standards listed below. Members of IEC and ISO
maintain registers of currently valid International
Standards.
ISO/IEC 646: 1991, Information processing – ISO
7-bit coded character set for information
interchange.
ISO/IEC 2022: 1994, Information technology –
Character code structure and extension
techniques.
ISO/IEC 4873: 1991, Information technology – ISO
8-bit code for information interchange – Structure
and rules for implementation.
ISO/IEC 6937: 1994, Information technology –
Coded graphic set for text communication – Latin
alphabet.
ISO/IEC 10646-1: 1993, Information technology –
Universal Multiple-Octet Coded Character Set
(UCS) – Part 1: Architecture and Basic Multilingual
Plane.
4 Definitions
4.1 combining character A member of an
identified subset of the coded character set of
ISO/IEC 10646 intended for combination with the
preceding non-combining graphic character, or
with a sequence of combining characters preceded
by a non-combining character.
4.2 code table A table showing the
characters allocated to each bit combination in a
code.
4.3 code position That part of a code table
identified by its column and row coordinates.
5 Registration Authority
5.1 The Registration Authority shall be an
organization nominated by the ISO/IEC JTC1 sub-committee
concerned with coding and appointed
by ISO to act as the Registration Authority for the
purpose of this International Standard.
5.2 The Registration Authority shall maintain
a register of the meanings assigned to escape
sequences. The contents of this register shall be
available upon request to ISO or IEC member
bodies, to liaison organizations of ISO or IEC, and
to any interested party.
5.3 The registration itself does not specify
the rules in accordance with which a character or
character set identified by an escape sequence is
to be used. Rather, the registration shall identify
the documents, for example, standards, which
specify such rules.
6 Sponsoring Authorities
6.1 Sponsoring Authorities can submit
proposals concerning the meanings of escape
sequences to the Registration Authority. For the
purposes of this International Standard,
Sponsoring Authorities are limited to the following:
• any ISO or IEC technical committee or
subcommittee;
• any group within the ISO/IEC JTC1 sub-committee
concerned with coding in.CD for ISO/IEC 2375:2000 (E) © ISO/IEC
2
information processing, appointed by the
subcommittee for purposes connected with
code extension or the use of escape
sequences;
• any member body of ISO or IEC;
• any organization having liaison status with
ISO or IEC or with any of their technical
committees or subcommittees.
NOTE: In the instance of proposals concerning single
additional control functions to be represented by the F s
escape sequence (see ISO/IEC 2022), the only
Sponsoring Authority shall be the coding subcommittee
(see annex C). This is necessary because of the
extremely limited number of escape sequences
available for that purpose.
6.2 The responsibilities of a Sponsoring
Authority shall be as follows.
6.2.1 A Sponsoring Authority shall receive
proposals concerning the meanings of escape
sequences from within its respective countries or
organizations.
6.2.2 A Sponsoring Authority shall effect such
justification or coordination of these proposals as it
may desire.
NOTE: This International Standard requires only that an
application for registration meets the requirements of
clause 7.3, but a Sponsoring Authority is free to specify
additional requirements to be met to receive its support.
6.2.3 A Sponsoring Authority shall forward
those proposals that have its support to the
Registration Authority.
6.2.4 A Sponsoring Authority shall make
known within its respective country or organization
the outcome of the registration procedure.
6.3 A Sponsoring Authority shall forward
proposals to the Registration Authority on the
prescribed form, the layout of which shall be
available from the Registration Authority. (Annex E
contains samples of the prescribed form.)
6.4 A Sponsoring Authority should, when
convenient and applicable, propose mappings of
the characters proposed in the registration to
ISO/IEC 10646.
6.5 The Sponsoring Authority is the owner
and has ultimate authority over the content of its
character sets.
7 Registration procedure
7.1 With regard to the initial assignment of
meanings to escape sequences and of subsequent
additions to the register, the responsibilities of the
Registration Authority shall be as follows.
7.2 The Registration Authority shall receive
from sponsoring authorities proposals for
meanings to be assigned to escape sequences.
7.3 The Registration Authority shall ascertain
that the proposals received are formally in accord-ance
with this International Standard, technically in
accordance with ISO/IEC 2022, and, where
applicable, with ISO/IEC 646 and ISO/IEC 4873; it
shall ascertain that the proposals received meet
the presentation practice of the the Registration
Authority.
NOTE: Complete coding systems registered need not be
in accordance with ISO/IEC 2022; see clause B.1.5. It is
the escape sequence which must be in accordance with
ISO/IEC 2022.
7.4 When required, the Registration
Authority shall indicate to the Sponsoring Authority
the changes needed to meet the requirements of
7.3 above.
7.5 The Registration Authority shall circulate
the proposals first to the members of the Joint
Advisory Committee as specified in clause 8 for a
three-month review period, and subsequently shall
circulate the proposals to the members of the
coding subcommittee for a three-month informa-tion
and comment period.
7.6 The Registration Authority shall consider
comments received and, when appropriate, shall
incorporate them in the final document.
7.7 The Registration Authority shall assign
the escape sequence.
7.8 The Registration Authority shall
promulgate to the member bodies and liaison
organizations of ISO/IEC JTC1 the meaning that
has been assigned to each escape sequence.
8 Review procedure
8.1 Review is a formal procedure by which
the Registration Authority’s Joint Advisory
Committee (RA-JAC) examines a proposed
registration for technical suitability prior to
circulation to members of the coding subcommittee
as specified in clause 7.5.
8.2 The RA-JAC shall be constituted as
specified in annex D.
8.3 The RA-JAC shall verify which proposed
coded characters mapped by the Sponsoring
Authority to ISO/IEC 10646 correspond in fact to
characters coded in ISO/IEC 10646.
8.4 The RA-JAC shall note the (U+)xxxx or.(U-)xxxxxxxx) code position and character name of
each proposed character that has a corresponding
character in ISO/IEC 10646.
NOTE 1: It is strongly recommended that the Sponsor-ing
Authority assist the RA-JAC by providing a proposed
ISO/IEC 10646 mapping, but it is not required that such
a mapping be provided.
NOTE 2: The ultimate right of character identification
and mapping, and ownership of any registered coded
character set remains with the Sponsoring Authority.
8.5 The RA-JAC shall determine whether or
not character names proposed conform to the
names of existing characters in ISO/IEC 10646.
Where a character has been identified as being
identical to a character encoded in ISO/IEC 10646,
but where the name proposed does not conform to
the name for that character in ISO/IEC 10646, the
RA-JAC may propose the amendment of that
name in order to ensure conformity.
NOTE: It is strongly recommended that the Sponsoring
Authority ensure that the names of characters mappable
to ISO/IEC 10646 characters conform to the names
used in ISO/IEC 10646. Where a character name in the
proposed registration differs fromthe character name in
ISO/IEC 10646, the Sponsoring authority shall provide
the ISO/IEC 10646 name in addition to (but not in
replacement of) the source name.
9 Withdrawal procedure
9.1 Withdrawal is a formal declaration by
which the Sponsoring Authority informs the
Registration Authority that it withdraws its support
of the proposal.
9.2 Such a declaration may, but need not, be
accompanied by a statement of the reasons for the
withdrawal.
9.3 The Registration Authority shall inform
the interested parties of the reception of such a
declaration.
9.4 After withdrawal, the registration shall
remain in the register and continue to be identified
by the allocated escape sequence.
9.5 After withdrawal, the Registration
Authority shall note in the registry that the
Sponsoring Authority withdrew the registration.
10 Correction procedure
10.1 The Registration Authority shall correct
material errors, for example typographical errors
and glyph errors, as soon as detected.
10.2 The Registration Authority shall add the
date to the corrected pages and issue the new
corrected pages of the register.
11 Revision procedure
11.1 In general, no changes to registrations
are permitted, as this would be contrary to the
principles on which the registrations are based. An
exception to this is the case of upwardly-compatible
versions as specified by ISO/IEC 2022.
11.2 The Registration Authority may excep-tionally
grant a waiver to international, govern-mental
organizations issuing internationally recog-nized
and world-wide implemented standards.
However, for these types of registrations, the first
application papers and the register shall mention
the possibility that such a registration may be
modified in future without the allocation of a new
escape sequence.
12 Appeal procedure
12.1 Appeal by a Sponsoring Authority can be
made in the following instances.
12.1.1 The Registration Authority will accept
appeals only from the Sponsoring Authority, or
from the subcommittee responsible for codes and
character sets if at least four member bodies of the
subcommittee object to a forthcoming publication
of a registration by the Registration Authority.
12.1.2 The only acceptable reasons for appeals
to the Sponsoring Authority are either
• disagreement with the Registration Authority
on whether the application meets the
requirement of clause 7.3, or
• the Registration Authority refuses to grant a
waiver according to clause 11.2.
12.2 Appeals shall be filed with the
Registration Authority by registered mail
• either within 30 days of reception of the
refusal of the Registration Authority, or
• before the end of the circulation period to
the member bodies according to clause 7.5.
NOTE 1: Simultaneously with the registered mail
posting, for expediency, the appeal can be filed
simultaneously by alternative parallel means such as
electronic mail or facsimile.
NOTE 2: See the flowchart in annex F.
12.3 Within 30 days after receipt from the
Sponsoring Authority, or after the end of the
© ISO/IEC CD for ISO/IEC 2375:2000 (E)
3.circulation period to the members fo the coding
subcommittee, the Registration Authority shall
submit the received appeal to the members of the
Joint Advisory Committee (see annex D). If the
matter cannot be resolved by the Joint Advisory
Committee the appeal shall be submitted to the P-members
of the subcommittee responsible for
codes and character sets for vote according to the
Directives for the technical work of ISO.
Annex A
(normative)
Registration Authority
A.1 The Registration Authority shall be an
organization actively participating in the work of
the subcommittee concerned with coding. In
particular a technical officer or officers of the
Registration Authority shall attend the meetings of
the subcommittee and of the working group(s)
involved with the work on ISO/IEC 646, ISO/IEC
2022, ISO/IEC 4873, ISO/IEC 8859, ISO/IEC
10646, and on other coding standards where
required.
A.2 The Registration Authority shall maintain
an up-to-date list of the parties interested in
receiving the International Register. New
registrations and any other pertinent com-munication
concerning the register shall be sent to
all persons or organizations on this list. The
Registration Authority may request from time to
time that the interested parties confirm their
continuing interest in receiving new registrations
and may drop from the list those having not
confirmed such interest.
A.3 The Registration Authority shall maintain
an explanatory document called “Practice of the
Registration Authority” available upon request to
all interested parties. It shall specify the pre-sentation
requirements for applications for
registration, for example fonts for the code table,
terminology, identification of unused positions,
etc., so as to ensure a uniform presentation of all
registrations, thus making comparison among
them easier.
CD for ISO/IEC 2375:2000 (E) © ISO/IEC
4.Annex B (normative)
International Register
B.1 Registration Documents
B.1.1 Layout
The International Register (IR) shall be issued in
loose-leaf and electronic formats. Each registration
shall comprise the following parts, as applicable,
depending on the type of registration.
NOTE: A registration should be made available in
electronic format, preferably PDF.
B.1.1.1 Cover page
The cover page shall list:
• the type of registration;
• the registration number;
• the date of registration;
• the allocated escape sequence;
• a short name for the character or character
set;
• a short description;
• the Sponsoring Authority;
• the origin or originator of the character or
character set;
• a general indication of the intended field of
application;
• as appropriate, a statement that the
Sponsoring Authority withdrew the
registration.
Where applicable, the standard(s) of which the
coded character set is a part shall be mentioned in
the short description or under “origin”.
B.1.1.2 Code tables
B.1.1.2.1 Graphic character sets
The layout of the code table shall be that given in
annex E.1, E.2, and E.3. For multiple-byte sets,
multiple code tables of 16 rows by 16 columns
shall be used (where appropriate).
B.1.1.2.2 Control functions
For C0 sets the layout of the tables shall be that
given in annex E.4. For C1 sets the two-character
escape sequences of type ESC F s shall be listed
for 7-bit coding. For 8-bit coding, the table shall be
that given in annex E.5.
B.1.1.3 Character names
B.1.1.3.1 The next pages of registrations of
graphic character sets shall list all code positions
in the code table and indicate the name of the
character allocated to each position. The next
pages of registrations of control character sets
shall list the control functions of the set indicating
their name and definition for each position.
B.1.1.3.2 Unused positions shall bear the mention
“(This position shall not be used)”. In interchange
the presence of the bit combinations correspond-ing
to these positions shall be an error condition.
NOTE: Unused columns may be omitted in the list of
character names.
B.1.1.3.3 Short notes may be added to the
registrations of graphic character sets only where
absolutely required for the understanding of the
registration.
B.1.1.3.4 “Combining characters” (as defined in
ISO/IEC 2022) shall be identified as such in a
note.
B.1.2 Use with other registered sets
If a registered set is intended for use in
combination with one or more other registered
sets, this shall be indicated.
B.1.3 Subsets and supersets
If a registered set is intentionally a subset or a
superset of one or more other registered sets, this
shall be indicated.
B.1.4 Revised standards
When a registered set is based on a standard that
is subsequently revised, an additional page to the
original registration shall be issued to identify the
new registration.
B.1.5 Complete coding systems
Registration of complete coding systems other
than those of ISO/IEC 2022 may, but need not,
comprise only the cover page. The cover page
shall indicate whether the return escape sequence
ESC 2/5 4/0 applies.
Registration of a complete coding system can be
registered only if:
© ISO/IEC CD for ISO/IEC 2375:2000 (E)
5.• the proposed registration identifies the
publicly available document that describes
the complete coding system, or
• the proposed registration includes the code
table and list of character names.
If the registration does not include the code table
and list of character names, the cover page shall
indicate where a publicly available document
describing the complete coding system can be
obtained.
NOTE: A complete coding system may be a coded
character set which is not in accordance with ISO/IEC
2022.
B.1.6 Identical sets
If a new application for registration contains a set
of characters identical with an already-registered
set, it shall not be registered, as its set will already
have been identified by an escape sequence. Two
sets are deemed to be identical if
• the number of characters is the same;
• the names of the characters are the same
according to the terminology of the Regi-stration
Authority;
• the same code positions (values) are used
for the same characters;
• both sets are of the same type, in particular
both a C0 or a C1 set;
• the definitions of control characters are
functionally equivalent (a more restricted
definition is not considered equivalent);
• graphic characters have the same geometric
shape apart from aesthetic variations be-tween
fonts;
• any “non-spacing characters” or “combining
characters” are in the same positions.
B.1.7 Repertoire
For graphic character sets, the registration
specifies only the characters of the set and their
coded representations, as shown in the code table
of the registration. It does not specify a repertoire
of characters which can be obtained by combining
the characters of the set, for example by means of
sequences of BACKSPACE and “nonspacing
characters” (for example, as defined in ISO/IEC
6937) or by means of sequences of base
characters and “combining characters” (as defined
in ISO/IEC 2022).
B.2 Allocation of final characters
Final characters shall be allocated by the Regi-stration
Authority in ascending order. This
allocation will only be made immediately prior to
publication of the registration, that is, after
completion of all procedural steps.
No final character(s) can be reserved for future
applications.
A final character once allocated to a registered
character or character set can never be re-allocated
to another character or character set.
B.3 Withdrawn registrations
When a registration has been withdrawn in
accordance with clause 9 of ISO/IEC 2375, the
Registration Authority shall inform all interested
parties by issuing a new page of the International
Register after the date of withdrawal. The
withdrawn registration shall remain in the
International Register but the new cover page shall
state that the Sponsoring Authority withdrew the
registration.
B.4 Multiple registrations for the same
application
B.4.1 Provided that an identical registration
does not exist, any Sponsoring Authority is entitled
to apply for registration of a coded character set
for a given application, for example a programming
language or a natural language, whether or not a
prior registration exists for the same application,
even if the prior registration originates from a
national or International Standard.
B.4.2 The fact that a registration for exactly the
same field of application exists cannot be a reason
for objection to the new registration.
B.5 Valid grounds for appeals
B.5.1 The valid grounds for an appeal against
a decision of the Registration Authority or a
forthcoming publication of a registration application
are listed in clause 12.1.2.
B.5.2 Appeals based on other reasons shall be
considered invalid and shall be disregarded. In
particular the following objections shall be
considered invalid:
• there is one or more registrations with
CD for ISO/IEC 2375:2000 (E) © ISO/IEC
6.identically the same field of application;
• the coded character set in the proposed
registration is incompatible with International
Standards, whether or not a character from
these International Standards is registered;
• an allegation is made that that the technical
content of the registration does not achieve
its alleged purpose;
• the “origin” field contains the name of a
commercial organization or a trade mark;
• editorial comments are rejected by the
Registration Authority.
B.5.3 A Sponsoring Authority may have
requirements for its support in addition to those of
ISO/IEC 2375. Additional requirements are the
responsibility of each Sponsoring Authority and not
by the Registration Authority.
B.6 Identification of Registration
A reference to an exsting registration should be
made by using the prefix “ISO-IR” followed by a
space and the registration number.
Examples:
ISO-IR 16
for the particular ISO/IEC 646 version for the
Portuguese language registered on 1976-12-30.
ISO-IR 48
for the set of control functions registered on 1981-
07-15.
NOTE: An exception to this would be where the origin
field specifies a national or international standard. For
example, “ISO/IEC 8859-14” is preferred to “ISO-IR
199”.
© ISO/IEC CD for ISO/IEC 2375:2000 (E)
7.8
© ISO/IEC CD for ISO/IEC 2375:2000 (E)
Annex C
(normative)
Criteria for the allocation of ESC F s
sequences
C.1 ISO/IEC 2022 provides for a very limited
number of ESC F s sequences. Priority in the
allocation of ESC F s sequences will be given to
control functions used for general code extension
purposes.
C.2 Other candidates for ESC F s repre-sentation
should be of a general nature with broad
applicability. The action of such control functions
should be largely independent of the graphic or
control character sets invoked at the time.
C.3 The control function should be logically
independent from other control functions, except if
it forms one half of a complementary pair, for
example in an ON/OFF action.
C.4 Only the subcommittee concerned with
coding shall be the Sponsoring Authority for single
control functions represented by ESC F s . Any
candidate for such allocation shall first be
submitted to this subcommittee as the Sponsoring
Authority for escape sequences other than ESC
F s .
C.5 Any proposal for a new ESC F s
sequence shall include (a) a complete definition of
the control function with an indication of the overall
environment in which it will be used, and (b)
justification for the need for a specially efficient
coding of the control function.
Annex D
(normative)
The Registration Authority’s
Joint Advisory Committee (JAC)
D.1 The subcommittee concerned with
coding shall set up a Joint Advisory Committee of
five members.
D.2 The RA-JAC shall consist of a repre-sentative
of the Registration Authority and four
other members elected by P-members of the
subcommittee. These members may be members
of the subcommittee or members of one or more
bodies with a liaison relationship to the
subcommittee. The members of the RA-JAC shall
be appointed or confirmed at each plenary meeting
of the subcommittee.
NOTE: The RA-JAC may consult relevant interested
bodies and organizations, including liaisons. Examples
of such organizations valid at the time of publication of
this International Standard are: the Unicode Consortium
and JTC1 SC2/WG2/IRG.
D.3 The task of the RA-JAC shall be as
follows.
D.3.1 The RA-JAC shall review each applica-tion
for registration according to clause 7.
D.3.2 The RA-JAC shall consider appeals
received by the Registration Authority.
D.3.3 The RA-JAC shall act as mediator
between the Registration Authority and the
appealing parties.
D.3.4 The Registration Authority shall yield if
four-fifths of the members of the RA-JAC consider
the appeal justified.
D.3.5 The RA-JAC shall, when necessary,
require the Sponsoring Authority to edit the
documents to be submitted to a vote according to
clause 10.3..Annex E
(normative)
Layout of code tables
E.1 7-bit graphic character sets: G0 set
© ISO/IEC CD for ISO/IEC 2375:2000 (E)
9
hex
0
0
0
b7
b6
b5
0
1
0
1
0
2
1
0
0
3
1
1
0
4
0
0
1
5
0
1
1
6
1
0
1
7
1
1
1
0 0 0 0
b4 b3 b2 b1
0
1 0 1 0 0
2 1 0 0 0
3 1 1 0 0
4 0 0 0 1
5 0 1 0 1
6 1 0 0 1
7 1 1 0 1
8 0 0 1 0
9 0 1 1 0
10 1 0 1 0
11 1 1 1 0
12 0 0 1 1
13 0 1 1 1
14 1 0 1 1
15 1 1 1 1
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
7 6 5 4 3 2 1 0.E.2 7-bit graphic character sets: G1 set
CD for ISO/IEC 2375:2000 (E) © ISO/IEC
10
hex
b7
b6
b5
0
0
0
0
1
0
1
0
2
1
0
0
3
1
1
0
4
0
0
1
5
0
1
1
6
1
0
1
7
1
1
1
0 0 0 0
b4 b3 b2 b1
0
1 0 1 0 0
2 1 0 0 0
3 1 1 0 0
4 0 0 0 1
5 0 1 0 1
6 1 0 0 1
7 1 1 0 1
8 0 0 1 0
9 0 1 1 0
10 1 0 1 0
11 1 1 1 0
12 0 0 1 1
13 0 1 1 1
14 1 0 1 1
15 1 1 1 1
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
7 6 5 4 3 2 1 0.hex
© ISO/IEC CD for ISO/IEC 2375:2000 (E)
11
E.3 8-bit graphic character sets:
00
0
0
0 b8
b7
b6
b5
0
01
0
1
0
0
02
1
0
0
0
03
1
1
0
0
04
0
0
0
1
05
0
1
0
1
06
1
0
0
1
07
1
1
0
1
08
0
0
1
0
09
0
1
1
0
10
1
0
1
0
11
1
1
1
0
12
0
0
1
1
13
0
1
1
1
14
1
0
1
1
15
1
1
1
1
00 0 0 0
b4 b3 b2 b1
0
01 0 1 0 0
02 1 0 0 0
03 1 1 0 0
04 0 0 0 1
05 0 1 0 1
06 1 0 0 1
07 1 1 0 1
08 0 0 1 0
09 0 1 1 0
10 1 0 1 0
11 1 1 1 0
12 0 0 1 1
13 0 1 1 1
14 1 0 1 1
15 1 1 1 1
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
F E D C B A 9 8 7 6 5 4 3 2 1 0.hex
b7
b6
b5
0
0
0
0
1
0
1
0
0 0 0 0
b4 b3 b2 b1
0
1 0 1 0 0
2 1 0 0 0
3 1 1 0 0
4 0 0 0 1
5 0 1 0 1
6 1 0 0 1
7 1 1 0 1
8 0 0 1 0
9 0 1 1 0
10 1 0 1 0
11 1 1 1 0
12 0 0 1 1
13 0 1 1 1
14 1 0 1 1
15 1 1 1 1
1 0
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
hex
b7
b6
b5
00
0
0
0
01
0
1
0
b8 0 0
00 0 0 0
b4 b3 b2 b1
0
01 0 1 0 0
02 1 0 0 0
03 1 1 0 0
04 0 0 0 1
05 0 1 0 1
06 1 0 0 1
07 1 1 0 1
08 0 0 1 0
09 0 1 1 0
10 1 0 1 0
11 1 1 1 0
12 0 0 1 1
13 0 1 1 1
14 1 0 1 1
15 1 1 1 1
1 0
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
E.4 7- and 8-bit C0 control function sets
© ISO/IEC CD for ISO/IEC 2375:2000 (E)
12.13
E.5 C1 control function sets
CD for ISO/IEC 2375:2000 (E) © ISO/IEC
hex
b7
b6
b5
08
0
0
0
09
0
1
0
b8 1 1
00 0 0 0
b4 b3 b2 b1
0
01 0 1 0 0
02 1 0 0 0
03 1 1 0 0
04 0 0 0 1
05 0 1 0 1
06 1 0 0 1
07 1 1 0 1
08 0 0 1 0
09 0 1 1 0
10 1 0 1 0
11 1 1 1 0
12 0 0 1 1
13 0 1 1 1
14 1 0 1 1
15 1 1 1 1
9 8
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F.Annex F
(informative)
Flowchart showing the registration process
(to be supplied)
Annex G
(informative)
Example registration
See following pages.
CD for ISO/IEC 2375:2000 (E) © ISO/IEC
14.© ISO/IEC CD for ISO/IEC 2375:2000 (E)
15
DESCRIPTION
A set of 47 graphic characters for use for Georgian and related
languages and Caucasian linguistics.
This registration gives UCS mappings where available. Character
names presented here are the name as it appears in ISO 10586;
these are italicized where the corresponding name appears
differently in ISO/IEC 10646 and the UCS name is given in
parentheses.
TYPE: 47-character graphic
character set
REGISTRATION NUMBER: xxx
DATE OF REGISTRATION:
ESCAPE SEQUENCE G0: ESC 02/08 02/01 F
G1: ESC 02/09 02/01 F
G2: ESC 02/10 02/01 F
G3: ESC 02/11 02/01 F
C0:
C1:
NAME
Georgian alphabet coded character set for bibliographic
information interchange
SPONSOR
NSAI (National Standards Authority of Ireland)
ORIGIN:
National Library of Ireland character set Georgian-B
FIELD OF UTILIZATION
Communication and processing of text for bibliographic citations,
including their annotations, in Georgian and related languages in
the Georgian ( mxedruli) script..CD for ISO/IEC 2375:2000 (E) © ISO/IEC
16
hex
b7
b6
b5
0
0
0
0
1
0
1
0
2
1
0
0
3
1
1
0
4
0
0
1
5
0
1
1
6
1
0
1
7
1
1
1
0 0 0 0
b4 b3 b2 b1
0
1 0 1 0 0
2 1 0 0 0
3 1 1 0 0
4 0 0 0 1
5 0 1 0 1
6 1 0 0 1
7 1 1 0 1
8 0 0 1 0
9 0 1 1 0
10 1 0 1 0
11 1 1 1 0
12 0 0 1 1
13 0 1 1 1
14 1 0 1 1
15 1 1 1 1
à
ð
á
ñ
â
ò
ã
ó
Ï
ä
ô
å
õ
æ
ö
¾
÷
ç
ø
è
ù
é
ú
ê
û
ë
ü Í
.
ÿ ì
¿
í
ý î
þ
Ù
ß
Ì
¹
»
ï
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
7 6 5 4 3 2 1 0
¼
â
ì
2
½.© ISO/IEC CD for ISO/IEC 2375:2000 (E)
04/00
04/01
04/02
04/03
04/04
04/05
04/06
04/07
04/08
04/09
04/10
04/11
04/12
04/13
04/14
04/15
05/00
05/01
05/02
05/03
05/04
05/05
05/06
05/07
05/08
05/09
05/10
05/11
05/12
05/13
05/14
05/15
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
GEORGIAN FULL STOP (ARMENIAN FULL STOP)
GEORGIAN COMMA (GREEK ANO TELEIA)
GEORGIAN PARAGRAPH SEPARATOR
GEORGIAN LETTER AN
GEORGIAN LETTER BAN
GEORGIAN LETTER GAN
GEORGIAN LETTER DON
GEORGIAN LETTER EN
GEORGIAN LETTER VIN
GEORGIAN LETTER ZEN
GEORGIAN LETTER HE
GEORGIAN LETTER TAN
GEORGIAN LETTER IN
GEORGIAN LETTER KAN
GEORGIAN LETTER LAS
GEORGIAN LETTER MAN
GEORGIAN LETTER NAR
GEORGIAN LETTER HIE
GEORGIAN LETTER ON
Pos. Name Note
U+0589
U+0387
U+10FB
U+10D0
U+10D1
U+10D2
U+10D3
U+10D4
U+10D5
U+10D6
U+10F1
U+10D7
U+10D8
U+10D9
U+10DA
U+10DB
U+10DC
U+10F2
U+10DD.CD for ISO/IEC 2375:2000 (E) © ISO/IEC
06/00
06/01
06/02
06/03
06/04
06/05
06/06
06/07
06/08
06/09
06/10
06/11
06/12
06/13
06/14
06/15
07/00
07/01
07/02
07/03
07/04
07/05
07/06
07/07
07/08
07/09
07/10
07/11
07/12
07/13
07/14
07/15
GEORGIAN LETTER PAR
GEORGIAN LETTER ZHAR
GEORGIAN LETTER RAE
GEORGIAN LETTER SAN
GEORGIAN LETTER TAR
GEORGIAN LETTER UN
GEORGIAN LETTER WE
GEORGIAN LETTER PHAR
GEORGIAN LETTER KHAR
GEORGIAN LETTER GHAN
GEORGIAN LETTER QAR
GEORGIAN LETTER SHIN
GEORGIAN LETTER CHIN
GEORGIAN LETTER CAN
GEORGIAN LETTER JIL
GEORGIAN LETTER CIL
GEORGIAN LETTER CHAR
GEORGIAN LETTER XAN
GEORGIAN LETTER HAR
GEORGIAN LETTER JAN (GEORGIAN LETTER JHAN)
GEORGIAN LETTER HAE
GEORGIAN LETTER HOE
GEORGIAN LETTER FI
GEORGIAN LETTER SHVA
GEORGIAN LETTER ELIFI
GEORGIAN LETTER TURNED GAN
MODIFIER LETTER GEORGIAN NAR
GEORGIAN LETTER AIN
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
(This position shall not be used)
Note
U+10DE
U+10DF
U+10E0
U+10E1
U+10E2
U+10E3
U+10F3
U+10E4
U+10E5
U+10E6
U+10E7
U+10E8
U+10E9
U+10EA
U+10EB
U+10EC
U+10ED
U+10EE
U+10F4
U+10EF
U+10F0
U+10F5
U+10F6
Pos. Name.Annex H
(informative)
Principal differences between this fourth
edition of ISO/IEC 2375 (2000-xx-xx) and the
third edition of ISO 2375 (1985-11-01)
• Clauses have been renumbered.
• A new clause 8 “Review procedure” has
been added.
• Clause 12 has been consolidated and
simplified (but has the same content).
• Layouts of the code tables are no longer
specified in annex B by reference to external
standards but are instead presented in
annex E.
• The term “non-spacing character” has been
updated to the term “combining character” in
B.1.1.3, with reference to ISO/IEC 2022.
• The possibility to attach code tables and
character names to registrations of complete
coding systems has been added to B.1.5. In
such cases a publicly-available document,
describing the coding system, is not now
needed.
CD for ISO/IEC 2375:2000 (E) © ISO/IEC
19