Unicode Technical Note #99

[Put Title Here]

Version	1
Authors	[authors]
Date	[date]
This Version	https://www.unicode.org/notes/tn99/tn99-1.html
Previous Version	N/A
Latest Version	https://www.unicode.org/notes/tn99/

Summary

This document provides a template for Unicode Technical Notes. Authors of Unicode Technical notes are not required to use this template. Documents may be submitted in other formats such as PDF. However, if an author chooses not to use this template, a simpler Basic Cover Template must be used to provide cover information and an abstract.

Status

This document is a Unicode Technical Note. Sole responsibility for its contents rests with the author(s). Publication does not imply any endorsement by the Unicode Consortium.

For information on Unicode Technical Notes including criteria for acceptance, see https://www.unicode.org/notes/.

Introduction
1. Subsection
Style
References
Modifications

1 Introduction

This document contains an optional template for generating Unicode Technical Notes in HTML format, using a hypothetical example of Unicode Technical Note #99, with the current version set to 1. To use this template, create a copy and make the following changes:

Replace the #99 by the correct values.
The version number will start out as 1 and increment upwards as needed if the UTN is ever revised.
Replace [authors], [date], and [title] by the correct values.
Remember to change the document title (<title>...</title> in the <head> section of the HTML) so that it shows up correctly.
Change the summary to have a short description of the document.
Don't touch the status section.
Major sections are <h2> in HTML, subsections are <h3>, etc.
Each section, subsection, etc. should have an anchor (aka bookmark). Use short, descriptive phrases for the anchor, without reference to the number of the section. Try not to change the anchors from version to version.
Have one line in the Contents for each section and subsection. These are to be linked to the section/subsection.
Add the appropriate References (and remove ones that are not referenced). The standard style is: "For more information, see Unicode Frequently Asked Questions [FAQ]."
- Notice that the document name directly links to the outside document, while the abbreviation links to the Reference table. The latter is to allow the document to be used in printed form.
At the bottom of the page, update "XXXX" and "[authors]" to the appropriate publication year and author name(s) as appropriate.

1.1 Subsection

This subsection is inserted just to have a sample. Likewise, the References section below is populated with a few possibly useful entries, but is not required.

2 Style

When in doubt, follow the Chicago Manual of Style [CMS]. In particular,

Only use a single space after the end of a sentence.
Use real punctuation instead of the ASCII fallbacks. For example:

Publishing	ASCII
questions—and answers—about	questions--and answers--about
“phthisic”	"phthisic"
‘fish’	'fish', `fish'
can’t	can't

3 References

[FAQ]	Unicode Frequently Asked Questions https://www.unicode.org/faq/ For answers to common questions on technical issues.
[Glossary]	Unicode Glossary https://www.unicode.org/glossary/ For explanations of terminology used in this and other documents.
[CMS]	The Chicago Manual of Style: The Essential Guide for Writers, Editors, and Publishers (14th Edition) University of Chicago Press (Trd); ISBN: 0226103897 Also see their FAQ at https://www.press.uchicago.edu/Misc/Chicago/cmosfaq.html
[Reports]	Unicode Technical Reports https://www.unicode.org/reports/ For information on the status and development process for technical reports, and for a list of technical reports.
[Versions]	Versions of the Unicode Standard https://www.unicode.org/versions/ For details on the precise contents of each version of the Unicode Standard, and how to cite them.

Modifications

The following summarizes modifications from the previous version of this document.

1	Sample version

©XXXX–XXXX [insert author’s name]. This publication is protected by copyright, and permission must be obtained from the author and Unicode, Inc. prior to any reproduction, modification, or other use not permitted by the Terms of Use.

Use of this publication is governed by the Unicode Terms of Use. The authors, contributors, and publishers have taken care in the preparation of this publication, but make no express or implied representation or warranty of any kind and assume no responsibility or liability for errors or omissions or for consequential or incidental damages that may arise therefrom. This publication is provided “AS-IS” without charge as a convenience to users.

Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries.