home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Mega Top 1
/
os2_top1.zip
/
os2_top1
/
APPS
/
TEKST
/
MAKETCP
/
EMTEX
/
DOC
/
ENGLISH
/
MAKETCP.DOC
Wrap
Text File
|
1992-11-27
|
6KB
|
143 lines
==============================================================================
MAKETCP.DOC for maketcp 1.1c VERSION: 27-Nov-1992
==============================================================================
******************************************************************************
******************************************************************************
** **
** maketcp 1.1c IS A BETA TEST RELEASE for emTeX 3.14 [3c-beta5] **
** **
******************************************************************************
******************************************************************************
maketcp generates (or decodes) TCP files (TeX code page). These files are
used by emTeX (and TeXconv) for code page conversion as well as to convert
special input characters into TeX commands. By using TCP files, emTeX can
be adapted to different code pages. Note that your texts may not be usable
with other TeX implementations if you're using TCP files. texconv can be
used for converting your input files for use with other TeX implementations.
Usage:
maketcp <mode> [<options>] [<input_file> [<output_file>]]
Mode:
-c Convert a text file into a TCP file (generate a TCP file;
compile)
-d Convert a TCP file into a text file (decompile).
Options:
-8 Set up a conversion table which leaves the characters with codes 128
to 255 unchanged (without -8, the codes from 128 to 255 are mapped to
code 127)
-r Set up a conversion table which leaves the characters with codes 0
to 31 unchanged (without -r, codes 0 to 31 are mapped to code 127)
The default extension for TCP files is .tcp (with the option -c this applies
to the output file, with -d the input file).
A TCP file contains three tables: the first shows which special characters are
to be converted into TeX control sequences; the second converts the characters
in the input file into the internal TeX characters and the third performs the
reverse of this.
When no TCP file is used with emTeX, only the characters with codes 0, 9, 12
and 32 to 126 are permitted. When the /r option is given, characters in the
range 0 through 31 are also allowed. With the /8 option (only with INITEX)
characters in the range 128 through 255 are permitted as well. No conversion
takes place.
This behaviour can be altered by using a TCP file. Characters in the range
128 through 255 can be converted into TeX control sequences; in addition, the
conversion of all characters for input and output can be changed - this is
necessary when TeX's character coding does not correspond to the code page in
use. This should only be done for the characters above 128 as otherwise
unexpected effects will be caused. Conversion for output will only affect
the LOG file, not the DVI file.
To create a TCP file you must make a text file in which both the translation
of special characters into TeX control sequences and the character conversion
for input and output is given. You can get an example of the format of the
file by converting the TCP file supplied (850_tex.tcp) into the equivalent
text file with the command
maketcp -d 850_tex.tcp example.txt
The text file can contain comments which are lines with a `%' in column 1:
you can also make your file more readable by inserting blank lines, which
are ignored. All other lines are either special character conversions or
input to internal character conversions - the output character conversion
table is constructed from the input table. Characters to be converted can be
entered either as is (a single character) or in hexadecimal, in the TeX 3.0
format (^^ff). The translation of a special character is entered as follows:
^^84 -> \"a % Umlaut-a
The line begins with the special character (Umlaut-a), followed by a space,
an arrow (hyphen and greater than character), space and then the TeX control
sequence which is to replace the character. The `%' and the text following
it up to the end of the line will be ignored unless it is part of the TeX
command - in the following, ONE space will not be ignored:
^^fe -> \%\ % Tex control sequence: "\%\ "
The conversion of an input character into an internal code (and an internal
code into an output character) is entered as follows:
^^84 ^^e4 % Umlaut-a (PC) -> Umlaut-a (ISO 8859/1)
The line begins with the input character followed by a space and the desired
internal representation (as coded in the TFM file). When the character ^^e4
is to be output, it will be converted into ^^84 (in this example). If more
than one character is mapped into the same internal character then the last
conversion will be used for output:
a b
b b
In this pointless (but simple) example, both a and b are mapped on to the
same internal character: by the rule above, b will be converted into b on
output. This feature is important if you want to map extended characters to
ASCII characters. You should use
^^af z
z z
to translate ^^af to z and to make z display z. If you're using only
^^af z
then ^^: will be displayed for z. (Moreover, a z in a file name would be
converted into ^^: causing grief when opening the file!)
The default conversion tables are changed by such a text file: these
conversion tables are set up by the -8 and -r options (see above) - in some
circumstances, you may save yourself some work by using the -8 and/or -r
options. When you convert a TCP file into a text file, the output shows only
the differences from the default tables set up by the -8 and -r options: the
text file output will therefore depend on the settings of these options.
History
=======
Version 1.1c (27-Nov-1992)
--------------------------
- Bug fixed. That bug caused emTeX displaying a character entered in
^^ff format to be displayed as character without conversion if there
is no conversion from an external character to that character. Now,
those characters are displayed in ^^ff format.
- Support of HPFS filenames under OS/2
-------- End of MAKETCP.DOC -------------