Fixed some readme layout issues
This commit is contained in:
Binary file not shown.
Binary file not shown.
2
Makefile
2
Makefile
@@ -1,4 +1,4 @@
|
|||||||
SOURCEs=README EK-VAXAA-4P-001.tex EK-VSTAA-MG-001.tex
|
SOURCES=README.tex EK-VAXAA-4P-001.tex EK-VSTAA-MG-001.tex
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
13
README.md
13
README.md
@@ -25,12 +25,13 @@ The reason for this is twofold:
|
|||||||
# How we are doing it
|
# How we are doing it
|
||||||
|
|
||||||
It is highly likely (backed up by some evidence from the documentation
|
It is highly likely (backed up by some evidence from the documentation
|
||||||
itself[^1] is written in LaTeX. In order to try and maintain as much of
|
itself[^1]) the original documentation is written in LaTeX. In order to
|
||||||
the original layout and pagination as closely as possible to the
|
try and maintain as much of the original layout and pagination as
|
||||||
original LaTeX has again been chosen as the method to re-create the
|
closely as possible to the original LaTeX has again been chosen as the
|
||||||
documentation. This also lets us separate out the style from the content
|
method to re-create the documentation. This also lets us separate out
|
||||||
making it much faster, once suitable document classes have been created,
|
the style from the content making it much faster, once suitable document
|
||||||
to recreate documents with the minimum of effort.
|
classes have been created, to recreate documents with the minimum of
|
||||||
|
effort.
|
||||||
|
|
||||||
# Contributing
|
# Contributing
|
||||||
|
|
||||||
|
|||||||
BIN
README.pdf
BIN
README.pdf
Binary file not shown.
@@ -30,7 +30,7 @@ The reason for this is twofold:
|
|||||||
\section{How we are doing it}
|
\section{How we are doing it}
|
||||||
|
|
||||||
It is highly likely (backed up by some evidence from the documentation itself\footnote{For example using a space separated console prompt such as {\tt > > >}
|
It is highly likely (backed up by some evidence from the documentation itself\footnote{For example using a space separated console prompt such as {\tt > > >}
|
||||||
to combat \LaTeX\ conversion of {>}{>} into >> } is written in \LaTeX. In order to try and maintain as much of the original layout and pagination as closely
|
to combat \LaTeX\ conversion of {>}{>} into >> }) the original documentation is written in \LaTeX. In order to try and maintain as much of the original layout and pagination as closely
|
||||||
as possible to the original \LaTeX\ has again been chosen as the method to re-create the documentation. This also lets us separate out the style from the content
|
as possible to the original \LaTeX\ has again been chosen as the method to re-create the documentation. This also lets us separate out the style from the content
|
||||||
making it much faster, once suitable document classes have been created, to recreate documents with the minimum of effort.
|
making it much faster, once suitable document classes have been created, to recreate documents with the minimum of effort.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user