From 5de7c57d3703cadcde3287f20fa5e03aa175a8e1 Mon Sep 17 00:00:00 2001
From: Context Git Mirror Bot <phg42.2a@gmail.com>
Date: Mon, 5 Jan 2015 01:15:05 +0100
Subject: 2015-01-05 00:16:00

---
 .../general/manuals/xtables/xtables-mkiv.tex       | 109 ++++++++++++++++++++-
 1 file changed, 108 insertions(+), 1 deletion(-)

(limited to 'doc/context/sources/general/manuals/xtables/xtables-mkiv.tex')

diff --git a/doc/context/sources/general/manuals/xtables/xtables-mkiv.tex b/doc/context/sources/general/manuals/xtables/xtables-mkiv.tex
index e137f9235..a83484658 100644
--- a/doc/context/sources/general/manuals/xtables/xtables-mkiv.tex
+++ b/doc/context/sources/general/manuals/xtables/xtables-mkiv.tex
@@ -651,7 +651,112 @@ parameter can get the values \type {before}, \type {after} and \type {both}.
 
 \stopsection
 
-\startsection[title={nesting}]
+\startsection[title={Options}]
+
+On the average a table will come out okay but you need to keep in mind that when
+(complex) spans are used the results can be less that optimal. However, as
+normally one pays attention to creating tables, the amount of control provided
+often makes it possible to get what you want.
+
+In the following situations, the first cell width is determined by the span. It
+is possible to make a more clever analyzer but we need to keep in mind that in
+the same column there can be entries that span a different amount of columns. Not
+only would that be inefficient but it would also be rather unpredictable unless
+you know exactly what happens deep down. The following two examples demonstrate
+default behaviour.
+
+\startbuffer
+\startxtable
+  \startxrow
+    \startxcell[nx=3]
+        1/2/3
+    \stopxcell
+  \stopxrow
+  \startxrow
+    \startxcell 1 \stopxcell
+    \startxcell 2 \stopxcell
+    \startxcell 3 \stopxcell
+  \stopxrow
+\stopxtable
+\stopbuffer
+
+\typebuffer \getbuffer
+
+\startbuffer
+\startxtable
+  \startxrow
+    \startxcell[nx=3]
+        1 / 2 / 3
+    \stopxcell
+  \stopxrow
+  \startxrow
+    \startxcell 1 \stopxcell
+    \startxcell 2 \stopxcell
+    \startxcell 3 \stopxcell
+  \stopxrow
+\stopxtable
+\stopbuffer
+
+\typebuffer \getbuffer
+
+In practice you will set the width of the columns, as in:
+
+\startbuffer
+\startxtable
+  \startxrow
+    \startxcell[nx=3]
+        1/2/3
+    \stopxcell
+  \stopxrow
+  \startxrow
+    \startxcell[width=\dimexpr\textwidth/3] 1 \stopxcell
+    \startxcell[width=\dimexpr\textwidth/3] 2 \stopxcell
+    \startxcell[width=\dimexpr\textwidth/3] 3 \stopxcell
+  \stopxrow
+\stopxtable
+\stopbuffer
+
+\typebuffer \getbuffer
+
+But, if you want you can control the enforced width by setting an option:
+
+\startbuffer
+\startxtable
+  \startxrow
+    \startxcell[nx=3,option=tight]
+        1/2/3
+    \stopxcell
+  \stopxrow
+  \startxrow
+    \startxcell 1 \stopxcell
+    \startxcell 2 \stopxcell
+    \startxcell 3 \stopxcell
+  \stopxrow
+\stopxtable
+\stopbuffer
+
+\typebuffer \getbuffer
+
+\startbuffer
+\startxtable
+  \startxrow
+    \startxcell[nx=3,option=tight]
+        1 / 2 / 3
+    \stopxcell
+  \stopxrow
+  \startxrow
+    \startxcell 1 \stopxcell
+    \startxcell 2 \stopxcell
+    \startxcell 3 \stopxcell
+  \stopxrow
+\stopxtable
+\stopbuffer
+
+\typebuffer \getbuffer
+
+\stopsection
+
+\startsection[title={Nesting}]
 
 Extreme tables can be nested but you need to keep an eye on inheritance here as
 the inner table uses the settings from the encapsulating cell. The widths and
@@ -1096,4 +1201,6 @@ in the distribution.
 \typebuffer[tight]  \start \getbuffer[tight,demo]  \stop
 \typebuffer[normal] \start \getbuffer[normal,demo] \stop
 
+% \ruledhbox{\getbuffer[normal,demo]}
+
 \stopdocument
-- 
cgit v1.2.3

