414 |
|
|
415 |
<p>You can embed another @-command inside the braces of an <code>@kbd</code> |
<p>You can embed another @-command inside the braces of an <code>@kbd</code> |
416 |
command. Here, for example, is the way to describe a command that |
command. Here, for example, is the way to describe a command that |
417 |
would be described more verbosely as "press an <samp>`r'</samp> and then |
would be described more verbosely as “press an <samp>`r'</samp> and then |
418 |
press the <kbd>RET</kbd> key": |
press the <kbd>RET</kbd> key”: |
419 |
</p> |
</p> |
420 |
<table><tr><td> </td><td><pre class="example">@kbd{r @key{RET}} |
<table><tr><td> </td><td><pre class="example">@kbd{r @key{RET}} |
421 |
</pre></td></tr></table> |
</pre></td></tr></table> |
565 |
<p>Any time you are referring to single characters, you should use |
<p>Any time you are referring to single characters, you should use |
566 |
<code>@samp</code> unless <code>@kbd</code> or <code>@key</code> is more appropriate. |
<code>@samp</code> unless <code>@kbd</code> or <code>@key</code> is more appropriate. |
567 |
Also, you may use <code>@samp</code> for entire statements in C and for entire |
Also, you may use <code>@samp</code> for entire statements in C and for entire |
568 |
shell commands--in this case, <code>@samp</code> often looks better than |
shell commands—in this case, <code>@samp</code> often looks better than |
569 |
<code>@code</code>. Basically, <code>@samp</code> is a catchall for whatever is |
<code>@code</code>. Basically, <code>@samp</code> is a catchall for whatever is |
570 |
not covered by <code>@code</code>, <code>@kbd</code>, or <code>@key</code>. |
not covered by <code>@code</code>, <code>@kbd</code>, or <code>@key</code>. |
571 |
</p> |
</p> |
904 |
<p>As a general rule, a sentence containing the defining occurrence of a |
<p>As a general rule, a sentence containing the defining occurrence of a |
905 |
term should be a definition of the term. The sentence does not need |
term should be a definition of the term. The sentence does not need |
906 |
to say explicitly that it is a definition, but it should contain the |
to say explicitly that it is a definition, but it should contain the |
907 |
information of a definition--it should make the meaning clear. |
information of a definition—it should make the meaning clear. |
908 |
</p> |
</p> |
909 |
<hr size="6"> |
<hr size="6"> |
910 |
<a name="cite"></a> |
<a name="cite"></a> |
1167 |
</pre></td></tr></table> |
</pre></td></tr></table> |
1168 |
<p>TeX typesets the small caps font in a manner that prevents the |
<p>TeX typesets the small caps font in a manner that prevents the |
1169 |
letters from `jumping out at you on the page'. This makes small caps |
letters from `jumping out at you on the page'. This makes small caps |
1170 |
text easier to read than text in all upper case--but it's usually |
text easier to read than text in all upper case—but it's usually |
1171 |
better to use regular mixed case anyway. The Info formatting commands |
better to use regular mixed case anyway. The Info formatting commands |
1172 |
set all small caps text in upper case. In HTML, the text is upper-cased |
set all small caps text in upper case. In HTML, the text is upper-cased |
1173 |
and a smaller font is used to render it. |
and a smaller font is used to render it. |