summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html51
1 files changed, 51 insertions, 0 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html
new file mode 100644
index 00000000000..9c8ce272563
--- /dev/null
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html
@@ -0,0 +1,51 @@
+<head>
+<title>UK TeX FAQ -- question label rulethk</title>
+</head><body>
+<h3>The thickness of rules in LaTeX tables</h3>
+<p>The rules in a LaTeX table are by default <code>0.4pt</code> thick;
+this is in fact a default built in at the lowest level, and applies to
+all rules (including those separating blocks of running text).
+<p>Sometimes, however, we look at a table and find we want the rules to
+stand out - perhaps to separate the text from the rest of the body
+text, or to make the sections of the table stand out from one another.
+However, a quick review of any LaTeX manual will reveal no
+technique for making any one rule stand out, and a little
+experimentation shows that it is indeed pretty difficult to prevent
+a change "bleeding" out to affect other rules in the same table.
+<p>Refer to the answer on <a href="FAQ-destable.html">design of tables</a>, elsewhere
+among these FAQs, and you may sense that the design of LaTeX
+suimply skipped the issues surrounding table design, and <em>that's</em>
+why there's no facilities to help you.
+<p>Specifically, the length <code>\</code><code>arrayrulewidth</code> affects the thickness of
+the rules (both horizontal and vertical) within both
+<code>tabular</code> and <code>array</code> environments. If you
+change from the default (see above) only as far as
+<blockquote>
+<pre>
+\setlength{\arrayrulewidth}{1pt}
+</pre>
+</blockquote>
+the change is remarkably striking. However, really quite subtle user
+level programming proves incapable of changing just <em>one</em> rule:
+it's necessary to delve into the (rather tricky) code of <code>\</code><code>hline</code>
+and <code>\</code><code>cline</code> themselves.
+<p>Fortunately, this job has already been done for the community: the
+<i>booktabs</i> package defines three different classes of rule
+(<code>\</code><code>toprule</code>, <code>\</code><code>midrule</code> and <code>\</code><code>bottomrule</code>), and the package
+documentation offers hints on how to use them. You are
+<em>strongly</em> advised to read the documentation pretty carefully.
+<p>The <i>memoir</i> class includes the <i>booktabs</i> package, and
+repeats the documentation in its compendious manual.
+<p>Note that none of the above mentions the issue of the weight of
+vertical rules (except in passing). For the reasons, see the
+documentation of the <i>booktabs</i> package (again); vertical
+rules in tables are in any case even more trickily coded than are
+horizontal rules, and if their lack of configurability makes them
+still less attractive, so much the better for the design of your
+document.
+<dl>
+<dt><tt><i>booktabs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse</a>)
+<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>)
+</dl>
+<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rulethk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rulethk</a>
+</body>