FAQ on FAQs
Q: How are Unicode FAQs created?
A: FAQs are created by the Unicode editorial committee. FAQ entries may also be submitted by the general Unicode
community via the contact form; those are reviewed and edited by the editorial committee before posting.
The primary authors of FAQ entries are often acknowledged by initials,
which provide a link to the FAQ attributions page, where they are
Q: What is the Unicode editorial committee?
A: The editorial committee is the group in charge of editorial oversight of all Unicode print and online publications, including FAQs.
The committee meets face-to-face about once a month and currently has
about 20 participants, many of whom also normally work via email on a
Q: When are new Unicode FAQs created?
A: Whenever someone has provided a useful summary answer to a question that has been asked frequently. Also to
provide clarifications about some aspects of the Unicode Standard or the other Unicode specifications, when it has become
apparent that misunderstandings of these issues are common.
Q: What can I do if I think there is an error in an FAQ answer?
A: To suggest a correction or update to the FAQ submit your feedback via the
Q: How does an FAQ relate to a Unicode specification?
A: The purpose of each FAQ is to explain and clarify issues in the Unicode Standard or other Unicode specifications.
The technical content of the FAQ is designed to be consistent with the relevant specifications. If there are inadvertent
differences or other errors, please bring them to the attention of the editorial committee.
Q: What can I do if I think there is an error in the Unicode Standard or other specification?
A: Request a correction, clarification or change to the relevant specification by submitting feedback or a formal proposal to the
corresponding technical committee. The three technical committees are the UTC, CLDR-TC and ULI-TC. The methods
are different for each committee and depending on the type of change requested. See Public Review Issues for an explanation of how to do this.