\documentstyle[11pt,wp2latex]{report}

\newcommand{\arrow}{$\rightarrow$}
\renewcommand{\thechapter}{}
\renewcommand{\thesection}{\arabic{section}}
\renewcommand{\thefigure}{\arabic{figure}}

\title{\WPtoLaTeX\\
 \hspace{1cm}\\
       User's Guide}
\author{R.C. Houtepen\thanks{Translated from the Dutch by G. R. Roelofs}\\
	Jaroslav Fojt\'{\i}k}

\begin{document}

\maketitle

\newpage

\pagenumbering{roman}
\tableofcontents

\newpage

\pagenumpos{\pnbc}
\pagenumbering{arabic}

\section{Introduction}

There is another version of \WPtoLaTeX\ written from scratch
by the original author R. C. Houtepen at TUE-Eindhoven. This version
differs completely from the package in your hand. Please check it on
your nearest CTAN host at:

\begin{verbatim}
    tex-archive/support/wp2latex/*    .
\end{verbatim}

The version there has the disadvantage, that there isn't any source code
available. The source code in the subdirectories is very old. I tried
hardly to contact the author but failed. So I took the latest available
sources (which based on these in the subdirectories mentioned above)
and corrected some errors. I never checked the other version. I apologize
everybody to compare both versions and tell me the conclusion.


\WPtoLaTeX\ was originally designed to translate WordPerfect 5.0 documents
into \LaTeX\ 2.09. Later some code was added to translate also WordPerfect 5.1
documents. Now the preamble is designed for \LaTeX\ 2e (by changing the
preamble by hand it runs also under \LaTeX\ 2.09 of course).

The programming language used was Turbo Pascal 7.0 and C++. The pascal version
will be no longer supported from me. Only severe bugs will be corrected.
C++ code has been ported to OS/2, DOS DJGPP and Linux operation
systems.

The projection from one paradigm (WordPerfect = word processing) to another
(\LaTeX\ = typesetting) requires some cooperation on the part of the user.
Because the use of \LaTeX\ is tied to strict rules, one must take these rules
into consideration when using WordPerfect, if the WordPerfect 5.0 document is
to be converted as accurately as possible.  This guide discusses those rules.

\subsection{Some general remarks}

\begin{enumerate}
\item {Don't expect a better looking result only caused by converting text
   from WordPerfect to \LaTeX. You HAVE TO edit the resulting \LaTeX\ files.
   The reason is, that wordprocessors didn't give the structure
   of the text (sections, itemizations, labels, ...) but only
   the formatting (boldface, underline (uurgh), italic, ...).}

\item {See next section for conversion abilities}

\item {Don't expect any miracles from this program.}
\end{enumerate}


\subsection{Authorship history}

\WPtoLaTeX\ was written in Turbo Pascal by R. C. Houtepen at TUE-Eindhoven.
It was converted into C using p2c, and modified, by Glenn Geers (Sydney U).
It was further modified by Michael Covington (U of Georgia).
Modified to be used in unix/linux environment by Claudio Porfiri.
The parsing of formulas was added by Dirk Lellinger (U Halle/Germany).
The splitting of code into several files and the documentation
was done by Andreas Tille.
J Fojtik developed original version from R. C. Houtepen at TUE-Eindhoven
and then tried to give all available versions together.


\newpage

\section{Conversion possibilities}
\label{capabilities}

Because the capabilities of WordPerfect and \LaTeX\ differ strongly, it is
not possible to convert all of WordPerfect's `features'.

\subsection*{
The conversions which are performed by \WPtoLaTeX\ (when converting WP4.x
documents) are:}

\begin{itemize}\setlength{\itemsep}{-1mm}
  \item Center page
  \item Comment
  \item Contents
      \begin{itemize}\setlength{\itemsep}{-1mm}
      \item Mark To Contents
      \item Table of Contents
      \end{itemize}
  \item Date Code
  \item Endnotes
  \item Extended characters (one charset 256 with chars)
  \item Flush-right text
  \item Footnotes
  \item Headers and footers
  \item Hard page breaks
  \item Hard returns
  \item Hyphenation ~~ On/Off
  \item Indenting :
  \item Index
      \begin{itemize}\setlength{\itemsep}{-1mm}
      \item Mark To Index
      \item Table of Indices (makeindex is required)
      \end{itemize}
  \item Justification :
      \begin{itemize}\setlength{\itemsep}{-1mm}
      \item right
      \item center
      \item full
      \end{itemize}
  \item Language
  \item Marks ToContents
  \item Newspaper-style columns (experimental max only 2)
  \item Overstriking
  \item Page number positioning
  \item Page numbers
  \item Page number set
  \item Soft Hyphen
%  \item Tab Settings
  \item The following Typefaces :
    \begin{itemize}\setlength{\itemsep}{-1mm}
      \item Superscript
      \item Subscript
      \item Bold
      \item Underlined
      \item Double-underlined
      \item RedLine (Only \LaTeX 20e)
    \end{itemize}
  \item Widow Orphan ~~ On/Off
\end{itemize}




\subsection*{
The conversions which are performed by \WPtoLaTeX\ (when converting WP5.x
documents) are:}

\begin{itemize}\setlength{\itemsep}{-1mm}
  \item Abstract
  \item Advances
  \item Center page
  \item Colors (Only \LaTeX 20e)
  \item Comment
  \item Contents
      \begin{itemize}\setlength{\itemsep}{-1mm}
      \item Mark To Contents
      \item Table of Contents
      \end{itemize}
  \item Cross-references
  \item Date Code
  \item Endnotes
  \item Equations
  \item Extended characters (foreign language/accented, math, Greek)
  \item Flush-right text
  \item Footnotes
  \item Headers and footers
  \item Hard page breaks
  \item Hard returns
  \item Hyphenation ~~ On/Off
  \item Indenting :
    \begin{itemize}\setlength{\itemsep}{-1mm}
      \item left
      \item left and right
    \end{itemize}
  \item Index
      \begin{itemize}\setlength{\itemsep}{-1mm}
      \item Mark To Index
      \item Table of Indices (makeindex is required)
      \end{itemize}
  \item Justification :
      \begin{itemize}\setlength{\itemsep}{-1mm}
      \item left
      \item right
      \item center
      \item full
      \end{itemize}
  \item Labels
  \item Language
  \item Marks ToContents
  \item Newspaper-style columns (using \verb|multicol.sty|)
  \item Outlining
  \item Overstriking ~ (and also attribute changes inside overstrikes)
  \item Page number positioning
  \item Page numbers
  \item Page number set
  \item Soft Hyphen
  \item Tab Settings
  \item Tabs :
    \begin{itemize}\setlength{\itemsep}{-1mm}
      \item setting
      \item left tabs
      \item center tabs
      \item right tabs
    \end{itemize}
  \item Tables
  \item Table boxes
  \item Table of contents
  \item Text boxes
  \item The following Typefaces:
    \begin{itemize}\setlength{\itemsep}{-1mm}
      \item Extra large
      \item Very large
      \item Large
      \item Small
      \item Fine
      \item Superscript
      \item subscript
      \item Bold
      \item Italic
      \item Overstrike
      \item Small caps
      \item Underlined
      \item Double-underlined
      \item RedLine (Only \LaTeX 20e)
    \end{itemize}
  \item Title
  \item Widow Orphan ~~ On/Off
\end{itemize}

\noindent
{\bf Not} converted are :
\begin{itemize}\setlength{\itemsep}{-1mm}
  \item margin settings
  \item top and bottom margins
  \item graphics boxes
  \item the calculations in tables
  \item and many other WP features ...
\end{itemize}


\subsection*{
The conversions which are performed by \WPtoLaTeX\ (when converting WP6.x
documents) are:}


\begin{itemize}\setlength{\itemsep}{-1mm}
  \item Center page
  \item Colors (Only \LaTeX 20e)
  \item Comment (also nested ones)
  \item Cross-references
  \item Endnotes
  \item Extended characters (foreign language/accented, math, Greek - not linedrawing),
	but some of them badly.
  \item Filename
  \item Flush-right text
  \item Footnotes
  \item Hard page breaks
  \item Hard returns
  \item Headers and footers
  \item Indenting
  \item Newspaper-style columns (using \verb|multicol.sty|)
  \item Page number set
  \item Page numbers
  \item Tables
  \item Table boxes
  \item Table of contents
  \item Text boxes
  \item Typefaces list follows:
    \begin{itemize}\setlength{\itemsep}{-1mm}
      \item Extra large
      \item Very large
      \item Large
      \item Small
      \item Fine
      \item Superscript
      \item subscript
      \item Italic
      \item Small caps
      \item Bold
      \item Underlined
      \item Double-underlined
      \item RedLine (Only \LaTeX 20e)
    \end{itemize}
  \item Widow Orphan ~~ On/Off  
\end{itemize}

\nwln
\noindent
{\bf Not} converted are all other features for this case.


\newpage


\section{The program}

\noindent
The program is invoked with the command:

\begin{verbatim}
   WP2LATEX [/? | /-help]
    [WP-filename.WP [TeX-filename.TEX]] [ /i WP-filename.WP] [/o TeX-filename.TEX]
    [ /l Log-filename.TXT ] [ /amssymb ] [ /bbm ] [ -configfile filename | -@ filename ]
    [ /copyright ] [ /cp-codepage ] [ /cp-styles ] [ /charset1 | /charsetCZ ]
    [ /extract-WPG ] [ /fancyhdr ] [/forceWP4] [ /ignore-tabs ] [ /input-PS ]
    [/L language] [ /LaTeX2 | /LaTeX3 ] [ /latexsym ] [ /no-amssymb ]
    [ /no-bbm ] [ /no-columns ] [/no-erase-strip] [ /no-extract-WPG ]
    [ /no-input-PS ] [ /no-latexsym ] [ /no-safemode ] [ /no-texchars ]
    [ /no-wasy ]  [ /s "password" ] [ /S | /silent] [/safemode] [ /silent ]
    [ /texchars] [ /v ] [ /wasy ]

\end{verbatim}

\bigskip
\noindent
Following Unix-like call style is also possible:

\begin{verbatim}
   WP2LATEX [-? | --help]
    [WP-filename.WP [TeX-filename.TEX]] [ /i WP-filename.WP] [/o TeX-filename.TEX]
    [ -l Log-filename.TXT ] [ -amssymb ] [ -bbm ] [ -configfile filename | -@ filename ]
    [ -copyright ] [ -cp-codepage ] [ -cp-styles ] [ -charset1 | -charsetCZ ]
    [ -extract-WPG ] [ -fancyhdr ] [-forceWP4] [ -ignore-tabs ] [ -input-PS ]
    [-L language] [ -LaTeX2 | -LaTeX3 ] [ -latexsym ] [ -no-amssymb ]
    [ -no-bbm ] [ -no-columns ] [-no-erase-strip] [ -no-extract-WPG ]
    [ -no-input-PS ] [ -no-latexsym ] [ -no-safemode ] [ -no-texchars ]
    [ -no-wasy ]  [ -s "password" ] [ -S | -silent] [-safemode] [ -silent ]
    [ -texchars] [ -v ] [ -wasy ]
\end{verbatim}

\subsection{Description of command line arguments}

\nwln
The parameter \verb|WP-filename.WP|\footnote{This may be a WordPefect 5.0
document with an extension other than \verb|.WP|} is optional.
The program starts with an opening screen and asks for the WordPerfect
filename.  The default filename is printed inside square brackets
\mbox{(\verb|[ ]|)} and is the parameter which was optionally included in
the initial invocation of \verb|WP2LATEX|\null.  The user can at this point type
in another WordPerfect filename, or he can hit return to choose the default
filename. The program next requests the name of the generated \LaTeX\
document. The default given within brackets is the name of the
WordPerfect file, with the extension \verb|.TEX|\null or
\verb|TeX-filename.TEX| passed as second argument.  Once again the user
may accept this name or enter another\footnote{This may be a file with an
extension other than \verb|.TEX|}.  Once the filenames are given, the 
following error messages may appear :

\begin{itemize}
  \item \Underline{File not found :} The given WordPerfect file does not exist.
  \item \Underline{Path not found :} An invalid path was given in the name
        of one of the files.
  \item \Underline{Not a WordPerfect 5.x document :} The given WordPerfect
	file was not created in WordPerfect 5.x
\end{itemize}

Arguments \verb|/cp895| ; \verb|/cp1250|  or  \verb|/cp852| are used for 8. bit \TeX, which is able
to process some of these code pages. The codepage \verb|/cp895| is called as
Kameni\v{c}t\'{\i} and is often used in central Europe. The codepage
\verb|/cp895| (ISO8) is preferred in DOS for central Europe and
the codepage \verb|/cp1250| is designed for central Europe Windows.

If you try to convert documents from WP version 4.x then tis program normally
says that you have no WP file. The reason is that WP 4.x format gives no chance
for autodetection. If you are sure that you have a WP 4.x file turn the
switch \verb|-forceWP4| on.

There are available several types of coding accented characters.
It is too bad. I guess that coding char set 1 is most common.
Thus switch \verb|/charset1| is default set.
If user wants to switch to the another coding, he should add switch
\verb|/charsetCZ|. But I have no available description of this coding
and only several characters will be converted properly.

Switch \verb|/L language| turns on the translation features. These features
are based on the gettext library, which must be properly installed.
This means, that the system variable \verb|LOCALEDIR| should be properly
set. If not, then the program \verb|wp2latex| looks for the file referred in
the \verb|DJGPP| and attempts to find the description of \verb|LOCALEDIR|.
The system variable \verb|LANGUAGE| has same meaning, but the
command line switch has stronger influence.

Switch \verb|/noerase-strip| is intended for debugging purposes. The program
do not erase all temporary files so you can analyze them later.

If you turn the switch \verb|-safemode| on, you can convert even corrupted WP
wiles which hang WordPerfect well. All internal objects are tested and
corrupted ones are digged out. If you don't want this feature then omit this
switch. Do not expect better conversion from this feature.
In most cases it only slow down a conversion. But if your documents are really
corrupted, the conversion results may be better due to fixing errors.

Switch \verb|/texchars| allows using WordPerfect as a \TeX\ editor. If this switch
is active, then controlling \TeX\ sequences are not distorted and
you can add for example new equation (in the WP equation editor),
which will be converted.


If you want to use some switch very often, it is possible to set a system variable
\verb|wp2latex|. This variable is read before a command line is processed.
For example you may want to set output codepage 895 and language
CS. \verb|wp2latex=-cp985 -L cs|.

\subsection{Program Behaviour}

The conversion takes place in two passes.  In the first pass the WordPerfect
input-file is read in, byte by byte.  On the basis of that are created two
files, \verb|WP-filename.STR| and \verb|WP_filename.TBL|\null.
\verb|WP-filename.STR| contains the characters, tab settings and changes of
typefaces; \verb|WP-filename.TBL| holds information regarding the various
\LaTeX\ environments that must be opened and closed.  In the second pass these
files are assimilated into a single \LaTeX\ file.  After a successful
conversion the files \verb|WP-filename.STR| and \verb|WP-filename.TBL| are
automatically deleted.

%\newpage

Invoking \WPtoLaTeX\ to convert the WordPerfect 4.x,5.x or 6.x document
\verb|C:\WPTEST\TEST.WP5| will cause the following screen to appear:

\begin{verbatim}

 >>>WP2LaTeX<<< Conversion program: From Wordperfect to LaTeX Version 2.71

  (c) TUE-Eindhoven ---- Made by R.C.Houtepen ---- Date : 24 Jan 1990
  (c) CVUT Prague   ---- Made by J.Fojtik     ---- Date : 1996 - 1999


WordPerfect-filename [ ] :  c:\wptest\test.wp5
LaTeX-filename [c:\wptest\test.TEX] :

Converting ...

First pass :
Converting-percentage : 100%

Second pass :
Converting-percentage : 100%

Conversion completed.

\end{verbatim}

The first line of the generated \LaTeX\ file, in the case of the file
\verb|C:\WPTEST\TEST.TEX|, will look as follows:

\begin{verbatim}
   \documentstyle[11pt,wp2latex]{report}
\end{verbatim}
\nwln

When calling \LaTeX\ to typeset the converted document, the style file
\verb|WP2LATEX.STY| should be in the current directory or in the style-file
directory (e.g., \verb|\PCTEX\TEXINPUT|).
This style file defines a number of macros and environments which are
regularly used in the generated \LaTeX\ files.  Examples include the command
\verb|\nwln| and the \verb|indenting| environment. \verb|\nwln| generates a
hard carriage return after the end of a \LaTeX-environment.  The
\verb|indenting| environment is used in the conversion of WordPerfect's
\verb|[|\arrow\verb|Indent]| command (see \S~\ref{indent}).

\section{How to install}

\subsection{Under DOS and OS/2}

You should place properly four files: \verb|wp2latex.exe|, \verb|wp2latex.sty|
\verb|endnotes.sty| and \verb|wp2latex.mo|.

Place the file \verb|wp2latex.exe| somewhere into your path. The good solution
is to place it to \verb|c:\emtex\| etc.

The path for files \verb|wp2latex.sty| and \verb|endnotes.sty| should be
available in the system variable \verb|texinput|. A good solution is to place them
to \verb|c:\emtex\texinput\|.

The last step is not required for proper behaviour of the program \verb|wp2latex|.
It the last file is not placed, then your program will not be abble to translate
output messages to your language (if the translation is available of course).
Merge the directory e.g. \verb|c:\gnu\share\locale\| with \verb|doc\locale\|.
Or you may have translations in the directory referred in the system
variable \verb|localedir|.


\subsection{Under Linux}

The installation is very easy. Change to the directory sources.cc and type
\verb|make install|. It is all.


\newpage

\section{Discussion about conversion reliability}

When I started to contribute to this convertor, I have read that after
conversion somebody must use several filters and special program to make a nice
\LaTeX\ output.
{\footnotesize \sc \it I have translated a huge WP file (about 1MB text) with a lot of
footnotes but no tables and formulas. To get a nice LaTeX format I wrote about 5 C-programs and about
40 sed-lines to convert some ugly formattings. After this I spend some time with manual editing.
At last I wrote a LaTeX-style for a nice looking document.
The whole procedure took me three days.}
It was too bad! I hope, that this is not true with a current release.

So I expect that the conversion should be done better. Thus I started to
improve convertor. Now it is something like AI (Artificial Intelligence)
project and the results are not excellent. Why?

\begin{enumerate}
\item Conversions performed by \WPtoLaTeX\ are only partial and some features
      are ignored.
\item In WordPerfect document are some unwanted
      codes (such as [Tab], [Tab Set], [indent] instead [Tab] etc.) I advise you
      to use [Tab] as small as possible.
\item Word Perfect allow anybody to do some terrible
      thinks which are in \LaTeX\ prohibited. For example
      \verb|\section{Some sect\tableofcontents ion}|. Many of them have been founded
      and fixed but I guess that number of such situations is very big.
\end{enumerate}


But don't worry so much. If your document is simple, you can use converted
\LaTeX\ file immediately with only minor changes. If your document become
complex, then you must check conversion results more carefully.
It is a good idea to print a converted file and compare it with original one.

If you expect, that something is removed from your document you can
try \verb|-l logfile.txt| option to see a list of all WP objects.


\section{Guidelines}

\subsection{Tabbing}

Tab settings allow the exact placement of pieces of text, e.g., for creating
tables. There are two sorts of commands involved here.  First, there is the
setting of tabs; this defines {\em where} subsequent tab-stop commands will
place text. Then there are the tabs themselves, which force a {\em jump} to
one of the previously-defined positions. In \LaTeX , however, tabs
are enabled only within a \verb|tabbing| environment. \WPtoLaTeX\ takes
care of that by invoking a \verb|tabbing| environment only for those lines
where one or more tabs appear.

Within WordPerfect, a line containing tabs must terminate with a hard
carriage return.  If this is not the case, the tab positions in the generated
\LaTeX-document will not be fixed.  \LaTeX\ will incorrectly typeset the
spacing of such lines.

\noindent
The following WordPerfect text will be incorrectly converted:

\begin{verbatim}
   Text1 [Tab] text2 [Tab] text3 [SRt]
   text4 [Tab] text5. [HRt]
\end{verbatim}
\nwln

\noindent
The following is better:

\begin{verbatim}
   Text1 [Tab] text2 [Tab] text3 [HRt]
   text4 [Tab] text5. [HRt]
\end{verbatim}
\nwln

A tab-setting in the middle of a line holds for the entire line in the 
converted document (unlike in WordPerfect).  It is
therefore advisable to set tabs at the beginning of or prior to the
pertinent line.

\medskip\noindent
{\bf Few restrictions:}

\LaTeX\ endows such commands as \verb|\'|, \verb|\`| and \verb|\=| with special
meanings within a \verb|tabbing| environment.  Outside a \verb|tabbing|
environment, these commands are used for the placement of accents; within
one, however, they must be replaced by \verb|\a'|, \verb|\a`| and \verb|\a=|, 
respectively.  \hbox{\WPtoLaTeX} does not perform this replacement, so it is 
left to the user to do it after the conversion.

WordPerfect 5.0 allows up to 40 tabstops to be set.  \LaTeX\ can set at most
14 of them.  As a result, if tabs are to be converted properly, the user may
set no more than 14 tabstops within WordPerfect, either.  If more than 14
tabs are set, processing by \LaTeX\ will result in a number of error messages,
and ultimately one or more tabs may be lost.

% \newpage

\subsection{Indenting}
\label{indent}

Indenting is used to alter the margins of pieces of text (paragraphs).
Possible conversions with regard to indenting commands are :

\medskip\noindent
Examples :

\begin{tabbing}
\verb|   [|\arrow\verb|Indent]|$^*$\verb|  |\=
        \verb|An indented paragraph which [SRt]| \\
     \> \verb|extends over several lines and [SRt]| \\
     \> \verb|is closed with a hard carriage [SRt]| \\
     \> \verb|return. [HRt]| \\
\end{tabbing}
\begin{tabbing}
\verb|   label  [|\arrow\verb|Indent]|$^*$\verb|  |
  \= \verb|We see here the possibility of [SRt]| \\
  \> \verb|placing a `label' in front of [SRt]| \\
  \> \verb|indented text. [HRt]| \\
\end{tabbing}
\begin{tabbing}
\verb|   [|\arrow\verb|Indent]|$^*$\verb|  label  [|
\arrow\verb|Indent]|$^*$\verb|  |
  \= \verb|It is also possible to place [SRt]| \\
  \> \verb|an `indented label' in front [SRt]| \\
  \> \verb|of indented text. [HRt]| \\
\end{tabbing}

\nwln
where \verb|[|\arrow\verb|Indent]|$^*$ indicates one or more 
\verb|[|\arrow\verb|Indent]| commands.

\vspace{1cm}

The indenting consists from three commands:\\
\verb|\testlastline|\\
~~~~~~~	This \TeX command replaces a \verb|\par| command. But
moreover it measure the length of the last paragraph line.

A command \verb|\zerolastline| assumes that the size of the last
paragraph line is zero.

A \LaTeX environment \verb|indenting| is used to indent a text.
In current release the limitation of two indents is broken, but
you cannot combine indents and tabs together.


\subsection{Combinations of tabbing and indenting}

In practice it is evident that tabbing and indenting commands are often
used together.  The effect of that within WordPerfect is often identical:
words come out on the page where one wishes, on the screen as well
as on paper (What You See Is What You Get).

In \LaTeX, however, the difference between tabs and indents is fundamental.
It is important that the WordPerfect-user take this into account.  Thus only
the \verb|[Tab]| command may be used for tabbing and only the 
\verb|[|\arrow\verb|Indent]| command for indenting.  If both tabbing and 
indenting commands are used within a single line, only the type which is 
encountered first will be converted.

\noindent
An example:
\begin{tabbing}
\verb|   [Tab] tom [Tab] dick [|\arrow\verb|Indent] harry [HRt]| \\
\end{tabbing}

The tab command in this line comes before the indenting command.  The
interpretation by \hbox{\WPtoLaTeX} is then:
\begin{tabbing}
\verb|   [Tab] tom [Tab] dick harry [HRt]|
\end{tabbing}

\noindent
The indent-command is eliminated.  The line should instead look as follows:
\begin{tabbing}
\verb|   [Tab] tom [Tab] dick [Tab] harry [HRt]|
\end{tabbing}



\subsection{Footnotes \& Endnotes}

Within a footnote only carriage returns and typefaces (see 
\S~\ref{capabilities}) are converted.  A footnote number may 
consist only of numerals.

Footnotes within lines which contain tab settings will not appear at the bottom
of the page; \LaTeX, in contrast to WordPerfect, does not process them.  This
is a limitation (read:  bug) of \LaTeX.

Endnotes are processed similarly as footnotes. Moreover an additional style
\verb|endnotes.sty| must be present in \TeX\ path for styles.
If you don't use endnotes in your WP document, the style
\verb|endnotes.sty| is not required.



\subsection{Headers and footers}

Within a header or footer a number of converted features is
reduced (see \S~\ref{capabilities}).

\noindent
One can split a header or footer into three pieces :
\begin{itemize}\setlength{\itemsep}{-1mm}
  \item left-aligned
  \item centered
  \item right-aligned
\end{itemize}
\nwln
These three parts are separated within WordPerfect by using the centering
command (Shift F6) and the flush-right command (Alt F6).

\noindent
The effect of the WordPerfect commands in the header

\begin{verbatim}
   Left[Cntr]Middle[C/A/Flrt][Flsh Rt]Right[C/A/Flrt]
\end{verbatim}
\nwln
will, after conversion to \LaTeX\ format, be interpreted as is shown in
figure~\ref{fig:header}.  Choosing a new setting for the placement
of header or footer text on only even (or only odd) pages does not affect 
the alternate pages' previous setting.

\begin{figure}[hbt]
\centering
\setlength{\unitlength}{3mm}
\begin{picture}(12,16)
 \thicklines
 \put(0,0){\framebox(12,16)}
 \put(1,14){\makebox(10,1)[l]{{\tiny Left}}}
 \put(1,14){\makebox(10,1){{\tiny Middle}}}
 \put(1,14){\makebox(10,1)[r]{{\tiny Right}}}
 \put(1,12){\line(1,0){10}}
 \put(1,11){\line(1,0){10}}
 \put(1,10){\line(1,0){10}}
 \put(1,9){\line(1,0){10}}
 \put(1,8){\line(1,0){10}}
 \put(1,7){\line(1,0){10}}
 \put(1,6){\line(1,0){10}}
 \put(1,5){\line(1,0){10}}
 \put(1,4){\line(1,0){10}}
 \put(1,3){\line(1,0){10}}
 \put(1,2){\line(1,0){10}}
\end{picture}
\caption{headers}
\label{fig:header}
\end{figure}

\subsection{Page number positioning}

The WordPerfect document is converted to a single-sided document.  This
means that page number positions 4 and 8 are not converted.  The page
number positions which \WPtoLaTeX\ will convert are reproduced in 
figure~\ref{fig:pagnr}.

\begin{figure}[hbt]
\centering
\setlength{\unitlength}{3mm}
\begin{picture}(12,16)
 \thicklines
 \put(0,0){\framebox(12,16)}
 \put(1,14){\makebox(10,1)[l]{1}}
 \put(1,14){\makebox(10,1){2}}
 \put(1,14){\makebox(10,1)[r]{3}}
 \put(1,1){\makebox(10,1)[l]{5}}
 \put(1,1){\makebox(10,1){6}}
 \put(1,1){\makebox(10,1)[r]{7}}
\end{picture}
\caption{page number positions}
\label{fig:pagnr}
\end{figure}

% \newpage

\subsection{WordPerfect default values}

The conversion program generates, independently of the WordPerfect settings,
a \LaTeX\ document with a left margin of 1 inch (2.54cm).  This is because
\LaTeX\ enforces left and top margins of at least 1 inch (see 
figure~\ref{fig:tabs}).  \WPtoLaTeX\ therefore assumes that the margins 
in the WordPerfect document are also set to 1 inch and that they do not 
change.

Tabs are set every inch by default (14 tab stops).  A different default 
tab-setting can be placed at the first line.  If the standard, one-inch 
default settings are not used, however, processing by \LaTeX\ may produce 
error messages.  This has more to do with the manner in which WordPerfect 
positions tab-stops than it does with \LaTeX (see figure~\ref{fig:tabs}). 
\LaTeX\ positions tab stops relative to the left margin, which, as mentioned
above, is a minimum of 1 inch wide.  In WordPerfect the left margin and the
tab settings are independent of each other.

\begin{figure}[hbt]
\centering
\setlength{\unitlength}{1.5mm}
\begin{picture}(60,50)
 \thicklines
 \put(0,0){\framebox(28,35)}
 \put(32,0){\framebox(28,35)}
 \thinlines
 \put(0,37){\makebox(1,3)[l]{WordPerfect}}
 \put(32,37){\makebox(1,3)[l]{\LaTeX}}
 \put(36,31){\line(1,0){21}}
 \put(36,31){\line(0,-1){28}}
 \put(32,31){\vector(1,0){4}}
 \put(36,31){\vector(-1,0){4}}
 \put(36,31){\vector(0,1){4}}
 \put(36,35){\vector(0,-1){4}}
 \put(37,31){\makebox(1,4)[l]{{\small 1"}}}
 \put(32,28){\makebox(4,2){{\small 1"}}}
 \put(36,27){\vector(1,0){3}}
 \put(40,27){\makebox(1,1)[tl]{{\scriptsize tab 1}}}
 \put(36,25){\vector(1,0){6}}
 \put(43,25){\makebox(1,1)[tl]{{\scriptsize tab 2}}}
 \put(36,23){\vector(1,0){9}}
 \put(46,23){\makebox(1,1)[tl]{{\scriptsize tab 3}}}
 \put(4,31){\line(0,-1){28}}
 \put(4,31){\line(1,0){21}}
 \put(0,27){\vector(1,0){7}}
 \put(8,27){\makebox(1,1)[tl]{{\scriptsize tab 1}}}
 \put(0,25){\vector(1,0){10}}
 \put(11,25){\makebox(1,1)[tl]{{\scriptsize tab 2}}}
 \put(0,23){\vector(1,0){13}}
 \put(14,23){\makebox(1,1)[tl]{{\scriptsize tab 3}}}
\end{picture}
\caption{tab settings in WordPerfect and \LaTeX}
\label{fig:tabs}
\end{figure}

\newpage

\subsection{Spaces}

Because WordPerfect works well as tool for the visual design of a document, 
users often have the tendency to use spaces to produce an acceptable layout.
Multiple spaces within \LaTeX, however, have the same effect as a single 
space.  Therefore, in converting a WordPerfect document, multiple spaces are 
changed into `hard' \LaTeX-spaces.

\noindent
For example:

\begin{tabular}{|l|l|}
\hline
WordPerfect                & \LaTeX \rule[-.5cm]{0cm}{1.5cm} \\
\hline
\verb*|word1    word2|   & \verb*|word1 ~~~word2|\rule[-.5cm]{0cm}{1.5cm} \\
\hline
\end{tabular}
\nwln

When these come at the beginning of a line, however, they have no effect.
Moreover, the layout which existed in the WordPerfect environment will seldom 
be properly achieved in \LaTeX, because of the different typographic rules, 
typefaces and text-spacing that the latter handles.

{\bf Note:} This feature produces typografically incorrect things and
thus it is implicitly turned off. If you want to turn it on, then use switch
\verb|-fix-spaces|.


\subsection{Equations}

Because of the philosophy of typing an equations in WP is very similar
to \TeX ~conversion is not so difficult. The Math is written in both cases
in text notation, but in WP is enveloped into the object [Equ Box:nn;;].
This convertor is also able to translate Greek characters, symbols and
matrixes included in equations.

\medskip\noindent
Example (of some simple equation):

\noindent
WP equation string:
\medskip\noindent
"  a= 1/4+\{4\^{}5\} over \{2+x\^{}5\} + 1 over \{2 + 3 over \{4+y\}\}
   5 SQRT \{68+x\^{}e over 5\} \~{} + \~{} NROOT \{r+6\}\{8\} "

\medskip\noindent
\TeX equation string:
" a= 1/4+$\tt\backslash$frac\{\{4\^{}5\}\}\{\{2+x\^{}5\}\} +$\tt\backslash$frac\{1\}\{\{2
  + $\tt\backslash$frac\{3\}\{\{4+y\}\}\}\} - 5 $\tt\backslash$sqrt \{\{68+x\^{}
  $\tt\backslash$frac\{e\}\{5\}\}\} \~{} + \~{} $\tt\backslash$sqrt [ \{r+6\} ] \{ 8\} "


\medskip\noindent
And correctly displayed equation follows:
\begin{displaymath}
a= 1/4+\frac{{4^5}}{{2+x^5}} +\frac{1}{{2 +\frac{3}{{4+y}}}} - 5 \sqrt{{68+x^\frac{e}{5}}}
   ~ +  ~ \sqrt[{r+6}]{8}
\end{displaymath}


\subsubsection{Influence of formula attributes}

The inside part of formulas is nearly same, but interfacing LaTeX enviroment
depends on setting many attributes.

The simplest output enviroment is {\bf displaymath}.
It is used for single formulas with anchor type paragraph or page without any caption.
The {\bf eqnarray*} enviroment is used for multiple formulas in one.

If there is any caption then {\bf displaymath} is changed to {\bf equation}
or {\bf eqnarray}. Only first equation in array is numbered and others
are marked by {\bf nonumber} \LaTeX command.

Enviroment \$ \$ is used mainly for the character type anchoring.
Don't ask me why. Character anchored equations are usually a part of sentence
and displaymath will distort such sentences like this: $\sqrt 4 + {1 \over 2}$.
It is also used in places where previous enviroments cannot be typed
(e.g. in the case of tables).

The most complicated case occurs when formula is enclosed in table, figure
or special box. Then correct box is generated and formula is placed inside.

\medskip
Sometimes you must repair converted equations manually.



\subsection{Tables}

The \WPtoLaTeX\ is also able to convert a tables. It converts
style of centering of columns. It do not recognize
all WP features such as special dotted cells, and double lines somewhere.
Thus an line art from tables will not be converted well.
A size of columns is not converted.

\medskip\noindent
Table looking like this in WP:
\begin{verbatim}
[Tbl Def:I;3,5.31cm,5.31cm,5.31cm]
[Row] [Cell] Left Centered  [Cell] Center [Cell] Right Centered
[Row] [Cell] 111 [Cell] 222 [Cell] 333 Centered
[Tbl Off]
\end{verbatim}

\medskip\noindent
Is converted to:
\begin{tabular}
{|l|c|r|} \hline
Left centered & Center & Right centered \\ \hline
111 & 222 & 333 \\ \hline
\end{tabular}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\newpage
\section{Used Styles}

\WPtoLaTeX\ has its own style named \verb|WP2LATEX.STY|. Features in thic style
could be divided into two categories:

\begin{enumerate}
\item Features that I cannot find in any package.
\item Automatically disabled/enabled features that could be found in
      some packages. Such packages must precede \verb|WP2LATEX.STY|.
\end{enumerate}

Please keep in mind, that you do not need to use all listed packages.
You can disable some of them or all of them and \WPtoLaTeX\ should still
be abble to produce \LaTeX\ output. \verb|WP2LATEX.STY| is the only mandatory
style.

\bigskip\noindent
The full list of used packages:

\begin{description}
\item[amssymb]    Style with special math characters.
\item[makeidx]    Style for creating index file.
\item[wp2latex]   The \WPtoLaTeX\ basic style. This style is mandatory and is
                  used in every documents.
\item[twoside]	  The style for distinguishing odd and even pages mainly
		  for headers and footers.
\item[twocolumn]  Style that supports typesetting in two columns.
\item[multicol]   Style that supports typesetting in two or more columns.
\item[endnotes]   Style that supports endnotes.
\item[cyrillic]   Style with special mainly Russian characters.
\item[InputPS]    Style that supports postscript tricks inside \LaTeX\ files.
\item[wasyfont]   Style with special characters.
\item[textcomp]   Style with special characters.
\item[bbm]        Style with special characters.
\item[mathrsfs]   Style with special characters.
\item[fancyhdr]   Style that supports headers and footers for pages.
\item[longtable]  Another style for tables.
\item[czech]      Native support for Czech language. Used only if the czech
                  language is autodetected.
\item[german]     Native support for German language. Used only if the czech
                  language is autodetected.
\end{description}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\newpage
\section{Advanced features}

\subsection{Understanding log file}

The log file is aimed to better understanding of the contents of binary
objects in the original WordPerfect file. It is similar to reveal codes
in the WordPerfect editor. From this file you could find all objects
that are not converted yet.

Creation of the log file is normally disabled. You could enable it by
option \verb|-l logfilename|. After conversion you can use any text viever
for analysing this file.

\medskip\noindent
An example of the log file:
\begin{verbatim}
% log file for converted file c:\temp\font8.wp, WP ver 6.0
% conversion program WP2LaTex v. 2.76 from 27 Dec 1999.

Object type: DDh subtype:  Ah length:  16 [!Global on] 
Object type: D1h subtype:  Fh length:  16    
Object type: D1h subtype: 13h length:  12    
Object type: D1h subtype: 11h length: 340    
Object type: D3h subtype:  5h length:  12 [Justification Full] 
Object type: DDh subtype:  Bh length:  11 [!Global off] 
Object type: D4h subtype: 5Fh length:  16    TNR1>>>
Object type: D4h subtype: 1Bh length:  31 [!Font 1.00] 
Object type: D4h subtype: 1Ah length:  31 [!Font Times] <<<Kecy kecy
Object type: CFh subtype:  0h length:   1 [SRt] kecy 
% pass1 finished going to pass2

% pass2 finished
%  There were 0 unconverted characters.
%  There were 25 unrecognized/ignored objects.
\end{verbatim}

On the top of the log file is placed small header. The list of objects
continues. Features \verb|Object type: D4h subtype: 1Ah length:  31| are
WP internals and you do not need to care with them. If the interpretation
of object is known, the bracketed symbol \verb|[Justification Full]| appear.
If the interpretation of object is known, but object cannot be converted,
the exclamation mark '!' appear before object name \verb|[!Font Times]|.
The object name is normal reveal code of recognized symbol.
Normal text is placed after objects.


\newpage
\section{Warning and Error messages}

This section discusses all warning runtime output messages.

\noindent
Fatal Errors:
\begin{itemize}\setlength{\itemsep}{-1mm}
  \item \Underline{Fatal: Code was badly compiled. Check types.h !!!!!}
	This error is quite serious and \WPtoLaTeX\ will not run properly.
	It might occur when \WPtoLaTeX\ is ported to new platform. Do
        suggested operation and recompile your code until this problem occurs.
  \item \Underline{Fatal: Program Error. Write full bug report.}
        This error is something like General Protection Fault. Such error
        message should not appear. Please edit your makefile, recompile
        \WPtoLaTeX\ with defined symbol DEBUG (proper switch for gcc is
        -DDEBUG) and run \WPtoLaTeX\ again. Then try to trace out a buggy
        part of code from the file \verb|default.log|.
\end{itemize}


\noindent
Errors:
\begin{itemize}\setlength{\itemsep}{-1mm}
  \item \Underline{Error: Bad command in table file:\%c!}
	This is a bug. Please report.
  \item \Underline{Error: File \%s not found.}
	The given WordPerfect file does not exist.
  \item \Underline{Error: File was badly compiled. Check types.h !}
	You probably port this program to another compiler. Some variables
	must have a unique size and thus you should fix it in the file
	types.h.
  \item \Underline{Error: Log file is not completely written.}
	An error occured while writing a .LOG file. This may be a device
	error e.g. device is full.
  \item \Underline{Error: Not a WordPerfect 5.x document.}
	The given WordPerfect file was not created in the WordPerfect 5.x
	or WordPerfect 6.0.
  \item \Underline{Error: Object consistency failed. Trying to ignore.}
	There are two possible problems. Eighter your WordPerfect file is
	corrupted or some object is not recognized correctly. If you are sure
	that your file is healthy report this may be a bug.
  \item \Underline{Error: Path not found.}
	An invalid path was given in the name of one of the files.
  \item \Underline{Error: Program Error.}
	This is a bug. Please report.
\end{itemize}

\noindent
Warnings:
\begin{itemize}\setlength{\itemsep}{-1mm}
  \item \Underline{Warning: Cannot open log file \%s ..."}
	The log file cannot be opened. The program will continue normally
	without logging anything.
  \item \Underline{Warning: File seems to be encrypted. Conversion may not be possible!!}
        Trere has been added password to the WP file. Decrypting code is
        implemented only for WP4.x and WP5.x and it may fail.
  \item \Underline{Warning: Incorrect line with TABs on end - fixed.}
	This is a problem of your document. Found [Tab] is useless and is
	ruled out.
  \item \Underline{Warning: Package "amssymb" should not be used in LaTex 2.09!}
	The package "amssymb" is available only for \LaTeX 2.0e and you want to convert
        into \LaTeX 2.09. Conversion will continue normally, but you may
	expect problems during translating converted \LaTeX\ code.
  \item \Underline{Warning: Unknown argument "\%s"!"}
	You passed something wrong on your command line. Read this manual more carefully.
  \item \Underline{Warning: Unknown output codepage %s!}
	You want to use unsupported encoding.
  \item \Underline{Warning: WP v 4.0 is forced. No autodetection is possible. ERRORS may occur!!!}
        Because there is no way how to check WP4.x format, you see this message.
        Everything may be OK if you really have file from WP4.x.
\end{itemize}


\newpage

\section{The package}

The \WPtoLaTeX\ package contains the following files :

\begin{description}\setlength{\itemsep}{-1mm}
  \item \verb|MAKEFILE|	    (The root makefile for wp2latex package.)	
  \item \verb|README.1ST|   (The file with basic instructions- abbreviated description of this program.)
  \item \verb|README.TXT|   (The main readme file for advertising this program.)
  \item \verb|WP2LATEX.FAQ| (File with ansvers to frekvently asked questions.)
  \item \verb|WP2LATEX.TEX| (This user's guide.)

  \item
  
  \item \verb|STYLES.TEX\BoxedEPSF.TEX| (Additional style for including PS images.
)
  \item \verb|STYLES.TEX\ENDNOTES.STY| (Additional style for processing endnotes in \LaTeX\.)
  \item \verb|STYLES.TEX\CYRACC.DEF|   (Additional package for including cyrillic characters
                                        into \LaTeX\ document.)
  \item \verb|STYLES.TEX\CYRILLIC.STY| (Additional style for including cyrillic characters
                                        into \LaTeX\ document - uses CYRACC.DEF.)
  \item \verb|STYLES.TEX\InputPS.STY|  (Additional style for including PS images.
)
  \item \verb|STYLES.TEX\WP2LATEX.STY| (Style file needed by \LaTeX\ for processing.)
  \item \verb|STYLES.TEX\WASYFONT.STY| (Additional style for including characters from wasy2 font into \LaTeX\.)

  \item

  \item \verb|SOURCES.CC\|	(The directory with C++ sources.)
  \item \verb|SOURCES.CC\FORMULAS.CC| (Procedures for converting formulas.)
  \item \verb|SOURCES.CC\CHARACTR.CC| (Procedures for converting extended WP characters.)
  \item \verb|SOURCES.CC\IGETTEXT.CC| (Procedures for initialize gettext translation features.)
  \item \verb|SOURCES.CC\MAKEFILE| (Makefile for C++ version under both DJGPP and Linux.)
  \item \verb|SOURCES.CC\PASS1.CC| (common procedures needed for all WP convertors during 1st pass.)
  \item \verb|SOURCES.CC\PASS1_4.CC| (procedures for PASS1 for WP version 4.x)
  \item \verb|SOURCES.CC\PASS1_5.CC| (procedures needed for PASS1 for WP version 5.x.)
  \item \verb|SOURCES.CC\PASS1_6.CC| (procedures for PASS1 for WP version 6.x (and also 7.x) )
  \item \verb|SOURCES.CC\PASS2.CC| (procedures for PASS2)
  \item \verb|SOURCES.CC\WP2LATEX.CC| (main part of \WPtoLaTeX)
  \item \verb|SOURCES.CC\WP2LATEX.H| (main include file for all components of \WPtoLaTeX.)
  \item \verb|SOURCES.CC\ATOMS\INCLUDE\COMMON.H|  (Include file with some compiler specific commands.)
  \item \verb|SOURCES.CC\ATOMS\LISTS.CC|          (Collection of procedures for operations with lists of text.)
  \item \verb|SOURCES.CC\ATOMS\INCLUDE\LISTS.H|   (The include file for tool LISTS.CC.)
  \item \verb|SOURCES.CC\ATOMS\SETS.CC|           (Collection of procedures for operations with sets.)
  \item \verb|SOURCES.CC\ATOMS\INCLUDE\SETS.H|    (The include file for tool SETS.CC.)
  \item \verb|SOURCES.CC\ATOMS\STRINGS.CC|        (Collection of procedures for operations with strings.)
  \item \verb|SOURCES.CC\ATOMS\INCLUDE\STRINGS.H| (The include file for tool STRINGS.CC.)
  \item \verb|SOURCES.CC\ATOMS\STRUCT.CC|         (Procedures for endian conversion of multi-byte numbers.)
  \item \verb|SOURCES.CC\ATOMS\INCLUDE\TYPES.H|   (This include file provides fixed size numbers like BYTE, WORD, DWORD.)

  \item

  \item \verb|SOURCES.PAS\|	(The directory with the original Turbo Pascal 7.0 sources)
  \item \verb|SOURCES.PAS\COMMON.PAS| (Commonly used procedures)
  \item \verb|SOURCES.PAS\FORMULAS.PAS| (Unit for converting of formulas)
  \item \verb|SOURCES.PAS\PASS1.PAS| (procedures for PASS1)
  \item \verb|SOURCES.PAS\PASS1_6.PAS| (experimental procedures for PASS1 for WP version 6.0)
  \item \verb|SOURCES.PAS\PASS2.PAS| (procedures for PASS2)
  \item \verb|SOURCES.PAS\WP2LATEX.PAS| (main part of \WPtoLaTeX)

  \item

  \item \verb|DOS\WP2LATEX.EXE| (the conversion program DOS executable)
  \item \verb|OS2\WP2LATEX.EXE| (the conversion program OS/2 executable)
  \item \verb|LINUX\WP2LATEX| (the conversion program Linux ELF executable)
  \item \verb|WIN\WP2LATEX.EXE| (the conversion program MS Windows executable)


  \item \verb|DOC\|	(The directory with documentation texts.)
  \item \verb|DOC\BUG.TXT| (The description of known bugs. Please consult this file first before you
			    will report anything.)
  \item \verb|DOC\WP2LTX.TEX|   ( Dutch (original) version of the user's guide - now obsolete)
  \item \verb|DOC\WP2LATEX.1|   (Man page for WP2LATEX program.)

  \item \verb|TEST\|	(The directory with testing WordPerfect files.)
  \item \verb|TEST\TEST.WP| (WP test file with mix of features)
  \item \verb|TEST\CHARACTR.WP| (WP test file with all WP charsets)
\end{description}

Four executable files are supported. One for real mode MSDOS, second
for MSWindows, third for Linux and fourth for protected DOS DJGPP.
All versions work in text mode. Using of DPMI (protected mode) version is not
advised, because the memory requirements of this program are too small
to do this.

\subsection{Re-compilation of the code}

Because the \WPtoLaTeX\ is distributed with source code you can solve to recompile
all code. Recompilation is easy for supported systems: DJGPP and Linux.
(May be Solaris, but I tested it only several times.)

\bigskip\noindent
Enter a command \verb|make| in the source directory \verb|sources.cc|

\noindent
\verb|prompt:>make| Enter

After this command all source code should be completelly rebuild.
The program is without syntaktical bugs because I will never release
new code without testing it.

\subsubsection{Support for gettext library}

This feature allows to internationalize programs by translating their
messages into your native language. The code of \WPtoLaTeX\ was modified
to support this library. If you do not have it, comment the line
\verb|GETTEXT=-D__gettext__| in the \verb|makefile|. Othervise you will
not abble to succesfully compile.

\begin{verbatim}
# Uncomment next line for allowing a gettext multilanguage translation features
# This feature is not required for succesfull run of WP2LaTeX.
GETTEXT=-D__gettext__
\end{verbatim}

\subsubsection{Debugging version of \WPtoLaTeX}

If you have problems with run of the \WPtoLaTeX\ you can solve to
create debugging version. The comment in makefile should be
clear for explanation.

\begin{verbatim}
# Uncomment next line for compile a debugging version of WP2LaTeX
# DEBUG=-DDEBUG -g
\end{verbatim}

The debugging version logs all function calls so that big .LOG file can
be created. Use this feature only if you really want to debug because
it slows down all code.


\section{Conclusion}

The 100\%-correct conversion of a WordPerfect-document is not guaranteed.
Error messages can always appear during processing by \LaTeX.  Some
adjustments to the generated \LaTeX\ file will in many cases be necessary.

The following were given the highest priority :
\begin{itemize}
  \item preventing the loss of text
  \item avoiding program crashes
\end{itemize}
\nwln

Because the sources are included (Turbo Pascal 5.0 format) it should not be
too difficult modifying the program to convert Wordperfect 5.1 documents,
provided the WordPerfect file formats are known.

The file formats we used for our program were found in the WordPerfect
5.0 Developer's Toolkit. Most likely such a toolkit is available for version 
5.1 of WordPerfect.

If you have remarks or comments regarding the program, you can send them
to:

\vspace{1cm}

Jaroslav Fojt\'{\i}k\\
Email:fojtik@htc.honeywell.cz  (my new Email)\\
      fojtik@penguin.cz\\
   or:fojtik@cmp.felk.cvut.cz (this may be invalid after 2000)

\medskip

Post Address:
Jaroslav Fojtik
Dvouramenna 13
Praha 4 - Podoli
140 00
Czech Republic

\medskip

Before doing this please visit my www page and test recent version:\\
http://www.penguin.cz/\~{}fojtik/wp2latex/



I have found that these address are not currently valid:\\
\begin{minipage}[t]{6cm}
R.C. Houtepen \\
Brusselstraat 150 \\
4826 NK Breda \\
The Netherlands \\
Tel: 076-714777
\end{minipage}
\hfill or \hfill
\begin{minipage}[t]{6cm}
\raggedleft
R.L.M. Helwig \\
Eindhoven University of Technology \\
P.O. BOX 513\\
5600 MB Eindhoven\\
The Netherlands \\
Tel: 040 - 472724\\
\nwln
uucp : rcronh@urc.tue.nl\\
bitnet : rcronh@heitue5
\end{minipage}

\newpage
\nwln
\begin{center}
(This page is intentionally left blank for notes.)
\end{center}
\nwln
\end{document}
