continues

CONFORMS TO

General UNIX conventions.

BUGS

This list is not exhaustive.

SEE ALSO

file(1), make(1)

Linux, 4 April 1996

tr2tex

tr2tex—Convert a document from troff to LaTeX

SYNOPSIS

tr2tex [ -m ] filename

DESCRIPTION

tr2tex converts a document typeset in troff to a LaTeX format. It is intended to do the first pass of the conversion. The user should then finish up the rest of the conversion and customize the converted manuscript to his or her liking. It can also serve as a tutor for those who want to convert from troff to LaTeX.

Most of the converted document will be in LaTeX, but some of it may be in plain TeX. It will also use some macros in troffms.sty or troffman.sty, which are included in the package and must be available to the document when processed with LaTeX.

If there is more than one input file, they will all be converted into one LaTeX document.

tr2tex understands most of the -ms and -man macros and eqn preprocessor symbols. It also understands several plain troff commands. Few tbl preprocessor commands are understood to help convert very simple tables.

When converting manuals, use the -m flag.

If a troff command cannot be converted, the line that contain that command will be commented out.

Note that if you have eqn symbols, you must have the inline mathematics delimiter defined by delim in the file you are converting. If it is defined in another setup file, that setup file must be concatenated with the file to be converted; otherwise, tr2tex regards the inline math as ordinary text.

BUGS

Many of these bugs are harmless. Most of them cause local errors that can be fixed in the converted manuscript.

• Some macros and macro arguments are not recognized.
• Commands that are not separated from their argument by a space are not properly parsed (such as .sp3i).
• When some operators (notably over, sub, and sup) are renamed (via define) and then they are encountered in the text, tr2tex treats them as ordinary macros and does not apply their rules.
• rpile, lpile, and cpile are treated the same as cpile.
• rcol and lcol are treated the same as ccol.
• Math-mode size, gsize, fat, and gfont are ignored.
• lineup and mark are ignored. The rules are so different.
• Some troff commands are translated to commands that require delimiters that have to be explicitly put. Because they are sometimes not put in troff, they can create problems. Example: .nf is not closed by .fi.
• When local motions are converted to nraise or nlower, an nhbox is needed, which must be put manually after the conversion.
• a sub i sub j is converted to a_i_j, which TeX parses as a_i{}_j} with a complaint that it is vague. a sub {i subj} is parsed correctly and converted to a_{i_j}.
• Line spacing is not changed within a paragraph in TeX (which is a bad practice anyway). TeX uses the last line spacing in effect in that paragraph.

TO DO

Access registers via the .nr command.

SEE ALSO

texmatch(9), trmatch(9)

AUTHOR

Kamal Al-Yahya, Stanford University

1 January 1987

Unicode

Unicode—The unified 16-bit super character set.

DESCRIPTION

The international standard ISO 10646 defines the Universal Character Set (UCS). UCS contains all the characters of all other character-set standards. It also guarantees round-trip compatibility; conversion tables can be built such that no information is lost when a string is converted from any other encoding to UCS and back.

UCS contains the characters required to represent almost all known languages. This includes apart from the many languages that use extensions of the Latin script also the following scripts and languages: Greek, Cyrillic, Hebrew, Arabic, Armenian, Gregorian, Japanese, Chinese, Hiragana, Katakana, Korean, Hangul, Devangari, Bengali, Gurmukhi, Gujarati, Oriya, Tamil, Telugu, Kannada, Malayam, Thai, Lao, Bopomofo, and a number of others. Work is going on to include further scripts such as Tibetan, Khmer, Runic, Ethiopian, Hieroglyphics, various Indo-European languages, and many others. For most of these latter scripts, it was not yet clear how they can be encoded best when the standard was published in 1993. In addition to the characters required by these scripts, also a large number of graphical, typographical, mathematical, and scientific symbols such as those provided by TeX, PostScript, MS-DOS, Macintosh, Videotext, OCR, and many word processing systems have been included, as well as special codes that guarantee round-trip compatibility to all other existing character-set standards.