14.03.2013 Views

symbols-a4

symbols-a4

symbols-a4

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

\usepackage{textcomp}<br />

\DeclareUnicodeCharacter{"2103}{\textcelsius} % Enable direct input of U+2103.<br />

\begin{document}<br />

It was a balmy 21℃.<br />

\end{document}<br />

which produces<br />

It was a balmy 21℃.<br />

See the ucs documentation for more information and for descriptions of the various options that control<br />

ucs’s behavior.<br />

Outputting Unicode characters<br />

Orthogonal to the ability to include Unicode characters in a LATEX input file is the ability to include a given<br />

Unicode character in the corresponding output file. By far the easiest approach is to use XE LATEX instead of<br />

pdfLATEX or ordinary LATEX. XE LATEX handles Unicode input and output natively and can utilize system fonts<br />

directly without having to expose them via .tfm, .fd, and other such files. To output a Unicode character,<br />

a XE LATEX document can either include that character directly as UTF-8 text or use TEX’s \char primitive,<br />

which XE LATEX extends to accept numbers larger than 255.<br />

Suppose we want to output the <strong>symbols</strong> for versicle (“ ”) and response (“ ”) in a document. The Unicode<br />

charts list “versicle” at position U+2123 and “response” at position U+211F. We therefore need to install a<br />

font that contains those characters at their proper positions. One such font that is freely available from CTAN<br />

is Junicode Regular (Junicode-Regular.ttf) from the junicode package. The fontspec package makes it easy<br />

for a XE LATEX document to utilize a system font. The following example defines a \textjuni command that<br />

uses fontspec to typeset its argument in Junicode Regular:<br />

\documentclass{article}<br />

\usepackage{fontspec}<br />

\newcommand{\textjuni}[1]{{\fontspec{Junicode-Regular}#1}}<br />

\begin{document}<br />

We use ‘‘\textjuni{\char"2123}’’ for a versicle<br />

and ‘‘\textjuni{\char"211F}’’ for a response.<br />

\end{document}<br />

which produces<br />

We use “ ” for a versicle and “ ” for a response.<br />

(Typesetting the entire document in Junicode Regular would be even easier. See the fontspec documentation<br />

for more information regarding font selection.) Note how the preceding example uses \char to specify a<br />

Unicode character by number. The double quotes before the number indicate that the number is represented<br />

in hexadecimal instead of decimal.<br />

8.8 About this document<br />

History David Carlisle wrote the first version of this document in October, 1994. It originally contained<br />

all of the native L ATEX <strong>symbols</strong> (Table 44, Table 57, Table 67, Table 102, Table 128, Table 131, Table 152,<br />

Table 153, Table 164, Table 169, Table 201, and a few tables that have since been reorganized) and was designed<br />

to be nearly identical to the tables in Chapter 3 of Leslie Lamport’s book [Lam86]. Even the table captions<br />

and the order of the <strong>symbols</strong> within each table matched! The AMS <strong>symbols</strong> (Table 45, Table 68, Table 69,<br />

Table 105, Table 106, Table 132, Table 137, Table 148, and Table 202) and an initial Math Alphabets table<br />

(Table 213) were added thereafter. Later, Alexander Holt provided the stmaryrd tables (Table 46, Table 59,<br />

Table 70, Table 108, Table 125, and Table 149).<br />

In January, 2001, Scott Pakin took responsibility for maintaining the symbol list and has since implemented<br />

a complete overhaul of the document. The result, now called, “The Comprehensive L ATEX Symbol List”,<br />

includes the following new features:<br />

118

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!