summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc')
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/COPYING339
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/README501
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/at.dvibin67028 -> 0 bytes
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/cmtt.dvibin59608 -> 0 bytes
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/doafter.dvibin51920 -> 0 bytes
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/footnote.dvibin64192 -> 0 bytes
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/mdwlist.dvibin68376 -> 0 bytes
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/mdwmath.dvibin52800 -> 0 bytes
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/mdwtab.dvibin357412 -> 0 bytes
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/sverb.dvibin94644 -> 0 bytes
-rw-r--r--Master/texmf-dist/doc/latex/mdwtools/syntax.dvibin184176 -> 0 bytes
11 files changed, 840 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/latex/mdwtools/COPYING b/Master/texmf-dist/doc/latex/mdwtools/COPYING
new file mode 100644
index 00000000000..a43ea2126fb
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/mdwtools/COPYING
@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 675 Mass Ave, Cambridge, MA 02139, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ Appendix: How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) 19yy <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/Master/texmf-dist/doc/latex/mdwtools/README b/Master/texmf-dist/doc/latex/mdwtools/README
new file mode 100644
index 00000000000..dd5538672ac
--- /dev/null
+++ b/Master/texmf-dist/doc/latex/mdwtools/README
@@ -0,0 +1,501 @@
+
+ ===============
+
+ M D W T O O L S
+
+ ===============
+
+
+--- Licence note ---
+
+mdwtools package release note
+Copyright (c) 1996 Mark Wooding, except doafter, which is Copyright (c) 1996
+Peter Schmitt and Mark Wooding.
+
+These programs are free software; you can redistribute them and/or modify
+them under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+These programs are distributed in the hope that they will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with these programs; if not, write to the Free Software
+Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+
+
+--- What it's all about ---
+
+This is a bunch of LaTeX 2e packages which have made my life as a LaTeX user
+easier, so I thought I'd share them. I'm mainly an ARM assembler hacker
+(which explains why my TeX code looks so horrible), although I have been
+known to write documentation for programs. This may explain the sort of
+things these packages do, and where I'm coming from.
+
+
+--- Licencing ---
+
+The packages are made available under the GNU General Public Licence (not the
+usual LaTeX agreement). A copy of this licence is supplied in the file
+COPYING. You should read this document if you haven't read it already, even
+if it's just for educational value. I'm not actually sure how good a thing
+the GNU GPL actually is, so I'm sort of testing the water. The idea that
+this is how all software should be distributed still fills me with a certain
+amount of trepidation.
+
+
+--- What's in the box ---
+
+You should have received the following files in whatever sort of archive
+thing this suite came in:
+
+ README -- You've got this file for sure, because it's this one
+ COPYING -- A textual version of the GNU General Public Licence
+ at.dtx -- Documentation and code for `at.sty' package
+ cmtt.dtx -- Documentation and code for `cmtt.sty'package and
+ associated files
+ doafter.dtx -- Documentation and code for `doafter.sty' package; the
+ code is also used in `syntax.sty' and `mdwtab.sty'
+ mdwlist.dtx -- Documentation and code for `mdwlist.sty' package
+ mdwmath.dtx -- Documentation and code for `mdwmath.sty' package
+ mdwtab.dtx -- Documentation and code for `mdwtab.sty' and `mathenv.sty'
+ packages
+ footnote.dtx -- Documentation and code for `footnote.sty' package; the
+ code is used in `mdwtab.sty'
+ sverb.dtx -- Documentation and code for `sverb.stx' package
+ syntax.dtx -- Documentation and code for `syntax.dtx' package
+ mdwtools.ins -- Installation script for all the packages
+ gpl.tex -- LaTeX version of the GNU General Public Licence
+ mdwtools.tex -- Definitions for typesetting the documentation
+
+If you're missing any of these files, complain at whoever gave the rest of
+them to you, and get them quickly. However, if you're lucky, you may have
+received some other files:
+
+ at.sty -- Unpacked `at.sty' package
+ cmtt.sty -- Unpacked `cmtt.sty' package
+ mTTenc.def -- Unpacked encoding definition file for `cmtt.sty'
+ mTTcmtt.fd -- Unpacked font definition file for `cmtt.sty'
+ doafter.sty -- Unpacked `doafter.sty' package for LaTeX
+ doafter.tex -- Unpacked `doafter.tex' package for Plain TeX
+ mathenv.sty -- Unpacked `mathenv.sty' package
+ mdwlist.sty -- Unpacked `mdwlist.sty' package
+ mdwmath.sty -- Unpacked `mdwmath.sty' package
+ mdwtab.sty -- Unpacked `mdwtab.sty' package
+ footnote.sty -- Unpackad `savenot.dty' package
+ sverb.sty -- Unpacked `sverb.sty' package
+ syntax.sty -- Unpacked `syntax.sty' package
+
+ at.dvi -- Typeset documentation for `at.sty'
+ cmtt.dvi -- Typeset documentation for `cmtt.sty' and co.
+ doafter.dvi -- Typeset documentation for `doafter.sty'
+ mdwlist.dtx -- Typeset documentation for `mdwlist.sty'
+ mdwmath.dvi -- Typeset documentation for `mdwmath.sty'
+ mdwtab.dvi -- Typeset documentation for `mdwtab.sty' and `mathenv.sty'
+ footnote.dvi -- Typeset documentation for `footnote.sty'
+ sverb.dvi -- Typeset documentation for `sverb.sty'
+ syntax.dvi -- Typeset documentation for `syntax.sty'
+
+If you've already got these, then great, because you don't have to generate
+them. If you haven't, it's not a big deal. You might also have a bunch of
+files with extensions like `.log', `.aux', `.tmp', `.ilg' and so on. These
+files are really not at all interesting, and you might as well get rid of
+them now.
+
+
+--- What the packages do ---
+
+Before we can get anywhere, you need to know what the packages do, roughly
+speaking. Here's a quick rundown:
+
+at.sty -- Allows you to use `@' as a sort of `command-introducing'
+ character, a bit like `\' is already. This gives you
+ a lot more short command names which you can assign to
+ common constructions. For example, you can set up
+ @/<text>/ as a command to put <text> in italics.
+
+cmtt.sty -- Provides an `mTT' encoding for the Computer Modern
+ Typewriter font, which solves lots of messy problems.
+
+doafter.sty -- Provides a TeX programmer's utility
+ \doafter <token> <group>
+ which does the <token> after the group is complete,
+ including any \aftergroup things. The code was originally
+ written by Peter Schmitt in answer to a `challenge' I made
+ on comp.text.tex;I tweaked it a bit to make it work
+ slightly better. doafter.tex is a plain TeX version of
+ the same macro.
+
+mathenv.sty -- Contains a collection of mathematical environments with
+ a theme of aligning things in columns. There's a
+ rewritten version of `eqnarray' which is much more
+ powerful than the old one, and it gets the spacing right.
+ This package requires `mdwtab.sty' in order to work. It
+ is extracted from `mdwtab.dtx'. In general, the AmS
+ things to a better job, although it seems that the mathenv
+ matrix and script handling environments give prettier
+ results than the AmS equivalents (at least to my eyes).
+
+mdwlist.sty -- Various list related environments. There's a more
+ versatile `description' environment, and some stuff for
+ making `compacted' lists (with no extra space between
+ items).
+
+mdwmath.sty -- Contains a few trivial definitions for mathematical
+ things. The main thing is that the \sqrt command for
+ doing square roots has been improved -- there's a \sqrt*
+ command which stops the line being drawn over the formula
+ being square-rooted, and the positioning of the root
+ index (the optional argument) has been improved.
+
+mdwtab.sty -- A complete ground-up rewrite of LaTeX's `tabular' and
+ `array' environments. Has lots of advantages over
+ the standard version, and over the version in `array.sty'.
+ It works correctly with all the table-related packages in
+ the Tools bundle (longtable, delarray, hhline, tabularx
+ and dcolumn). This package includes most of the code
+ from `doafter.sty' and `footnote.sty' (it doesn't load
+ the packages -- it has its own copies built-in, although
+ you won't waste memory if you do load these packages).
+ To generate `mdwtab.sty', you require `mdwtab.dtx',
+ `doafter.dtx' and `footnote.dtx'; the last two provide
+ the shared code.
+
+footnote.sty -- Provides commands for saving executing footnotes; the
+ author has noticed several packages which attempt to
+ enable footnotes in tables, all of which eat an extra
+ token list register. This is an attempt to offer shared
+ code to do the job, saving space and effort. It also
+ provides a `footnote' environment which allows verbatim
+ text.
+
+sverb.sty -- A bunch of macros for doing verbatim things. Required
+ for typesetting all the documentation for the other
+ packages.
+
+syntax.sty -- A load of commands for describing syntax. There's an
+ environment for typesetting BNF grammars. But best of
+ all, there's a load of commands and environments for
+ drawing syntax diagrams. Required for typesetting all
+ the documentation for the other packages. If you're
+ extracting syntax.sty from syntax.dtx, you also need
+ doafter.dtx.
+
+With the exception of the dependencies listed above, the packages will all
+work independently of each other. If you want to typeset the documentation,
+you'll need `sverb.sty' and `syntax.sty'. Typesetting the documentation
+isn't essential, although it will probably help if you can see what the
+various commands actually do.
+
+
+--- Extracting the packages ---
+
+If you don't have the various .sty files already, you'll need to extract them
+from the .dtx files. This requires docstrip.tex, which should be part of
+your base LaTeX 2e distribution. If you have docstrip vsersion 2.3d, which
+is available with the December 1995 release of LaTeX, things will go rather
+faster. If your LaTeX release is much older than this, you should upgrade,
+because the packages need a fairly new LaTeX anyway. (I could do something
+about this, but I won't, because I want to encourage everyone to upgrade.)
+
+If everything's set up correctly, all you should need to do is say
+
+ tex mdwtools.ins
+
+or
+
+ latex mdwtools.ins
+
+or whatever incantation is necessary to run TeX or LaTeX on the supplied
+`mdwtools.ins' file on your system.
+
+TeX will grind away at the files for a bit, and then say `Done' at you. (This
+could take a while, so be patient.) You will then have a mdwtools.log file,
+which you can throw away, and a collection of sparkly new .sty files, which
+you should put somewhere where TeX can find them easily.
+
+
+--- Typesetting the documentation ---
+
+If you want to typeset the documentation for a package, you'll need the
+`mdwtools.tex' file provided, and the `syntax.sty' and `sverb.sty' packages.
+You'll also need the `.dtx' file for the package you want documentation on,
+and any packages it generated.
+
+For example, if you want documentation on `mathenv.sty', you need:
+
+ mdwtools.tex -- Shared defintions for all the documentation files
+ syntax.sty -- Syntax typesetting commands
+ sverb.sty -- Verbatim text handling commands
+ mathenv.sty -- So the documentation can use it to demonstrate its
+ features
+ mdwtab.sty -- Required by `mathenv.sty'
+ mdwtab.dtx -- The documentation file from which `mathenv.sty' was
+ extracted, and therefore the file which contains the
+ documentation you want to read
+
+Make sure you've got all the files, and then run LaTeX on the .dtx file you
+want to read.
+
+TeX will start hammering away for a very short while, and then stop and ask
+you whether you want to build the indexing files. Generating index files
+takes a lot longer (I'd guess that it doubled the amount of time taken to
+typeset the `.dtx' file) so I don't recommend it unless:
+
+ * you've got a very fast processor, or
+ * you're very interested in how the package works internally, or
+ * you just like everything to be complete, or
+ * you're a masochist.
+
+Even so, there's no point writing indexing information the first time you
+run LaTeX on a file, because the table of contents hasn't been created yet,
+and when you LaTeX the file the second time, all the references will change.
+
+If you want the index files anyway, type `y' when you're asked. Otherwise,
+type 'n'. You know you want to type `n' really...
+
+If you want to do the job properly, you need to run LaTeX a second time
+to read in the contents table. /This/ is the correct time to turn on
+indexing, if you really want it.
+
+If you did build the index files, you should now sort the index by saying
+
+ makeindex -s gind.ist <name>.idx
+
+where <name> is the same as the name of the `.dtx' file. The `gind.ist' file
+should have come with LaTeX. Having done this, you should run the `.dtx'
+file though LaTeX one final time, to insert the formatted index.
+
+You can now print or preview the generated `.dvi' file using whatever tools
+you usually use for such things.
+
+
+--- What changed? ---
+
+Here's a list of what changed in the various releases.
+
+Version Changes
+
+1.00 * First general releases of everything.
+
+
+1.01 * Fixed typos in various bits of documentation.
+
+ * (mdwtab.sty) Added enhanced \cline command. Added
+ hhline.sty to list of supported table-related packages.
+ (I guess it always worked -- I just forgot about it.)
+ Made some of the section titles a little sillier ;-)
+
+ * (mathenv.sty) Added some new random environments, mainly
+ because I saw some more interesting examples in /The/
+ /TeXbook/ and had an idea... Now support nesting of
+ various environments, albeit rather imperfectly.
+
+ * (at.sty) Made @-commands really properly robust. Fixed
+ some lies in the documentation. Removed some truly insane
+ bits of old code here too. Made package sort of
+ cooperate with amsmath's use of @-commands -- suggestions
+ for improvement welcomed.
+
+ * (mdwtools.tex) Fixed /really/ stupid mistake in which made
+ typesetting the documentation about fifty times slower
+ than it should have been (bashes self on head several
+ times). Changed the structure here a bit too, to handle
+ document classes as well as packages. Made TeX much
+ quieter while it's typesetting the documentation.
+
+ * (sverb.sty) Fixed duff paragraph formatting in listing
+ environment and \verbinput command (due to the `wrong
+ sort' of grouping). (My excuse for missing this one is
+ that my standard document class sets \parskip=0pt.)
+
+ * (mdwtools.ins) Fixed this in line with the documentation
+ which hints that it should work with older docstrips.
+ It's a bit hacky but it works.
+
+
+1.02 * (gpl.tex) Fixed some bugs which made typesetting go wrong
+ in larger documents. Restructured preamble so that it
+ can be typeset on its own. Put in eplicit item numbers
+ in the enumerate environments, for more obvious conformance
+ to the original.
+
+ * (mdwtab.sty) Lots of changes here, many suggested by
+ David Carlisle (so oodles of thanks to him for taking
+ an interest in my humble hackings). Fixed bugs, including
+ one which put entirely incorrect interline spacing in
+ `p' type columns. Redone the handling of [t] and [b]
+ tables with top and bottom rules, and removed the
+ `\rulefudge' parameter which is no longer necessary.
+ Miscellaneous other changes.
+
+ * (mdwtab.dtx) Tidied up some nastinesses in the
+ documentation, and removed the `\over' commands from the
+ maths demos, to keep certain people happy. Floated a few
+ more of the demonstrations to make page breaking better.
+ There's a danger that some of the demos are drifting too
+ far away from their text, but it's not too bad yet.
+
+ * (syntax.sty) Used \doafter here to fix some colour handling
+ problems.
+
+ * (syntax.sty) Tidied up the `grammar' environment quite a
+ bit (it now uses `\item', rather than trying to emulate it
+ internally), and fixed some vicious bugs in it and some
+ other code.
+
+ * (doafter.sty etc.) A new addition, to make the various
+ packages handle colour properly. Mainly written by
+ Peter Scmitt, actually, I just fiddled with it a little.
+ Then Peter gave me a better version, and I've tried to
+ upgrade this one.
+
+ * (footnote.sty) A new addition, to offer some shared things
+ for handling footnotes. It also enables footnotes in
+ parboxes, which used to be difficult, and provides a
+ `footnote' environment which allows verbatim text.
+
+ * (mdwlist.sty} A new addition, providing miscellanous
+ list-related macros. It's a sort of mixed bag of things
+ I've had lying around various document preambles, combined
+ with some ideas from the Companion.
+
+ * (at.sty) Rewritten command name parser to be much nicer.
+ Added support for digits within @-command names (subject
+ to being enabled by an option). This is in response to
+ requests in comp.text.tex for digits in command names.
+
+ * (mathenv.sty) Totally overhauled the matrix spacing rules.
+ Added `script' environment. Improved numbering things,
+ with `\eqnumber'.
+
+ * (mdwtools.tex) Some minor changes here to fix some buglets.
+ Played with some more float parameters, to discourage
+ float pages a bit more. Then revamped completely, turned
+ into a docced program (although it isn't docstripped),
+ rewritten title generation, and made much more
+ customisable.
+
+
+1.02a * (mdwtab.sty) Added support for table beautification in
+ longtable. Documented how to do this.
+
+
+1.03 * (mdwtab.sty) Completely redone the paragraph-cell handling:
+ list environments now work properly inside tables (without
+ funny extra space appearing at the top and bottom). Also
+ fixed a bug in the newline handling, which ignored negative
+ interrow space in the \\ command.
+
+ * (syntax.sty) Changed the underscore handling, and some
+ other bits, to fit in rather better with LaTeX's output
+ encoding system. It's nastier and hackier inside, but it
+ works better with things like the DC fonts. Also stopped
+ re-lowercasing of `~' from escaping and messing everything
+ up for everyone. Improved underscore appearance by
+ lowering it some more.
+
+ * (syntax.sty) Replaced some `2's with `\tw@'s. Added a
+ comment about dvips's inaccurate positioning of rules.
+
+ * (sverb.sty) Made non-* environments build end text from
+ the name of the current environment, rather than having it
+ hardcoded. Also stopped `unignore' environments being
+ a group.
+
+ * (sverb.dtx) Removed some porkies from the documentation.
+
+ * (mdwtab.sty) Fixed some miscellaneous typos. Removed
+ `\rulefudge' from the table of tweakables, because it
+ was withdrawn in release 1.02.
+
+ * (cmtt.dtx) New package, for handling the `cmtt' font
+ better. It introduces a special encoding for the font,
+ and provides a command which allows you to use all the
+ characters without the disadvantages of verbatim text.
+
+ * (other changes) Improved distribution building and
+ testing stuff which you can't see because I'm not
+ releasing it.
+
+
+1.04 * (syntax.sty) Provided some new commands for playing with
+ interword spacing in `tt' fonts.
+
+ * (doafter.dtx and footnote.dtx) Added some docstrip guards
+ around the meta-comments, so that the charactertable and
+ the GPL header aren't put into other packages.
+ Unfortunately the version of docstrip which understands
+ this hasn't been released yet...
+
+ * RCSified everything, so I can find old revisions, and I'm
+ less likely to destroy everything.
+
+ * (footnote.dtx) Added a check for AMS environments doing
+ measuring passes, to avoid duplicated footnotes. (Spotted
+ by Roberto Bagnara.)
+
+
+1.05 * (mdwtab.dtx) Fixed stupid bug in paragraph cells which
+ left 1000pt high table rows. (Spotted by Rowland.)
+
+ * (mdwtab.dtx) Fixed horizontal spacing problems with
+ empty paragraph cells.
+
+ * (mdwlist.dtx) Allowed compact lists and resumed lists
+ to pass arguments on to the underlying environments.
+
+ * (syntax.dtx) Fix bug affecting underscore handling in
+ syntax abbreviations.
+
+--- Future plans ---
+
+doafter.sty Add Peter Schmitt's testing for implicit/explicit braces,
+ as a package or docstrip option. (This extra testing is
+ a significant chunk of code, and I don't think it's worth
+ burdening the standard version with it. Peter agrees with
+ me.)
+
+mathenv.sty Do postprocessing on display maths environments to position
+ the equations and equation numbers properly, so they don't
+ overlap (like the AMS environments do, although more
+ robustly). Once this is done, I think I'll have a reasonable
+ case for saying that this provides an alternative to the
+ AMS environments, although quite what the advantage is I
+ don't know: mdwtab.sty isn't exactly small.
+
+ Work is currently `in progress' on this one.
+
+mdwtab.sty Consider doing postprocessing on tables (yuk) in a blkarray
+ sort of way.
+
+footnote.sty Merge with Robin Fairbairn's package of the same name. Allow
+ different rules for continued notes (suggested by Donald
+ Arseneau, after a news article by Jonathan Wand).
+
+New packages I'm currently working on a little something for typesetting
+ poetry properly (centring poems horizontally based on the
+ longest line, etc.), handling footnotes properly, doing
+ line numbering etc. If anyone has any wishes for this,
+ little things a tyro like me ought to know, or knows that
+ it's already done better than I could manage, then let me
+ know.
+
+
+--- Contacting the author ---
+
+The author can be reached by email at mdw@excessus.demon.co.uk. This is his
+personal dial-up account, paid for privately, so don't expect replies after
+five minutes or anything like that.
+
+If you do have any comments regarding the code, its documentation, or
+anything else to do with these packages, don't leave me guessing -- let me
+know. While I won't guarantee to do anything about your comments, chances
+are that I'll right any wrongs and rescue any damsels in distress (oh, no,
+wrong spiel).
+
+
+-----------------------------------------------------------------------------
diff --git a/Master/texmf-dist/doc/latex/mdwtools/at.dvi b/Master/texmf-dist/doc/latex/mdwtools/at.dvi
deleted file mode 100644
index bc4d45fc3af..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/at.dvi
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/mdwtools/cmtt.dvi b/Master/texmf-dist/doc/latex/mdwtools/cmtt.dvi
deleted file mode 100644
index 9225f0c391e..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/cmtt.dvi
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/mdwtools/doafter.dvi b/Master/texmf-dist/doc/latex/mdwtools/doafter.dvi
deleted file mode 100644
index 98233f66aca..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/doafter.dvi
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/mdwtools/footnote.dvi b/Master/texmf-dist/doc/latex/mdwtools/footnote.dvi
deleted file mode 100644
index 6b4222b3041..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/footnote.dvi
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/mdwtools/mdwlist.dvi b/Master/texmf-dist/doc/latex/mdwtools/mdwlist.dvi
deleted file mode 100644
index 485a68ce4ff..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/mdwlist.dvi
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/mdwtools/mdwmath.dvi b/Master/texmf-dist/doc/latex/mdwtools/mdwmath.dvi
deleted file mode 100644
index 3a776e7e9ad..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/mdwmath.dvi
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/mdwtools/mdwtab.dvi b/Master/texmf-dist/doc/latex/mdwtools/mdwtab.dvi
deleted file mode 100644
index 603e07cd022..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/mdwtab.dvi
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/mdwtools/sverb.dvi b/Master/texmf-dist/doc/latex/mdwtools/sverb.dvi
deleted file mode 100644
index b40f47f4ced..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/sverb.dvi
+++ /dev/null
Binary files differ
diff --git a/Master/texmf-dist/doc/latex/mdwtools/syntax.dvi b/Master/texmf-dist/doc/latex/mdwtools/syntax.dvi
deleted file mode 100644
index b9036610362..00000000000
--- a/Master/texmf-dist/doc/latex/mdwtools/syntax.dvi
+++ /dev/null
Binary files differ