summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/plain
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2008-11-07 18:29:39 +0000
committerKarl Berry <karl@freefriends.org>2008-11-07 18:29:39 +0000
commitd021c11b31a50fef4c95a2fc171ab2c5b7ef22b9 (patch)
treec23090030d32b38c8bc065c2373fb838fbea30ad /Master/texmf-dist/doc/plain
parentef0b9535341949b3436c05268d57f6c4bdfebbcb (diff)
rm cellular, license noinfo, author deceased
git-svn-id: svn://tug.org/texlive/trunk@11216 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/plain')
-rw-r--r--Master/texmf-dist/doc/plain/cellular/cellular.doc114
-rw-r--r--Master/texmf-dist/doc/plain/cellular/origin28
2 files changed, 0 insertions, 142 deletions
diff --git a/Master/texmf-dist/doc/plain/cellular/cellular.doc b/Master/texmf-dist/doc/plain/cellular/cellular.doc
deleted file mode 100644
index 0a46d604381..00000000000
--- a/Master/texmf-dist/doc/plain/cellular/cellular.doc
+++ /dev/null
@@ -1,114 +0,0 @@
-% File: TeX Inputs cellular.doc
-% Author: J E Pittman
-% Bitnet: JEPTeX@TAMVenus
-% Internet: JEPTeX@Venus.TAMU.EDU
-% Date: November 8, 1988
-
-A cellular table is specified by:
-
- \begincellular{specifications that change defaults}
- appropriate macro definitions
- column header specifications
- row specifications (header and data)
- \endcellular
-
-The following are examples of specifications that change defaults:
-
- \pixelwidth=1in
- \divide\pixelwidth by 300
-
- The pixel width dimension register should be set to the resolution
- of the device used. The default is 1/300th of an inch.
-
- \setverticaladjustment -or- \sethorizontaladjustment
-
- Some printers (such as the Xerox 9700s and 4050s) produce vertical
- and horizontal rules that have a different visual thickness for the
- same specified thickness. The macros set vertical and set
- horizontal adjustment specified that vertical or horizontal rules
- are to be thickened by pixel width, which may correct this problem.
-
- \edef\everycolumn{\everycolumn
- \leftrulewidth=0.4pt\relax
- \rightrulewidth=\leftrulewidth
- \leftborderskip=6pt plus 1fil\relax
- \rightborderskip=\leftborderskip
- \columnwidth=\zeropt\relax
- \columnwidth=\zeropt\relax
- }%
-
- An \edef can be used to add material (usually default overrides) to
- the every column macro. The information shown above reflect the
- defaults. Care must be exercised to avoid introducing spurous
- spaces, which will be very visible when output.
-
- \edef\everyrow{\everyrow
- \toprulewidth=0.4pt\relax
- \bottomrulewidth=\toprulewidth
- \topborderskip=3pt plus 1fil\relax
- \bottomborderskip=\topborderskip
- \rowheight=\zeropt\relax
- }%
-
- Same as every column.
-
- \tracingexpansions=1
-
- This specification will request notes on how column and rows are
- expanded to accommedate spans.
-
-Any sort of macros can be defined within a cellular table. An obvious
-example is abbrevations for commonly used control sequence names.
-
-A column header is specified as:
-
- \column{specifications}
-
- The specifications are the same as for every column. Note: There
- is a considerable amount of processing required for these
- specifications, wise selection of defaults can decrease execution
- time significantly.
-
- Column headers are optional.
-
-Rows are specified as a row header (similiar to a column header) and a
-series of entry specifications.
-
-An entry specification can be any of the following:
-
- \blank
-
- A blank entry specification creates a completely blank spot in the
- table (no rules or text).
-
- \mergeright
-
- A merge right specification merges the width of the entry into the
- width of the entry to the right. It is used to create column
- spans.
-
- \mergedown
-
- Similar to merge right. Note: The overhead for a merge down
- specification is considerably higher than a merge right.
- Therefore, when specifing an entry that spans both rows and
- columns, merge rights should be used as much as possible. For
- example:
-
- > > > V V V V V
- > > > V rather V V V V
- > > > V than V V V V
- > > > * > > > *
-
- \entry{horizontal mode material}
-
- An entry macro takes the specified material and formats it as
- appropriate.
-
-It is not necessary to complete every row.
-
-Vertical mode material can be added after a row by specifying:
-
- \noalign{vertical mode material}
-
-at any point in the row. Multiple no aligns are permitted.
diff --git a/Master/texmf-dist/doc/plain/cellular/origin b/Master/texmf-dist/doc/plain/cellular/origin
deleted file mode 100644
index 89d309c957c..00000000000
--- a/Master/texmf-dist/doc/plain/cellular/origin
+++ /dev/null
@@ -1,28 +0,0 @@
-Date: Wed, 9 Nov 88 13:33:46 CST
-From: J E PITTMAN <JEPTEX@venus.tamu.edu>
-Subject: TeX Inputs cellular.tex (table-generating macros)
-Keywords: macros
-
-Several months ago, someone sent in a request for macros that allow vertical
-and horizontal spans within a ruled table. There have also been questions
-about `nubs' and `gaps' within ruled tables.
-
-After thinking about the problem for a while, I realized that a solution was to
-abandon the \halign primitive and start from scratch.
-
-I have finished my first attempt at a set of table generating macros, which I
-have chosen to call Cellular.TeX. These macros allow for both vertical and
-horizontal spans and take steps to prevent `nubs' and `gaps' when rules are
-used.
-
-They are, unfortunately, very slow and I have not been able to increase their
-speed without sacrificing memory conservation and generality.
-
-I am sending the macros under separate cover since there are nearly 1,000 lines
-of code involved, divided into five files. Detailed comments are available in
-the file TeX Inputs cellular.doc.
-
-J E Pittman Bitnet: JEPTeX@TAMVenus
-User Services Group Internet: JEPTeX@Venus.TAMU.Edu
-Computing Services Center
-Texas A&M University