last modified: 2003-02-28
This checklist focuses on formal checking of format for publication release and does not contain issues for content review. All items in yellow need to be regularly updated almost every release. Instructions to the reviewer are given in blue.
A summary of checklist items, especially for the TR body, may be found in section 1, The Checklist.
UTR #25: Unicode and Mathematics
From this point, the TR body should be enclosed in a <div class="body"> element in order to provide a left margin. (This TR template has such a body element.)
Check status (either Draft or Proposed Draft, Proposed Update, or nothing) and the formatting of the title, e.g.:
Check header table contents and format - table must neither be 100%, nor use fixed pixels or it will not display/print correctly (the table below uses 95% width):
UAXs, when updated, should have the Unicode Version.
|Authors||Barbara Beeton (firstname.lastname@example.org), Asmus Freytag (email@example.com), Murray Sargent III (firstname.lastname@example.org) (not updated every time)|
|Date||2002-05-08 (always use ISO format)|
(also check the link; it should be the same number)
(also check link; it should be the previous number)
|Latest Version||http://www.unicode.org/reports/tr25 (check link)|
|Tracking Number||5 (must match the file name of "This Version" and must link to Modifications section below)|
Starting with version 3.2, Unicode includes virtually all of the standard characters used in mathematics. This set supports a variety of math applications on computers, including document presentation languages like TeX, math markup languages like MathML, computer algebra languages like OpenMath, internal representations of mathematics in systems like Mathematica and MathCAD, computer programs, and plain text. This technical report describes the Unicode mathematics character groups and gives some of their default math properties.
This document has been reviewed by Unicode members and other interested parties, and has been approved by the Unicode Technical Committee as a Unicode Standard Annex / Unicode Technical Standard / Unicode Technical Report. This is a stable document and may be used as reference material or cited as a normative reference by other specifications.
|Alternate Paragraph for not-yet approved documents. Replace the above if needed, and delete this table.|
|This document is a proposed draft / draft / proposed update / proposed update of a previously approved Unicode Standard Annex / Unicode Technical Standard / Unicode Technical Report. Publication does not imply endorsement by the Unicode Consortium. This is a draft document which may be updated, replaced, or superseded by other documents at any time. This is not a stable document; it is inappropriate to cite this document as other than a work in progress.|
A Unicode Standard Annex (UAX) forms an integral part of the Unicode Standard, but is published as a separate document. The Unicode Standard may require conformance to normative content in a Unicode Standard Annex, if so specified in the Conformance chapter of that version of the Unicode Standard. The version number of a UAX document corresponds to the version number of the Unicode Standard at the last point that the UAX document was updated.
Alternate Paragraphs for other types of TRs. Replace the above if needed, and delete this table. A Unicode Technical Standard (UTS) is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS. Each UTS specifies a base version of the Unicode Standard. Conformance to the UTS requires conformance to that version or higher. A Unicode Technical Report (UTR) contains informative material. Conformance to the Unicode Standard does not imply conformance to any UTR. Other specifications, however, are free to make normative references to a UTR.
Please submit corrigenda and other comments with the online reporting form [Feedback]. Related information that is useful in understanding this document is found in [References]. The latest version of the Unicode Standard is found on [Unicode]. A list of current Unicode Technical Reports is found on [Reports]. For more information about versions of the Unicode Standard, see [Versions].
This technical report starts with a discussion of the mathematics character repertoire incorporating the relevant block descriptions of the Unicode.... [ TR SPECIFIC CONTENTS ELIDED]
This section contains an item-by-item checklist of critical things to watch for in TR updates.
|questions—and answers—about||questions--and answers--about|
Tables that contain code can use class="syntax". To set a class in FrontPage, select the table, right-click, table properties, Style..., class
||the sequence consisting of x then y|
||zero or more occurences of x|
||Match ASCII alphanumerics|
||Match anything but ASCII alphanumerics|
||Match the literal characters ], -, ','|
|[Charts]||The online code charts can be found at http://www.unicode.org/charts/ An index to characters names with links to the corresponding chart is found at http://www.unicode.org/charts/charindex.html|
|[Feedback]||Reporting Errors and Requesting
|[FAQ]||Unicode Frequently Asked Questions
For answers to common questions on technical issues.
For explanations of terminology used in this and other documents.
|[NormProps]||Derived Normalization Properties
The file version at the time of this publication is:
The latest version of the data file is:
|[Reports]||Unicode Technical Reports
For information on the status and development process for technical reports, and for a list of technical reports.
|[UCD]||Unicode Character Database. http://www.unicode.org/UCD
For and overview of the Unicode Character Database and a list of its associated files
|[Unicode]||The Unicode Consortium. The Unicode Standard, Version 4.0. Reading, MA, Addison-Wesley, 2003. 0-321-18578-1.|
|[Versions]||Versions of the Unicode Standard
The following summarizes modifications from the previous version of this document.
Copyright © 2001-2003 Unicode, Inc. All Rights Reserved. The Unicode Consortium makes no expressed or implied warranty of any kind, and assumes no liability for errors or omissions. No liability is assumed for incidental and consequential damages in connection with or arising out of the use of the information or programs contained or accompanying this technical report.
Unicode and the Unicode logo are trademarks of Unicode, Inc., and are registered in some jurisdictions.