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 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300
|
README for sdc
sdc is a well featured, free system aiming to make SGML suitable for
day to day use. It's in a ``production state'' now and proved for large
documentation.
With sdc it is really simple to write technical documentation, reports,
books, letters, man pages, or prepare talks and classes (with slides
and hand outs). You can include some graphic (made with other tools,
e.g., xfig, tgif or anything creating EPS-Files) or other special data
representation (e.g., tlb/roff tables) and so on with ease.
Whatever you do, while writing you never have to worry what the final
result will look like. When done, you convert your writing into the desired
target format by sdc and promised: it will look at least reasonable.
The goal of sdc is to be author friendly, easy to use without the need of
special editors and to hide as much of the backend as possible. For the
sake of the latter extremly funny features of the one or other backend are
not supported. Or at least not in a portable way.
The version 0.7 (sdc-1.0) is a mayor rewrite. Internals have changed to
allow for more flexibility and arbitrary changes to the document structure.
While it should not do, that might affect some (a few) documents.
It turned out long ago, that some shells have an internal command with the
same name as the original -- typeset. Therefor I'm looking for a new name.
If you have an idea: PLEASE mail me.
1. The package
consists of:
o a executable (parser/formater)
o a library of document type definitions (DTD'S)
o a set of files describing the formatting for the various output formats
(currently LaTeX, PostSript, HTML, Info, roff -man, ASCII, limited RTF
and slides). RTF is still supported the old way.
o some scrips to do automatic conversion of graphic and other notations
2. Features
o The whole system is written in the aim to be author friendly. The DTD's
are very easy to use. (LaTeX, QUERTZ, TeXInfo or HTML are much more
complicated.)
For SGML experts: We use mixed content model almost everywhere. While
you can type text at any place it's meaning is ambigous sometimes.
Therefor we parse internaly a second time and format as if we had a
- 2 -
element content most of the time.
o Backend formaters are completely hidden. Don't worry about any
'special' characters but the two introduced trough SGML (< and &).
o Multi Language support (current english and german) including automatic
hyphenation (for PostScript). Custumization to support danish, dutch,
finnish, french, norwegian, spanish and swedish should be a matter of
minutes. (Not done because I can't test it.)
o Support for system notations. (xfig, tgif, roff/tbl, LaTeX, lout)
Suitable for converting entities like pictures and complicated formulas
into a format accepted by the target format.
o DTD's for simple documents, reports, books, manpages and DIN-letters.
(The latter is in german and easy enough to be used by secretaries
knowing nothing about computers and SGML). Adding new DTD's is quite
simple and strait forward. Book support partially done.
o Required markup is minimized.
o Support of bibliography databases. (Database is SGML too.)
o Automated creation of sorted indices.
o Automagical insertion of standard text parts (like bibliography [from
referenced items of the currently used databases], content and cross
reference text).
o Support for literate programing.
o Adding new output formats is fairly easy. (roff -ms and RTF will be the
next targets)
o Frontend SGML-parser is sgmls/nsgmls, thus you can use everything these
understand.
o Easy to extend through Scheme.
3. Requirements
To install it you need:
1 my favorite scheme compiler bigloo (essential). You may obtain the
latest version from
ftp://ftp.inria.fr/INRIA/Projects/icsla/Implementations
There is a plan to support guille, but this will take a bit of time I
don't have by now.
2 sgmls version 1.1.91 or above or nsgmls (essential) which is used
as the SGML-parser (we use features not in V 1.1). If you have C++
available you can use nsgmls instead. It comes with sp from
- 3 -
http://www.jclark.com/sp.html
There is also sgmls version 1.1.91 available which doesn't need this
******* C++. Otherwise I can sent sgmls 1.1.91 out by mail. Just drop
me a note.
3 LaTeX (semi optional) serving one backend which looks nicer than the
Lout (especially for math formulas) but is harder to deal with. Note
that to include eps pictures sdc relies on epsfig.sty respectivly the
graphics package.
4 Lout version 3.05 (or above, semi optional) which is the (hidden)
PostScript and ASCII formatter (much easier to program than LaTeX). You
may obtain the latest Version from
ftp://ftp.cs.su.oz.au/jeff (original ftp site) or
ftp://ftp.inria.fr:/textproc
5 if you want automatic figure handling as it comes, you'll need tools
like tgif, xfig, ghostscript and pnm tools.
6 I can recomment the psgml packages to edit your documents.
get it from
http://ftp.lysator.liu.se/pub/sgml/``''
But with the little amount of markup it's not nessesary. I use a
supplied mode with some highlighting, which is quite a hack, but the
hilit is useful.
4. Distribution
http:/www.inf.tu-dresden.de/ jw6
For usage see the intro.ps. Unfortunatly it's not too detailed, but
comparing source and output might serve it's purpose for everyone. Cause
it's probably one of the most complicated documents you can write (it
- 4 -
descibes usage of SGML with SGML) I hopefully caught most of the bugs.
5. COPYING
sdc is Copyright (C) 1995,1996 Joerg Wittenberger
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the Free
Software Foundation; version 2 dated June, 1991.
This program is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc., 675
Mass Ave., Cambridge, MA 02139, USA.
<joerg.wittenberger@inf.tu-dresden.de>
6. Changes
See the Changes.sgml or the approbriate section in the introduction.
7. Things to do
1 Add a note in the doc's about the `id'-attribute of sect's etc.
especially their use in the info target.
2 Use new epstogif as supplied from Sebastian Schnberg.
3 -R option to use diffenrent \figure env for LaTeX
4 Implement equations as in HTML-3 (This is in fact LaTeX :-)
5 a automatic glossary.
6 Implement <label> for info
7 Improve output for slides (no empty slides).
8 refine the A FAQ-DTD (due to user response)
- 5 -
9 Refine the Brief (letter) formatting.
10 LaTeX code for verb-elements is still subotpimal. It ought to break
full lines. Anybody knows how to achieve this?
11 Merged indexes
12 Write the developers documentation
13 rewrite RTF output
14 move temp files to use $TMPDIR or /tmp with permission 0600
|