Author: branden
Date: 2004-07-09 00:12:05 -0500 (Fri, 09 Jul 2004)
New Revision: 1608
Modified:
trunk/debian/CHANGESETS
trunk/debian/local/FAQ.xhtml
Log:
(cosmetic) Add some markup.
Modified: trunk/debian/CHANGESETS
===================================================================
--- trunk/debian/CHANGESETS 2004-07-09 05:10:18 UTC (rev 1607)
+++ trunk/debian/CHANGESETS 2004-07-09 05:12:05 UTC (rev 1608)
@@ -13,6 +13,6 @@
1606
Miscellaneous cosmetic fixes.
- 1607
+ 1607, 1608
vim:set ai et sts=4 sw=4 tw=80:
Modified: trunk/debian/local/FAQ.xhtml
===================================================================
--- trunk/debian/local/FAQ.xhtml 2004-07-09 05:10:18 UTC (rev 1607)
+++ trunk/debian/local/FAQ.xhtml 2004-07-09 05:12:05 UTC (rev 1608)
@@ -101,8 +101,9 @@
of readable text, some characters appear as little gray boxes. Why?</a></li>
<li><a href="#xservmemory">Why does the X server take up so much
memory?</a></li>
-<li><a href="#xtermwrongconfig">Why do the menus in xterm have the wrong font,
- size, background color, or foregound color?</a></li>
+<li><a href="#xtermwrongconfig">Why do the menus in <code
+ class="command">xterm</code> have the wrong font, size, background color, or
+ foregound color?</a></li>
<li><a href="#upgrnonfreedriver">I just upgraded the X server and it doesn't
work; also, I'm using Matrox's proprietary <code class="other">mga_hal</code>
driver module or NVidia's proprietary <code class="other">nvidia</code>
driver
@@ -1925,13 +1926,15 @@
kernel sources which implement it is about the best manual I know of.</p>
</blockquote>
-<h3><a id="xtermwrongconfig">Why do the menus in xterm have the wrong font,
-size, background color, or foregound color?</a></h3>
+<h3><a id="xtermwrongconfig">Why do the menus in <code
+ class="command">xterm</code> have the wrong font, size, background color, or
+ foregound color?</a></h3>
<p>Because, 99 times out of 100, you're not using X resources correctly.</p>
-<p>If you have X resource specifications (say, in your $HOME/.Xresources file)
-that look like this:</p>
+<p>If you have X resource specifications (say, in your <code
+class="filespec"><var>$HOME</var>/.Xresources</code> file) that look like
+this:</p>
<pre>XTerm*foreground: black
XTerm*background: white
@@ -1940,13 +1943,13 @@
<p>...then be aware that you are, in fact, telling the menus, not just the
VT100 widget, to use the 10x20 font with white-on-black text. That
-asterisk is a wildcard, not an ordinary separator. XTerm is doing exactly
-what you are telling it to do. If you find X resources confusing, don't
-use them, or read the "RESOURCES" section of the <code
-class="manpage">X(7x)</code> manual page.</p>
+asterisk is a wildcard, not an ordinary separator. <code
+class="command">xterm</code> is doing exactly what you are telling it to do.
If
+you find X resources confusing, don't use them, or read the "RESOURCES" section
+of the <code class="manpage">X(7x)</code> manual page.</p>
-<p>If you want to set X resources for xterm that affect only its VT100 widget,
-then you need to say so:</p>
+<p>If you want to set X resources for <code class="command">xterm</code> that
+affect only its VT100 widget, then you need to say so:</p>
<pre>XTerm.VT100.background: white
XTerm.VT100.foreground: black
