
%% The cstrip manual
%% (C) 1998, Petr Ol\v s\'ak

%% WARNING: do not process this file by csplain until you know
%%          that your csplain is correctly installed.
%%          The cstripm.dvi or cstripm.ps may be destroed!
%%          Use the original cstripm.dvi or cstripm.ps for
%%          information how to valiadte the csplain format.

\ehyph  % use format: csplain
\exhyphenpenalty=10000
\newcount\num
{\obeyspaces \gdef\activespace{\obeyspaces\let =\ }}
\def\setverb{\def\do##1{\catcode`##1=12}\dospecials}
\def\ttinput #1 {\bigskip \begingroup
   \par \setverb \activespace \def\par{\endgraf\indent}\obeylines\tt
   \input #1 \endgroup \vfill\break}

\def\b #1.{\medskip\noindent\hbox to\parindent{\bf{#1.}\hfil}\ignorespaces}
\def\ttshow #1\par{\par\nobreak\medskip\indent{\tt #1}\medskip}

\def\CS{$\cal C\kern-.1667em\lower.5ex\hbox{$\cal S$}\kern-.075em $}
\chardef\\=`\\

\def\titul#1\par{\bigskip\noindent{\bf#1}\medskip}
\def\sub#1\par{\par\bigskip\noindent{\bf#1}\par\nobreak\medskip}



\titul The Test of the Validity of {\tt csplain} format
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

The aim of this test is to check the functionality of the format
{\tt csplain}. The suitability of the \TeX{} binary used in Czech and
Slovak environment with {\tt csplain} format is checked too.
The {\tt csplain} have to give {\it the same results\/} on {\it every\/}
operating system where the Czech and Slovak alphabet is implemented.
This provides the transfer of {\tt csplain} documents between operating
systems without problems.

The independence of \TeX{} kernel is supported with another instruments,
thus this test is designed to check the only one matter which is very
important for working with Czech and Slovak languages, of course.
This test check the processing of {\tt csplain} format on text files
where the Czech and/or Slovak alphabet is encoded by standard used in your
operating system. The existence of this test is the result of an existence
of many encoding standards for our alphabets in different operating
systems.

We suppose the Czech/Slovak documents in text files ({\tt *.tex} for
example) will be always converted immediately into encoding standardized
in host system after transferring it from another system. No matter, if this
work is done automatically (in e-mail clients or by intelligent
connection of www server/client or by new extended protocols) or if the
user have to do this work manually (using a text editor function or
using an external program). If the user see in his/her text editor the
letter \v z (for example), the same letter must be shown in {\tt dvi}
output and (if needed) in {\tt log} file and output text files using
{\tt\\write}.

The {\tt dvi} \TeX{} output is system independent and the fonts for
{\tt dvi} drivers are system independent too. This implies, the re-encoding
from various encoding standard used in operating systems must be done
by \TeX{} program itself. The non identity re-encoding is needed if your
system has different encoding for Czech/Slovak alphabet from ISO-8859-2
because this encoding is adopted as internal \TeX{} encoding in
{\tt csplain} format.


\sub The steps of the cstrip test
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

There are files {\tt cstrip.tex}, {\tt cstripl.vrf} and {\tt cstripd.vrf}
in {\tt csplain} distribution. You have to have some implementation of
Czech and/or Slovak alphabet in your system.

\b 1. Look the files {\tt cstrip.tex} and {\tt cstripl.vrf} in your text
editor. If there are not all accented characters correct
(see appendixes A and B) you must to convert these files into your encoding
using some tools in your operating system. For your information, the files
in {\tt csplain} distribution are encoded in ISO-8859-2 (UNIX text files).
The end-of-line mark(s) may be different in your operating system. Convert
all master files into the text files with the end-of-line marks used in
your operating system. Check that the files after your conversion exactly
matches with encoding standard and end-of-line mark(s) in your operating
system and save this (probably corrected) files on your disk.

\b 2. If the {\tt csplain} format is not generated, install it (see the {\tt
csplain.doc} or {\tt csplaine.doc}

\b 3. Run \TeX{} with {\tt csplain} format on the file {\tt cstrip.tex}.
This process is system dependent. Usually, you can say on your command
prompt:

\ttshow csplain cstrip

\noindent
The files {\tt cstrip.log} and {\tt cstrip.dvi} are generated. You can
convert the {\tt cstrip.dvi} into {\tt cstrip.log} using the {\tt dvitype}
program:

\ttshow dvitype cstrip.dvi cstrip.txt

\b 4. Check, if the file {\tt cstrip.log} has no differences from the master
file {\tt cstripl.vrf}. Check, if the file {\tt cstrip.txt} has no
differences from the master file {\tt cstripd.vrf}.

\b 5. If you cannot run the {\tt dvitype} program, the visual check of the
``look'' of the appendix~D and the {\tt cstrip.dvi} in your {\tt dvi}
viewer is sufficient.


\sub What differences are permitted
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\b 1. The first (and probably next) line includes the banner. The program
name, version, date of format and date of document processing are presented
here. These statements may be different. The version of the format after the
words:

\ttshow The format: csplain

\noindent can be different. The statement in your {\tt log} file similar
with this:

\ttshow The CP1250->ISO-8859-2 re-encoding is activated by encTeX

\noindent may be present.

\b 2. Some numeric data can be slightly different in the {\tt cstrip.txt}
file. See the TRIP manual by Don Knuth for more details.

\b 3. Some implementations of \TeX{} define a different length of line
in the {\tt log} file (usually the 80 character length of lines are set).
Thus, the text in {\tt cstrip.log} may be broken differently into lines
than in {\tt cstripl.vrf}.


\sub What differences are not permitted
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

All another differences not mentioned in the previous paragraph are not
permitted. If some difference occurs, the {\tt csplain} format is not
correctly installed. We will show two current problems:

\b 1. Some code equation of type {\tt 193=193} is not correct in
{\tt cstrip.log} file. This error is fatal, because this implies that some
Czech/Slovak letters may be destroyed in {\tt dvi} output.

\b 2. The file {\tt cstrip.log} includes the sequences of type
{\tt\char`\^\char`\^ae} instead of the right accented letters. This error
is fatal too. The manipulation of Czech/Slovak text files using
{\tt\\write} primitive is not possible.

\medskip

The comments about reparation: You can change the ``system dependencies''
sections 21 and 23 in {\tt tex.web} source file using {\tt tex.ch} file.
Then compile the \TeX{} binary again. This policy is in compliance with the
Knuth's license of \TeX{}. But problems arise. You have to have the various
\TeX{} binaries because various \TeX{} internal encodings (8-bit) and various
encodings adopted in operating systems exist. In addition, it is impossible
to compile the \TeX{} binary from {\tt web} sources on many \TeX{}
implementations.

Much better solution is to use the enc\TeX{} (see the README file in
the {\tt enctex} package). You can set the input re-encoding of \TeX{}
and printability of characters in the {\tt log} and {\tt\\write} files
during ini\TeX{}. Another solution is to use the em\TeX{}
binary (for DOS and OS/2) with {\tt -8} parameter and an appropriate
{\tt tcp} table.


\sub Comments about passive using of {\tt csplain}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

It is possible, that the the {\tt cstrip.dvi} file match with its master
file if you keep the input {\tt cstrip.tex} in ISO-8859-2. If your
operating system does not support this encoding at all, you can process
many documents designed in {\tt csplain} from the network in this encoding.
We call that you use the {\tt csplain} in passive mode. This mode is
sufficient for non Czech/Slovak users, but it is unusable for current work
with Czech/Slovak languages.

If only passive mode is possible on your implementation of \TeX{}, we must
say that the {\tt csplain} is not installed correctly. The cstrip test is
not fulfilled. It is not permitted to distribute the {\tt csplain} in
environment without any possibility of correct implementation of this format.

\bigskip

October 1998 \hfill Petr Ol¹įk

\vfill\break

\sub Appendix A~-- The contents of the file {\tt cstrip.tex}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

The file {\tt cstrip.tex} have to have the ``look'' in your editor in
the following way:

\ttinput cstrip.tex


\sub Appendix B -- The contents of the file {\tt cstrip.log}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

The {\tt cstrip.log} have to have the following contents:

\ttinput cstripl.vrf


\sub Appendix D -- The contents of the file {\tt cstrip.txt}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

You can process the {\tt dvitype} program on {\tt cstrip.dvi}.
The output may look as this:

\ttinput cstripd.vrf


\sub Appendix D -- The {\tt cstrip.dvi} in your dvi viewer
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

If you cannot use the {\tt dvitype} program, you can uze the dvi
viewer on {\tt cstrip.dvi}. The result have to be the same like
following: 


\bigskip
\begingroup
\let\bye=\relax
\input cstrip
\endgroup

\end

