blob: 34c0fe7f82bf795a5cae27fa6b5e4975dc54a004 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
.\" Automatically generated by Pandoc 3.0.1
.\"
.\" Define V font for inline verbatim, using C font in formats
.\" that render this, and otherwise B font.
.ie "\f[CB]x\f[]"x" \{\
. ftr V B
. ftr VI BI
. ftr VB B
. ftr VBI BI
.\}
.el \{\
. ftr V CR
. ftr VI CI
. ftr VB CB
. ftr VBI CBI
.\}
.TH "edtx2dtx" "1" "October 10, 2023" "edtx2dtx 0.1.0" "User Manual"
.nh
.SH NAME
.PP
edtx2dtx - Convert .edtx into .dtx
.SH SYNOPSIS
.PP
\f[B]edtx2dtx\f[R] \f[I]filename.edtx\f[R] > \f[I]filename.dtx\f[R]
.SH DESCRIPTION
This utility wraps code chunks by a (commented and properly indented)
.PP
pair.
A code chunk is any sequence of lines not introduced by a single
(possibly indented) comment character (%); i.e.\ both non-commented
lines and lines introduced by multiple comment characters count as code,
and documentation lines may be indented.
The part(s) of the file which should undergo conversion should be marked
by a
.PP
pair (unlike in a .dtx, these lines need not immediately precede and
follow the code, respectively).
This convention allows for the driver to remain as is, and also makes it
easy to paste a .dtx file into an .edtx, as using this utility on a .dtx
does not change the file.
.PP
The utility furthermore replaces the first occurrence of
\[lq].edtx\[rq], followed by an optional parenthesized note, with
\[lq].dtx\[rq], plus the note on how the file was generated.
.SH OPTIONS
.TP
\f[B]-h, --help\f[R]
Show help and exit.
.TP
\f[B]-V, --version\f[R]
Show the version number and exit.
.SH SEE ALSO
.PP
easydoctex.el
|
