diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html')
| -rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html index e31404b1b9d..6610dd321d8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html @@ -3,9 +3,9 @@ </head><body> <h3><code>\</code><code>@</code> and <code>@</code> in macro names</h3> <p/>Macro names containing <code>@</code> are <em>internal</em> to LaTeX, and -without special treatment just don’t work in ordinary use. A nice +without special treatment just don’t work in ordinary use. A nice example of the problems caused is discussed in -<a href="FAQ-atvert.html"><code>\</code><code>@</code> in vertical mode</a>”. +<a href="FAQ-atvert.html"><code>\</code><code>@</code> in vertical mode</a>”. <p/>The problems users see are caused by copying bits of a class (<code>.cls</code> file) or package (<code>.sty</code> file) into a document, or by including a class or @@ -16,10 +16,10 @@ avoid clashes between its internal names and names that we would normally use in our documents. In order that these commands may work at all, <code>\</code><code>documentclass</code> and <code>\</code><code>usepackage</code> play around with the meaning of <code>@</code>. -<p/>If you’ve included a file some other way (for example, using +<p/>If you’ve included a file some other way (for example, using <code>\</code><code>input</code>), you can probably solve the problem by using the correct command. -<p/>If you’re using a fragment of a package or class, you may well feel +<p/>If you’re using a fragment of a package or class, you may well feel confused: books such as the first edition of the <a href="FAQ-books.html">The LaTeX Companion</a> are full of fragments of packages as examples for you to employ. @@ -44,7 +44,7 @@ second edition.) <p/>The alternative is to treat all these fragments as a package proper, bundling them up into a <code>.sty</code> file and including them with <code>\</code><code>usepackage</code>; this way you hide your LaTeX internal code somewhere -that LaTeX internal code is expected, which often looks ‘tidier’. +that LaTeX internal code is expected, which often looks ‘tidier’. <dl> <dt><tt><i>Examples from the Companion</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (or <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse the directory</a>) </dl> |