Network Working Group R. McGowan
Request for Comments: 3718 Unicode
Category: Informational February 2004
Network Working Group R. McGowan
Request for Comments: 3718 Unicode
Category: Informational February 2004
A Summary of Unicode Consortium Procedures, Policies, Stability, and Public Access
Unicode联盟程序、政策、稳定性和公共访问摘要
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
Abstract
摘要
This memo describes various internal workings of the Unicode Consortium for the benefit of participants in the IETF. It is intended solely for informational purposes. Included are discussions of how the decision-making bodies of the Consortium work and their procedures, as well as information on public access to the character encoding & standardization processes.
本备忘录描述了Unicode联盟的各种内部工作，以利于IETF的参与者。它仅用于提供信息。其中包括对联合体决策机构如何工作及其程序的讨论，以及关于公众获取字符编码和标准化过程的信息。
This memo describes various internal workings of the Unicode Consortium for the benefit of participants in the IETF. It is intended solely for informational purposes. Included are discussions of how the decision-making bodies of the Consortium work and their procedures, as well as information on public access to the character encoding & standardization processes.
本备忘录描述了Unicode联盟的各种内部工作，以利于IETF的参与者。它仅用于提供信息。其中包括对联合体决策机构如何工作及其程序的讨论，以及关于公众获取字符编码和标准化过程的信息。
The Unicode Consortium is a corporation. Legally speaking, it is a "California Nonprofit Mutual Benefit Corporation", organized under section 501 C(6) of the Internal Revenue Service Code of the United States. As such, it is a "business league" not focussed on profiting by sales or production of goods and services, but neither is it formally a "charitable" organization. It is an alliance of member companies whose purpose is to "extend, maintain, and promote the Unicode Standard". To this end, the Consortium keeps a small office, a few editorial and technical staff, World Wide Web presence, and mail list presence.
Unicode联盟是一家公司。从法律上讲，它是一家“加州非营利性互惠公司”，根据《美国国税局法典》第501 C（6）节组建。因此，它是一个“商业联盟”，不专注于通过销售或生产商品和服务获利，但也不是一个正式的“慈善”组织。它是一个成员公司联盟，其目的是“扩展、维护和推广Unicode标准”。为此，该联盟保留了一个小型办公室、一些编辑和技术人员、万维网和邮件列表。
The corporation is presided over by a Board of Directors who meet annually. The Board is comprised of individuals who are elected annually by the full members for three-year terms. The Board appoints Officers of the corporation to run the daily operations.
公司由董事会主持，董事会每年召开一次会议。董事会由每年由正式成员选举产生的个人组成，任期三年。董事会任命公司的高级职员负责日常运营。
Membership in the Consortium is open to "all corporations, other business entities, governmental agencies, not-for-profit organizations and academic institutions" who support the Consortium's purpose. Formally, one class of voting membership is recognized, and dues-paying members are typically for-profit corporations, research and educational institutions, or national governments. Each such full member sends representatives to meetings of the Unicode Technical Committee (see below), as well as to a brief annual Membership meeting.
联合体的成员资格向支持联合体宗旨的“所有公司、其他商业实体、政府机构、非营利组织和学术机构”开放。从形式上讲，一类投票会员是公认的，缴纳会费的会员通常是营利性公司、研究和教育机构或国家政府。每个正式成员都派代表出席Unicode技术委员会的会议（见下文）以及简短的年度成员会议。
The Unicode Technical Committee (UTC) is the technical decision making body of the Consortium. The UTC inherited the work and prior decisions of the Unicode Working Group (UWG) that was active prior to formation of the Consortium in January 1991.
Unicode技术委员会（UTC）是联合体的技术决策机构。UTC继承了Unicode工作组（UWG）的工作和先前的决定，该工作组在1991年1月成立联合体之前是活跃的。
Formally, the UTC is a technical body instituted by resolution of the board of directors. Each member appoints one principal and one or two alternate representatives to the UTC. UTC representatives frequently do, but need not, act as the ordinary member representatives for the purposes of the annual meeting.
正式而言，UTC是由董事会决议设立的技术机构。每名成员向UTC任命一名负责人和一名或两名候补代表。UTC代表经常（但无需）作为普通成员代表参加年会。
The UTC is presided over by a Chair and Vice-Chair, appointed by the Board of Directors for an unspecified term of service.
UTC由董事会任命的主席和副主席主持，任期未指定。
The UTC meets 4 to 5 times a year to discuss proposals, additions, and various other technical topics. Each meeting lasts 3 to 4 full days. Meetings are held in locations decided upon by the membership, frequently in the San Francisco Bay Area. There is no fee for participation in UTC meetings. Agendas for meetings are not generally posted to any public forum, but meeting dates, locations, and logistics are posted well in advance on the "Unicode Calendar of Events" web page.
UTC每年召开4至5次会议，讨论提案、补充内容和各种其他技术主题。每次会议持续3至4整天。会议在成员国决定的地点举行，经常在旧金山湾地区举行。参加UTC会议不收取任何费用。会议议程通常不会发布到任何公共论坛，但会议日期、地点和后勤安排会提前发布在“Unicode活动日历”网页上。
At the discretion of the UTC chair, meetings are open to participation of member and liaison organizations, and to observation by others. The minutes of meetings are also posted publicly on the "UTC Minutes" page of the Unicode Web site.
UTC主席可自行决定，成员和联络组织可参加会议，其他组织也可观察会议。会议记录还公开发布在Unicode网站的“UTC会议记录”页面上。
All UTC meetings are held jointly with the INCITS Technical Committee L2, the body responsible for Character Code standards in the United States. They constitute "ad hoc" meetings of the L2 body and are
所有UTC会议均与INCITS技术委员会L2（负责美国字符代码标准的机构）联合举行。它们构成L2机构的“特别”会议，并且是
usually followed by a full meeting of the L2 committee. Further information on L2 is available on the official INCITS web page.
通常随后是L2委员会的全体会议。有关L2的更多信息，请访问INCITS官方网页。
The formal procedures of the UTC are publicly available in a document entitled "UTC Procedures", available from the Consortium, and on the Unicode web site.
UTC的正式程序在一份名为“UTC程序”的文件中公开，该文件可从联合体获得，也可在Unicode网站上获得。
Despite the invocation of Robert's Rules of Order, UTC meetings are conducted with relative informality in view of the highly technical nature of most discussions. Meetings focus on items from a technical agenda organized and published by the UTC Chair prior to the meeting. Technical items are usually proposals in one of the following categories:
尽管引用了Robert的《议事规则》，但鉴于大多数讨论的高度技术性，UTC会议还是以相对非正式的方式进行的。会议重点讨论UTC主席在会议之前组织和发布的技术议程中的项目。技术项目通常是以下类别之一的建议书：
1. Addition of new characters (whole scripts, additions to existing scripts, or other characters)
1. 添加新字符（整个脚本、添加到现有脚本或其他字符）
2. Preparation and Editing of Technical Reports and Standards
2. 编制和编辑技术报告和标准
3. Changes in the semantics of specific characters
3. 特定字符语义的变化
4. Extensions to the encoding architecture and forms of use
4. 编码体系结构和使用形式的扩展
Note: There may also be changes to the architecture, character properties, or semantics. Such changes are rare, and are always constrained by the "Unicode Stability Policies" posted on the Unicode web site. Significant changes are undertaken in consultation with liaison organizations, such as W3C and IETF, which have standards that may be affected by such changes. See sections 5 and 6 below.
注意：架构、字符属性或语义也可能发生更改。这种变化很少见，而且总是受到Unicode网站上发布的“Unicode稳定性策略”的约束。重大变更是与联络组织协商进行的，如W3C和IETF，这些组织的标准可能会受到此类变更的影响。见下文第5和第6节。
Typical outputs of the UTC are:
UTC的典型输出为：
1. The Unicode Standard, major and minor versions (including the Unicode Character Database)
1. Unicode标准、主要和次要版本（包括Unicode字符数据库）
2. Unicode Technical Reports
2. Unicode技术报告
3. Stand-alone Unicode Technical Standards
3. 独立Unicode技术标准
4. Formal resolutions
4. 正式决议
5. Liaison statements and instructions to the Unicode liaisons to other organizations.
5. 与其他组织联络的Unicode联络声明和指示。
For each technical item on the meeting agenda, the general process is as follows:
对于会议议程上的每个技术项目，一般流程如下：
1. Introduction by the topic sponsor
1. 专题发起人介绍
2. Proposals and discussion
2. 建议和讨论
3. Consensus statements or formal motions
3. 协商一致声明或正式动议
4. Assignment of formal actions to implement decisions
4. 分配正式行动以执行决策
Technical topics of any complexity never proceed from initial proposal to final ratification or adoption into the standard in the course of one UTC meeting. The UTC members and presiding officers are aware that technical changes to the standard have broad consequences to other standards, implementers, and end-users of the standard. Input from other organizations and experts is often vital to the understanding of various proposals and for successful adoption into the standard.
在一次UTC会议期间，任何复杂的技术主题都不会从最初的提案到最终批准或通过标准。UTC成员和主持会议的官员都知道，本标准的技术变更会对本标准的其他标准、实施者和最终用户产生广泛的影响。其他组织和专家的投入对于理解各种提案和成功采用本标准通常至关重要。
Technical topics are decided in UTC through the use of formal motions, either taken in meetings, or by means of thirty-day letter ballots. Formal UTC motions are of two types:
技术主题在UTC中通过正式动议决定，无论是在会议上还是通过30天的信函投票。正式UTC运动有两种类型：
1. Simple motions
1. 简单动作
2. Precedents
2. 先例
Simple motions may pass with a simple majority constituting more than 50 percent of the qualified voting members; or by a special majority constituting two-thirds or more of the qualified voting members.
简单的动议可以由超过50%的合格有表决权成员的简单多数通过；或由三分之二或三分之二以上的合格投票成员组成的特别多数。
Precedents are defined, according to the UTC Procedures as either
根据UTC程序，先例定义如下：
(A) an existing Unicode Policy, or
（A） 现有的Unicode策略，或
(B) an explicit precedent.
（B） 明确的先例。
Precedents must be passed or overturned by a special majority.
先例必须以特别多数通过或推翻。
Examples of implicit precedents include:
隐含先例的例子包括：
1. Publication of a character in the standard
1. 标准中字符的发布
2. Published normative character properties
2. 已发布的规范性字符属性
3. Algorithms required for formal conformance
3. 形式一致性所需的算法
An Explicit Precedent is a policy, procedure, encoding, algorithm, or other item that is established by a separate motion saying (in effect) that a particular prior motion establishes a precedent.
明确的先例是一项政策、程序、编码、算法或其他项目，由一项单独的动议（实际上）确定，该动议表明一项特定的先前动议确立了先例。
A proposal may be passed either by a formal motion and vote, or by consensus. If there is broad agreement as to the proposal, and no member wishes to force a vote, then the proposal passes by consensus and is recorded as such in the minutes.
提案可以通过正式动议和表决或协商一致通过。如果对该提案有广泛的一致意见，并且没有成员希望强制进行表决，则该提案以协商一致方式通过，并记录在会议记录中。
Because the Unicode Standard is continually evolving in an attempt to reach the ideal of encoding "all the world's scripts", new characters will constantly be added. In this sense, the standard is unstable: in the standard's useful lifetime, there may never be a final point at which no more characters are added. Realizing this, the Consortium has adopted certain policies to promote and maintain stability of the characters that are already encoded, as well as laying out a Roadmap to future encodings.
由于Unicode标准在不断发展，以达到编码“世界上所有的脚本”的理想，新字符将不断添加。从这个意义上讲，标准是不稳定的：在标准的有效生命周期中，可能永远不会有最后一点不再添加字符。认识到这一点，该联盟采取了某些政策来促进和维护已编码字符的稳定性，并制定了未来编码的路线图。
The overall policies of the Consortium with regard to encoding stability, as well as other issues such as privacy, are published on a "Unicode Consortium Policies" web page. Deliberations and encoding proposals in the UTC are bound by these policies.
联合体关于编码稳定性的总体政策以及隐私等其他问题发布在“Unicode联合体政策”网页上。UTC的审议和编码建议受这些政策的约束。
The general effect of the stability policies may be stated in this way: once a character is encoded, it will not be moved or removed and its name will not be changed. Any of those actions has the potential for causing obsolescence of data, and they are not permitted. The canonical combining class and decompositions of characters will not be changed in any way that affects normalization. In this sense, normalization, such as that used for International Domain Naming and "early normalization" for use on the World Wide Web, is fixed and stable for every character at the time that character is encoded. (Any changes that are undertaken because of outright errors in properties or decompositions are dealt with by means of an adjunct data file so that normalization stability can still be maintained by those who need it.)
稳定性策略的一般效果可以这样表述：一旦对字符进行编码，它将不会被移动或删除，其名称也不会更改。任何这些行为都有可能导致数据过时，因此是不允许的。字符的规范组合类和分解不会以任何影响规范化的方式进行更改。从这个意义上讲，标准化（例如用于国际域名命名的标准化和用于万维网的“早期标准化”）在编码字符时对每个字符都是固定和稳定的。（由于属性或分解中的彻底错误而进行的任何更改都通过附加数据文件进行处理，以便需要的人仍然可以保持规范化稳定性。）
Once published, each version of the Unicode Standard is absolutely stable and will never be changed retroactively. Implementations or specifications that refer to a specific version of the Unicode Standard can rely upon this stability. If future versions of such implementations or specifications upgrade to a future version of the Unicode Standard, then some changes may be necessary.
一旦发布，Unicode标准的每个版本都是绝对稳定的，并且永远不会进行追溯性更改。引用Unicode标准特定版本的实现或规范可以依赖于这种稳定性。如果此类实现或规范的未来版本升级到Unicode标准的未来版本，则可能需要进行一些更改。
Property values of characters, such as directionality for the Unicode Bidi algorithm, may be changed between versions of the standard in some circumstances. As less-well documented characters and scripts are encoded, the exact character properties and behavior may not be well known at the time the characters are first encoded. As more experience is gathered in implementing the newly encoded characters, adjustments in the properties may become necessary. This re-working is kept to a minimum. New and old versions of the relevant property tables are made available on the Consortium's web site.
在某些情况下，字符的属性值（如Unicode Bidi算法的方向性）可能会在标准版本之间更改。由于对文档较少的字符和脚本进行编码，因此在首次对字符进行编码时，可能不知道确切的字符属性和行为。随着在实现新编码字符方面积累更多的经验，可能需要对属性进行调整。这种重新工作保持在最低限度。相关财产表的新版本和旧版本可在联合体的网站上查阅。
Normative and some informative data about characters is kept in the Unicode Character Database (UCD). The structure of many of these property values will not be changed. Instead, when new properties are defined, the Consortium adds new files for these properties, so as not to affect the stability of existing implementations that use the values and properties defined in the existing formats and files. The latest version of the UCD is available on the Consortium web site via the "Unicode Data" heading.
有关字符的规范性和一些信息性数据保存在Unicode字符数据库（UCD）中。其中许多属性值的结构将不会更改。相反，在定义新属性时，联合体会为这些属性添加新文件，以免影响使用现有格式和文件中定义的值和属性的现有实现的稳定性。最新版本的UCD可通过“Unicode数据”标题在联合体网站上获得。
Note on data redistribution: Unlike the situation with IETF documents, some parts of the Unicode Character Database may have restrictions on their verbatim redistribution with source-code products. Users should read the notices in files they intend to use in such products. The information contained in the UCD may be freely used to create derivative works (such as programs, compressed data files, subroutines, data structures, etc.) that may be redistributed freely, but some files may not be redistributable verbatim. Such restrictions on Unicode data files are never meant to prohibit or control the use of the data in products, but only to help ensure that users retrieve the latest official releases of data files when using the data in products.
关于数据再分配的注意事项：与IETF文档的情况不同，Unicode字符数据库的某些部分可能会对源代码产品的逐字再分配进行限制。用户应阅读他们打算在此类产品中使用的文件中的通知。UCD中包含的信息可自由用于创建衍生作品（如程序、压缩数据文件、子程序、数据结构等），这些作品可自由重新分发，但某些文件可能无法逐字重新分发。对Unicode数据文件的此类限制决不是为了禁止或控制产品中数据的使用，而是为了帮助确保用户在使用产品中的数据时检索数据文件的最新官方版本。
The character repertoire, names, and general architecture of the Unicode Standard are identical to the parallel international standard ISO/IEC 10646. ISO/IEC 10646 only contains a small fraction of the semantics, properties and implementation guidelines supplied by the Unicode Standard and associated technical standards and reports. Implementations conformant to Unicode are conformant to ISO/IEC 10646.
Unicode标准的字符表、名称和通用体系结构与并行国际标准ISO/IEC 10646相同。ISO/IEC 10646仅包含Unicode标准及相关技术标准和报告提供的语义、属性和实施指南的一小部分。符合Unicode的实现符合ISO/IEC 10646。
ISO/IEC 10646 is maintained by the committee ISO/IEC JTC1/SC2/WG2. The WG2 committee is composed of national body representatives to ISO. Details on the ISO organization may be found on the official web site of the International Organization for Standardization (ISO).
ISO/IEC 10646由ISO/IEC JTC1/SC2/WG2委员会维护。WG2委员会由ISO的国家机构代表组成。有关ISO组织的详细信息，请访问国际标准化组织（ISO）的官方网站。
Details and history of the relationship between ISO/IEC JTC1/SC2/WG2 and Unicode, Inc. may be found in Appendix C of The Unicode Standard. (A PDF rendition of the most recent printed edition of the Unicode Standard can be found on the Unicode web site.)
有关ISO/IEC JTC1/SC2/WG2与Unicode，Inc.之间关系的详细信息和历史记录，请参见Unicode标准的附录C。（Unicode网站上提供了Unicode标准最新印刷版的PDF格式副本。）
WG2 shares with UTC the policies regarding stability: WG2 neither removes characters nor changes their names once published. Changes in both standards are closely tracked by the respective committees, and a very close working relationship is fostered to maintain synchronization between the standards.
WG2与UTC共享有关稳定性的政策：WG2在发布后既不会删除字符，也不会更改其名称。各委员会密切跟踪两个标准的变化，并建立了非常密切的工作关系，以保持标准之间的同步。
The Unicode Collation Algorithm (UCA) is one of a small set of other independent standards defined and maintained by UTC. It is not, properly speaking, part of the Unicode Standard itself, but is separately defined in Unicode Technical Standard #10 (UTS #10). There is no conformance relationship between the two standards, except that conformance to a specific base version of the Unicode Standard (e.g., 4.0) is specified in a particular version of a UTS. The collation algorithm specified in UTS #10 is conformant to ISO/IEC 14651, maintained by ISO/IEC JTC1/SC2, and the two organizations maintain a close relationship. Beyond what is specified in ISO/IEC 14651, the UCA contains additional constraints on collation, specifies additional options, and provides many more implementation guidelines.
Unicode排序算法（UCA）是UTC定义和维护的一小部分其他独立标准之一。正确地说，它不是Unicode标准本身的一部分，而是在Unicode技术标准10（UTS 10）中单独定义的。这两个标准之间没有一致性关系，除非在UTS的特定版本中指定了与Unicode标准的特定基本版本（例如4.0）的一致性。UTS#10中规定的排序算法符合ISO/IEC 14651，由ISO/IEC JTC1/SC2维护，两个组织保持着密切的关系。除了ISO/IEC 14651中规定的内容之外，UCA还包含关于排序的附加约束，指定了附加选项，并提供了更多的实施指南。
Changes to The Unicode Standard are of two types: architectural changes, and character additions.
对Unicode标准的更改有两种类型：体系结构更改和字符添加。
Most architectural changes do not affect ISO/IEC 10646, for example, the addition of various character properties to Unicode. Those architectural changes that do affect both standards, such as additional UTF formats or allocation of planes, are very carefully coordinated by the committees. As always, on the UTC side, architectural changes that establish precedents are carefully monitored and the above-described rules and procedures are followed.
大多数架构更改不会影响ISO/IEC 10646，例如，在Unicode中添加各种字符属性。那些确实影响这两个标准的架构变更，例如额外的UTF格式或飞机分配，由委员会非常仔细地协调。与往常一样，在UTC方面，对建立先例的架构更改进行仔细监控，并遵循上述规则和程序。
Additional characters for inclusion in the The Unicode Standard must be approved both by the UTC and by WG2. Proposals for additional characters enter the standards process in one of several ways: through...
Unicode标准中包含的其他字符必须得到UTC和WG2的批准。增加字符的建议通过以下几种方式之一进入标准流程：通过。。。
1. a national body member of WG2
1. WG2的国家机构成员
2. a member company or associate of UTC
2. UTC的成员公司或合伙人
3. directly from an individual "expert" contributor
3. 直接来自个人“专家”贡献者
The two committees have jointly produced a "Proposal Summary Form" that is required to accompany all additional character proposals. This form may be found online at the WG2 web site, and on the Unicode web site along with information about "Submitting New Characters or Scripts". Instructions for submitting proposals to UTC may likewise be found online.
这两个委员会联合制作了一份“提案汇总表”，要求随附所有其他提案。此表格可在线在WG2网站和Unicode网站上找到，以及有关“提交新字符或脚本”的信息。向UTC提交建议书的说明也可以在网上找到。
Often, submission of proposals to both committees (UTC and WG2) is simultaneous. Members of UTC also frequently forward to WG2 proposals that have been initially reviewed by UTC.
通常，同时向两个委员会（UTC和WG2）提交提案。UTC成员还经常转发UTC最初审查过的WG2提案。
In general, a proposal that is submitted to UTC before being submitted to WG2 passes through several stages:
通常，在提交给WG2之前提交给UTC的提案会经过几个阶段：
1. Initial presentation to UTC
1. 向UTC的初始演示
2. Review and re-drafting
2. 审查和重新起草
3. Forwarding to WG2 for consideration
3. 转交第二工作组审议
4. Re-drafting for technical changes
4. 技术变更的重新起草
5. Balloting for approval in UTC
5. UTC中的投票批准
6. Re-forwarding and recommendation to WG2
6. 向第二工作组转发和推荐
7. At least two rounds of international balloting in ISO
7. 国际标准化组织至少两轮国际投票
About two years are required to complete this process. Initial proposals most often do not include sufficient information or justification to be approved. These are returned to the submitters with comments on how the proposal needs to be amended or extended. Repertoire addition proposals that are submitted to WG2 before being submitted to UTC are generally forwarded immediately to UTC through committee liaisons. The crucial parts of the process (steps 5 through 7 above) are never short-circuited. A two-thirds majority in UTC is required for approval at step 5.
完成这一过程大约需要两年时间。最初的提案通常不包含足够的信息或理由以供批准。这些文件将返回给提交人，并对提案需要如何修改或扩展提出意见。在提交给UTC之前提交给WG2的补充曲目提案通常会通过委员会联络人立即转发给UTC。过程的关键部分（上述步骤5至7）绝不会短路。第5步的批准需要UTC三分之二多数票。
Proposals for additional scripts are required to be coordinated with relevant user communities. Often there are ad-hoc subcommittees of UTC or expert mail list participants who are responsible for actually drafting proposals, garnering community support, or representing user communities.
需要与相关用户社区协调额外脚本的提案。通常，UTC或专家邮件列表参与者的特设小组委员会负责实际起草提案、获得社区支持或代表用户社区。
The rounds of international balloting in step 7 have participation both by UTC and WG2, though UTC does not directly vote in the ISO process.
步骤7中的几轮国际投票均由UTC和WG2参与，但UTC不直接在ISO过程中投票。
Occasionally a proposal approved by one body is considered too immature for approval by the other body, and may be blocked de-facto by either of the two. Only after both bodies have approved the additional characters do they proceed to the rounds of international balloting. (The first round is a draft international standard during which some changes may occur, the second round is final approval during which only editorial changes are made.)
有时，一个机构批准的提案被认为太不成熟，无法得到另一个机构的批准，并且可能被两个机构中的任何一个事实上阻止。只有在两个机构都批准增加的字符后，它们才能进行国际投票。（第一轮是国际标准草案，在此期间可能会发生一些更改，第二轮是最终批准，在此期间仅进行编辑性更改。）
This process assures that proposals for additional characters are mature and stable by the time they appear in a final international ballot.
这一过程确保在最后的国际投票中，增选角色的提案是成熟和稳定的。
While Unicode, Inc. is a membership organization, and the final say in technical matters rests with UTC, the process is quite open to public input and scrutiny of processes and proposals. There are many influential individual experts and industry groups who are not formally members, but whose input to the process is taken seriously by UTC.
虽然Unicode，Inc.是一个会员组织，技术事宜的最终决定权属于UTC，但该过程对公众的输入和过程及提案的审查是相当开放的。有许多有影响力的个人专家和行业团体，他们不是正式成员，但UTC认真对待他们对过程的投入。
Internally, UTC maintains a mail list called the "Unicore" list, which carries traffic related to meetings, technical content of the standard, and so forth. Members of the list are UTC representatives; employees and staff of member organizations (such as the Research Libraries Group); individual liaisons to and from other standards bodies (such as WG2 and IETF); and invited experts from institutions such as the Library of Congress and some universities. Subscription to the list for external individuals is subject to "sponsorship" by the corporate officers.
在内部，UTC维护一个名为“Unicore”列表的邮件列表，其中包含与会议、标准技术内容等相关的流量。名单中的成员为UTC代表；员工和成员组织（如研究图书馆组）的工作人员；与其他标准机构（如WG2和IETF）的个人联络；并邀请了来自国会图书馆和一些大学等机构的专家。外部个人订阅该名单须由公司高管“赞助”。
Unicode, Inc. also maintains a public discussion list called the "Unicode" list. Subscription is open to anyone, and proceedings of the "Unicode" mail list are publicly archived. Details are on the Consortium web site under the "Mail Lists" heading.
Unicode，Inc.还维护一个名为“Unicode”列表的公共讨论列表。订阅是对任何人开放的，“Unicode”邮件列表的会议记录是公开存档的。详细信息在联合体网站的“邮件列表”标题下。
Technical proposals for changes to the standard are posted to both of these mail lists on a regular basis. Discussion on the public list may result in a written proposal being generated for a later UTC meeting. Technical issues and other standardization "events" of any significance, such as beta releases and availability of draft documents, are announced and then discussed in this public forum, well before standardization is finalized. From time to time, the UTC also publishes on the Consortium web site "Public Review Issues" to gather feedback and generate discussion of specific proposals whose impact may be unclear, or for which sufficiently broad review may not yet have been brought to the UTC deliberations.
标准变更的技术建议定期发布在这两个邮件列表中。公众名单上的讨论可能会导致为以后的UTC会议生成书面提案。技术问题和其他任何重要的标准化“事件”，如beta版本和文档草案的可用性，都会在标准化最终确定之前在这个公共论坛上公布并讨论。UTC还不时在联合体网站上发布“公共审查问题”，以收集反馈意见，并就可能影响不明确或尚未对UTC进行充分广泛审查的具体提案进行讨论。
Anyone may make a character encoding or architectural proposal to UTC. Membership in the organization is not required to submit a proposal. To be taken seriously, the proposal must be framed in a substantial way, and be accompanied by sufficient documentation to warrant discussion. Examples of proposals are easily available by following links from the "Proposed Characters" and "Roadmaps" headings on the Unicode web site. Guidelines for proposals are also available under the heading "Submitting Proposals".
任何人都可以向UTC提出字符编码或架构建议。本组织成员无需提交提案。要认真对待，提案必须以实质性的方式提出，并附有足够的文件以供讨论。通过以下Unicode网站上“建议的字符”和“路线图”标题的链接，可以很容易地获得建议的示例。提案指南也可在“提交提案”标题下查阅。
In general, proposals are publicly aired on the "Unicode" mail list, sometimes for a long period, prior to formal submission. Generally this is of benefit to the proposer as it tends to reduce the number of times the proposal is sent back for clarification or with requests for additional information. Once a proposal reaches the stage of being ready for discussion by UTC, the proposer will have received contact through the public mail list with one or more UTC members willing to explain or defend it in a UTC meeting.
一般来说，在正式提交之前，提案会在“Unicode”邮件列表上公开发布，有时会持续很长时间。一般来说，这对投标人有利，因为这会减少标书发回澄清或要求提供额外信息的次数。一旦提案达到准备由UTC讨论的阶段，提案人将通过公开邮件列表收到一个或多个UTC成员的联系，这些成员愿意在UTC会议上解释或辩护提案。
Thanks to Mark Davis, Simon Josefsson, and Ken Whistler for their extensive review and feedback on previous versions of this document.
感谢Mark Davis、Simon Josefsson和Ken Whistler对本文档以前版本的广泛审查和反馈。
This memo describes the operational procedures of an organization; the procedures themselves have no consequences for Internet Security.
本备忘录描述了组织的运作程序；这些程序本身对互联网安全没有影响。
Rick McGowan c/o The Unicode Consortium P.O. Box 391476 Mountain View, CA 94039-1476 U.S.A.
Rick McGowan转交美国加利福尼亚州山景城Unicode财团邮政信箱391476，邮编94039-1476。
Phone: +1-650-693-3921
Web: http://www.unicode.org/
Phone: +1-650-693-3921
Web: http://www.unicode.org/
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78 and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。