| 1 |
.TH JADETEX 1 "12 July 1998" "Marcus Brinkmann" |
| 2 |
.\"===================================================================== |
| 3 |
.if t .ds TX \fRT\\h'-0.1667m'\\v'0.20v'E\\v'-0.20v'\\h'-0.125m'X\fP |
| 4 |
.if n .ds TX TeX |
| 5 |
.ie t .ds OX \fIT\v'+0.25m'E\v'-0.25m'X\fP\" for troff |
| 6 |
.el .ds OX TeX\" for nroff |
| 7 |
.\" the same but obliqued |
| 8 |
.\" BX definition must follow TX so BX can use TX |
| 9 |
.if t .ds BX \fRB\s-2IB\s0\fP\*(TX |
| 10 |
.if n .ds BX BibTeX |
| 11 |
.\" LX definition must follow TX so LX can use TX |
| 12 |
.if t .ds LX \fRL\\h'-0.36m'\\v'-0.15v'\s-2A\s0\\h'-0.15m'\\v'0.15v'\fP\*(TX |
| 13 |
.if n .ds LX LaTeX |
| 14 |
.\"===================================================================== |
| 15 |
.SH NAME |
| 16 |
jadetex \- processing tex files produced by the \*(TX backend of Jade. |
| 17 |
.SH SYNOPSIS |
| 18 |
.B jadetex |
| 19 |
[ first line ] |
| 20 |
.\"===================================================================== |
| 21 |
.SH DESCRIPTION |
| 22 |
This manual page was derived from the manual page for \*(LX and is not meant |
| 23 |
to be exhaustive. The complete |
| 24 |
documentation for this version of \*(TX can be found in the info file |
| 25 |
or manual |
| 26 |
.IR "Web2C: A TeX implementation" . |
| 27 |
.PP |
| 28 |
Jade\*(TX is a \*(TX macro package, not a modification to the \*(TX source |
| 29 |
program, so all the capabilities described in |
| 30 |
.BR tex (1) |
| 31 |
are present. |
| 32 |
.B pdfjadetex |
| 33 |
is the PDF\*(TX version of the jade\*(TX format. |
| 34 |
.\"===================================================================== |
| 35 |
.SH "SEE ALSO" |
| 36 |
.BR pdfjadetex (1), |
| 37 |
.BR latex (1), |
| 38 |
.BR tex (1), |
| 39 |
.br |
| 40 |
.SH AUTHORS |
| 41 |
The author of jade\*(TX is Sebastian Rahtz. |
| 42 |
.PP |
| 43 |
This manual page was derived from the \*(LX manual page. It is provided for |
| 44 |
the Debian distribution by Marcus Brinkmann. Please send improvements, |
| 45 |
suggestion and other comments to [email protected]. |