1 $Cambridge: exim/doc/doc-docbook/HowItWorks.txt,v 1.9 2008/02/04 17:28:44 fanf2 Exp $
3 CREATING THE EXIM DOCUMENTATION
5 "You are lost in a maze of twisty little scripts."
8 This document describes how the various versions of the Exim documentation, in
9 different output formats, are created from DocBook XML, and also how the
10 DocBook XML is itself created.
13 BACKGROUND: THE OLD WAY
15 From the start of Exim, in 1995, the specification was written in a local text
16 formatting system known as SGCAL. This is capable of producing PostScript and
17 plain text output from the same source file. Later, when the "ps2pdf" command
18 became available with GhostScript, that was used to create a PDF version from
19 the PostScript. (A few earlier versions were created by a helpful user who had
20 bought the Adobe distiller software.)
22 A demand for a version in "info" format led me to write a Perl script that
23 converted the SGCAL input into a Texinfo file. Because of the somewhat
24 restrictive requirements of Texinfo, this script always needed a lot of
25 maintenance, and was never totally satisfactory.
27 The HTML version of the documentation was originally produced from the Texinfo
28 version, but later I wrote another Perl script that produced it directly from
29 the SGCAL input, which made it possible to produce better HTML.
31 There were a small number of diagrams in the documentation. For the PostScript
32 and PDF versions, these were created using Aspic, a local text-driven drawing
33 program that interfaces directly to SGCAL. For the text and texinfo versions,
34 alternative ascii-art diagrams were used. For the HTML version, screen shots of
35 the PostScript output were turned into gifs.
38 A MORE STANDARD APPROACH
40 Although in principle SGCAL and Aspic could be generally released, they would
41 be unlikely to receive much (if any) maintenance, especially after I retire.
42 Furthermore, the old production method was only semi-automatic; I still did a
43 certain amount of hand tweaking of spec.txt, for example. As the maintenance of
44 Exim itself was being opened up to a larger group of people, it seemed sensible
45 to move to a more standard way of producing the documentation, preferable fully
46 automated. However, we wanted to use only non-commercial software to do this.
48 At the time I was thinking about converting (early 2005), the "obvious"
49 standard format in which to keep the documentation was DocBook XML. The use of
50 XML in general, in many different applications, was increasing rapidly, and it
51 seemed likely to remain a standard for some time to come. DocBook offered a
52 particular form of XML suited to documents that were effectively "books".
54 Maintaining an XML document by hand editing is a tedious, verbose, and
55 error-prone process. A number of specialized XML text editors were available,
56 but all the free ones were at a very primitive stage. I therefore decided to
57 keep the master source in AsciiDoc format, from which a secondary XML master
58 could be automatically generated.
60 The first "new" versions of the documents, for the 4.60 release, were generated
61 this way. However, there were a number of problems with using AsciiDoc for a
62 document as large and as complex as the Exim manual. As a result, I wrote a new
63 application called xfpt ("XML From Plain Text") which creates XML from a
64 relatively simple and consistent markup language. This application has been
65 released for general use, and the master sources for the Exim documentation are
68 All the output formats are generated from the XML file. If, in the future, a
69 better way of maintaining the XML source becomes available, this can be adopted
70 without changing any of the processing that produces the output documents.
71 Equally, if better ways of processing the XML become available, they can be
72 adopted without affecting the source maintenance.
74 A number of issues arose while setting this all up, which are best summed up by
75 the statement that a lot of the technology was (in 2006) still very immature.
76 Trying to do this conversion any earlier would probably not have been anywhere
77 near as successful. The main issues that bother me in the XML-generated
78 documentation are described in the penultimate section of this document.
80 Initially, the major problems were in producing PostScript and PDF outputs. The
81 available free software for doing this was and still is (we are now in 2007)
82 cumbersome and slow, and does not support certain output features that I would
83 like. My response to this was, over a period of two years, to write an XML
84 processor called SDoP (Simple DocBook Processor). This program reads DocBook
85 XML and writes PostScript, without using any of the heavyweight apparatus that
86 is required for xmlto and fop (the previously used software).
88 An experimental first version of SDoP was used for the Exim 4.67
89 documentation. Subsequently SDoP was released for general use. SDoP's output
90 includes features that are missing when xmlto/fop is used, and it also runs
91 about 60 times faster. The main manual can be formatted in 2.5 seconds instead
92 of 2.5 minutes, which makes checking and fixing mistakes much easier.
94 The Makefile that is used to build the various forms of output will, for the
95 moment, support both ways of producing PostScript and PDF output, though the
96 default is now to use SDoP.
98 The following sections describe the processes by which the xfpt files are
99 transformed into the final output documents. In practice, the details are coded
100 into a Makefile that specifies the chain of commands for each output format.
105 Installing software to process XML puts lots and lots of stuff on your box. I
106 run Gentoo Linux, and a lot of things have been installed as dependencies that
107 I am not fully aware of. This is what I know about (version numbers are current
108 at the time of writing):
112 This converts the master source file into a DocBook XML file.
116 This is my new DocBook-to-PostScript processor.
120 This is a wrapper script that is part of the GhostScript distribution. It
121 converts a PostScript file into a PDF file. It is used to process the output
122 from SDoP. It is not required when xmlto/fop is being used to generate PDF
127 This is a shell script that drives various XML processors. It is used to
128 produce "formatted objects" when PostScript and PDF output is being generated
129 using fop (the old way) rather than SDoP. It is always used to produce HTML
130 output. It uses xsltproc, libxml, libxslt, libexslt, and possibly other
131 things that I have not figured out, to apply the DocBook XSLT stylesheets.
137 These are all installed on my box; I do not know which of libxml or libxml2
138 the various scripts are actually using.
140 . xsl-stylesheets-1.70.1
142 These are the standard DocBook XSL stylesheets.
146 FOP is a processor for "formatted objects". It is written in Java. The fop
147 command is a shell script that drives it. It required only if you do not
148 want to use SDoP and ps2pdf to generate PostScript and PDF output.
152 This is a text-oriented web brower. It is used to produce the ASCII form of
153 the Exim documentation (spec.txt) from a specially-created HTML format. It
154 seems to do a better job than lynx.
156 . docbook2texi (part of docbook2X 0.8.5)
158 This is a wrapper script for a two-stage conversion process from DocBook to a
159 Texinfo file. It uses db2x_xsltproc and db2x_texixml. Unfortunately, there
160 are two versions of this command; the old one is based on an earlier fork of
161 docbook2X and does not work.
163 . db2x_xsltproc and db2x_texixml (part of docbook2X 0.8.5)
165 More wrapping scripts (see previous item).
169 This is used to make an "info" file from a Texinfo file.
171 In addition, there are a number of locally written Perl scripts. These are
177 The makefile supports a number of targets of the form x.y, where x is one of
178 "filter", "spec", or "test", and y is one of "xml", "fo", "ps", "pdf", "html",
179 "txt", or "info". The intermediate targets "x.xml" and "x.fo" are provided for
180 testing purposes. The other five targets are production targets. For example:
184 This runs the necessary tools in order to create the file spec.pdf from the
185 original source spec.xfpt. A number of intermediate files are created during
186 this process, including the master DocBook source, called spec.xml. Of course,
187 the usual features of "make" ensure that if this already exists and is
188 up-to-date, it is not needlessly rebuilt.
190 Because there are now two ways of creating the PostScript and PDF outputs,
191 there are two targets for each one. For example fop-spec.ps makes PostScript
192 using fop, and sdop-spec.ps makes it using SDoP. The generic targets spec.ps
193 and spec.pdf now point to the SDoP versions.
195 The "test" series of targets were created so that small tests could easily be
196 run fairly quickly, because processing even the shortish XML document takes
197 a bit of time, and processing the main specification takes ages -- except when
198 using SDoP for PostScript and PDF.
200 Another target is "exim.8". This runs a locally written Perl script called
201 x2man, which extracts the list of command line options from the spec.xml file,
202 and creates a man page. There are some XML comments in the spec.xml file to
203 enable the script to find the start and end of the options list.
205 There is also a "clean" target that deletes all the generated files.
208 CREATING DOCBOOK XML FROM XFPT INPUT
210 The small amount of local configuration for xfpt is included at the start of
211 the two .xfpt files; there are no separate local xfpt configuration files.
212 Running the xfpt command creates a .xml file from a .xfpt file. When this
213 succeeds, there is no output.
218 Processing a .xml file into the five different output formats is not entirely
219 straightforward. For a start, the same XML is not suitable for all the
220 different output styles. When the final output is in a text format (.txt,
221 .texinfo) for instance, all non-ASCII characters in the input must be converted
222 to ASCII transliterations because the current processing tools do not do this
223 correctly automatically.
225 In order to cope with these issues in a flexible way, a Perl script called
226 Pre-xml was written. This is used to preprocess the .xml files before they are
227 handed to the main processors. Adding one more tool onto the front of the
228 processing chain does at least seem to be in the spirit of XML processing.
230 The XML processors other than SDoP make use of style files, which can be
231 overridden by local versions. There is one that applies to all styles, called
232 MyStyle.xsl, and others for the different output formats. I have included
233 comments in these style files to explain what changes I have made. Some of the
234 changes are quite significant.
239 The Pre-xml script copies a .xml file, making certain changes according to the
240 options it is given. The currently available options are as follows:
244 This option is used for ASCII output formats. It makes the following
245 character replacements:
247 ’ => ' apostrophe
248 © => (c) copyright
250 ‡ => ** double dagger
251 => a space hard space
254 The apostrophe is specified numerically because that is what xfpt generates
255 from an ASCII single quote character. Non-ASCII characters that are not in
256 this list should not be used without thinking about how they might be
257 converted for the ASCII formats.
259 In addition to the character replacements, this option causes quotes to be
260 put round <literal> text items, and <quote> and </quote> to be replaced by
261 ASCII quote marks. You would think the stylesheet would cope with the latter,
262 but it seems to generate non-ASCII characters that w3m then turns into
267 This option causes the <bookinfo> element to be removed from the XML. It is
268 used for the PostScript/PDF forms of the filter document, in order to avoid
269 the generation of a full title page.
273 Replace any occurrence of "fi" by the ligature fi except when it is
274 inside an XML element, or inside a <literal> part of the text.
276 The use of ligatures would be nice for the PostScript and PDF formats. Sadly,
277 it turns out that fop cannot at present handle the FB01 character correctly.
278 Happily this problem is now avoided when SDoP is used to generate PostScript
279 (and thence PDF) because SDoP automatically uses an "fi" ligature for
280 non-fixed-width fonts.
282 The only xmlto format that handles FB01 is the HTML format, but when I used
283 this in the test version, people complained that it made searching for words
284 difficult. So this option is in practice not used at all.
288 Remove the XML to generate a Concept Index and an Options index. The source
289 document has three types of index entry, for variables, options, and concept
290 indexes. However, no index is required for the .txt and .texinfo outputs.
294 Remove the XML to generate separate variables, options, and concept indexes,
295 and add XML to generate a single index. The only output processors that
296 support multiple indexes are SDoP and the processor that produces "formatted
297 objects" for PostScript and PDF output for fop. The HTML processor ignores
298 the XML settings for multiple indexes and just makes one unified index.
299 Specifying three indexes gets you three copies of the same index, so this has
304 Look for items of the form <option>...</option> and <varname>...</varname> in
305 ordinary paragraphs, and insert ​ after each underscore in the
306 enclosed text. The same is done for any word containing four or more upper
307 case letters (compile-time options in the Exim specification). The character
308 ​ is a zero-width space. This means that the line may be split after
309 one of these underscores, but no hyphen is inserted.
312 CREATING POSTSCRIPT AND PDF
314 These two output formats are created either by using my new SDoP program to
315 produce PostScript which can then be run through ps2pdf to make a PDF, or by
316 using xmlto and fop in the old way.
319 USING SDOP TO CREATE POSTSCRIPT AND PDF
321 PostScript output is created in two stages. First, the XML is pre-processed by
322 the Pre-xml script. For the filter document, the <bookinfo> element is removed
323 so that no title page is generated. For the main specification, the only change
324 is to insert line breakpoints via -optbreak.
326 The SDoP program is then used to create PostScript output directly from the XML
327 input. Then the ps2pdf command is used to generated a PDF from the PostScript.
328 There are no external stylesheets that are used by SDoP. Any variations to the
329 default format are specified inline using "processing instructions".
332 USING XMLTO AND FOP TO CREATE POSTSCRIPT AND PDF
334 This is the original way of creating PostScript and PDF output. The processing
335 happens in three stages, with an additional fourth stage for PDF. First, the
336 XML is pre-processed by the Pre-xml script. For the filter document, the
337 <bookinfo> element is removed so that no title page is generated. For the main
338 specification, the only change is to insert line breakpoints via -optbreak.
340 Second, the xmlto command is used to produce a "formatted objects" (.fo) file.
341 This process uses the following stylesheets:
343 (1) Either MyStyle-filter-fo.xsl or MyStyle-spec-fo.xsl
348 The last of these is not used for the filter document, which does not have a
349 title page. The first three stylesheets were created manually, either by typing
350 directly, or by coping from the standard style sheet and editing.
352 The final stylesheet has to be created from a template document, which is
353 called MyTitlepage.templates.xml. This was copied from the standard styles and
354 modified. The template is processed with xsltproc to produce the stylesheet.
355 All this apparatus is appallingly heavyweight. The processing is also very slow
356 in the case of the specification document. However, there should be no errors.
358 The reference book that saved my life while I was trying to get all this to
359 work is "DocBook XSL, The Complete Guide", third edition (2005), by Bob
360 Stayton, published by Sagehill Enterprises.
362 In the third part of the processing, the .fo file that is produced by the xmlto
363 command is processed by the fop command to generate either PostScript or PDF.
364 This is also very slow, and you get a whole slew of errors, of which these are
367 [ERROR] property - "background-position-horizontal" is not implemented yet.
369 [ERROR] property - "background-position-vertical" is not implemented yet.
371 [INFO] JAI support was not installed (read: not present at build time).
372 Trying to use Jimi instead
373 Error creating background image: Error creating FopImage object (Error
374 creating FopImage object
375 (http://docbook.sourceforge.net/release/images/draft.png) :
376 org.apache.fop.image.JimiImage
378 [WARNING] table-layout=auto is not supported, using fixed!
380 [ERROR] Unknown enumerated value for property 'span': inherit
382 [ERROR] Error in span property value 'inherit':
383 org.apache.fop.fo.expr.PropertyException: No conversion defined
385 [ERROR] Areas pending, text probably lost in lineinclude parts matched in the
386 response by response_pattern by means of numeric variables such as
388 The last one is particularly meaningless gobbledegook. Some of the errors and
389 warnings are repeated many times. Nevertheless, it does eventually produce
390 usable output, though I have a number of issues with it (see a later section of
391 this document). Maybe one day there will be a new release of fop that does
392 better. In the meantime, I have written my own program for making PostScript
393 output -- see the previous section -- because the problems with xmlto/fop were
394 sufficiently annoying.
396 The PDF file that is produced by this process has one problem: the pages, as
397 shown by acroread in its thumbnail display, are numbered sequentially from one
398 to the end. Those numbers do not correspond with the page numbers of the body
399 of the document, which makes finding a page from the index awkward. There is a
400 facility in the PDF format to give pages appropriate "labels", but I cannot
401 find a way of persuading fop to generate these. Fortunately, it is possibly to
402 fix up the PDF to add page labels. I wrote a script called PageLabelPDF which
403 does this. They are shown correctly by acroread and xpdf, but not by
407 THE PAGELABELPDF SCRIPT
409 This script reads the standard input and writes the standard output. It is used
410 to "tidy up" the PDF output that is produced by fop. It is not needed when
411 PDF output is generated from SDoP's output using ps2pdf.
413 The PageLabelPDF script searches for the PDF object that sets data in its
414 "Catalog", and adds appropriate information about page labels. The number of
415 front-matter pages (those before chapter 1) is hard-wired into this script as
416 12 because I could not find a way of determining it automatically. As the
417 current table of contents finishes near the top of the 11th page, there is
418 plenty of room for expansion, so it is unlikely to be a problem.
420 Having added data to the PDF file, the script then finds the xref table at the
421 end of the file, and adjusts its entries to allow for the added text. This
422 simple processing seems to be enough to generate a new, valid, PDF file.
427 Only two stages are needed to produce HTML, but the main specification is
428 subsequently postprocessed. The Pre-xml script is called with the -optbreak and
429 -oneindex options to preprocess the XML. Then the xmlto command creates the
430 HTML output directly. For the specification document, a directory of files is
431 created, whereas the filter document is output as a single HTML page. The
432 following stylesheets are used:
434 (1) Either MyStyle-chunk-html.xsl or MyStyle-nochunk-html.xsl
438 The first stylesheet references the chunking or non-chunking standard DocBook
439 stylesheet, as appropriate.
441 You may see a number of these errors when creating HTML: "Revisionflag on
442 unexpected element: literallayout (Assuming block)". They seem to be harmless;
443 the output appears to be what is intended.
445 The original HTML that I produced from the SGCAL input had hyperlinks back from
446 chapter and section titles to the table of contents. These links are not
447 generated by xmlto. One of the testers pointed out that the lack of these
448 links, or simple self-referencing links for titles, makes it harder to copy a
449 link name into, for example, a mailing list response.
451 I could not find where to fiddle with the stylesheets to make such a change, if
452 indeed the stylesheets are capable of it. Instead, I wrote a Perl script called
453 TidyHTML-spec to do the job for the specification document. It updates the
454 index.html file (which contains the the table of contents) setting up anchors,
455 and then updates all the chapter files to insert appropriate links.
457 The index.html file as built by xmlto contains the whole table of contents in a
458 single line, which makes is hard to debug by hand. Since I was postprocessing
459 it anyway, I arranged to insert newlines after every '>' character.
461 The TidyHTML-spec script also processes every HTML file, to tidy up some of the
462 untidy features therein. It turns <div class="literallayout"><p> into <div
463 class="literallayout"> and a matching </p></div> into </div> to get rid of
464 unwanted vertical white space in literallayout blocks. Before each occurrence
465 of </td> it inserts so that the table's cell is a little bit wider than
468 The TidyHTML-spec script also takes the opportunity to postprocess the
469 spec_html/ix01.html file, which contains the document index. Again, the index
470 is generated as one single line, so it splits it up. Then it creates a list of
471 letters at the top of the index and hyperlinks them both ways from the
472 different letter portions of the index.
474 People wanted similar postprocessing for the filter.html file, so that is now
475 done using a similar script called TidyHTML-filter. It was easier to use a
476 separate script because filter.html is a single file rather than a directory,
477 so the logic is somewhat different.
482 This happens in four stages. The Pre-xml script is called with the -ascii,
483 -optbreak, and -noindex options to convert the input to ASCII characters,
484 insert line break points, and disable the production of an index. Then the
485 xmlto command converts the XML to a single HTML document, using these
488 (1) MyStyle-txt-html.xsl
492 The MyStyle-txt-html.xsl stylesheet is the same as MyStyle-nochunk-html.xsl,
493 except that it contains an addition item to ensure that a generated "copyright"
494 symbol is output as "(c)" rather than the Unicode character. This is necessary
495 because the stylesheet itself generates a copyright symbol as part of the
496 document title; the character is not in the original input.
498 The w3m command is used with the -dump option to turn the HTML file into ASCII
499 text, but this contains multiple sequences of blank lines that make it look
500 awkward. Furthermore, chapter and section titles do not stand out very well. A
501 local Perl script called Tidytxt is used to post-process the output. First, it
502 converts sequences of blank lines into a single blank lines. Then it searches
503 for chapter and section headings. Each chapter heading is uppercased, and
504 preceded by an extra two blank lines and a line of equals characters. An extra
505 newline is inserted before each section heading, and they are underlined with
508 The output of xmlto also contains non-ASCII Unicode characters that w3m passes
509 through. Fortunately, they are few, and Tidytxt cleans them up as well. Some
510 headings use "box drawing" characters in the range U+2500 to U+253F which are
511 translated into -+| as appropriate, and U+00A0 (hard space) and U+25CF (bullet)
512 are translated into plain spaces and asterisks. (It might be possible to do all
513 this in the same way as I dealt with copyright - see above - but adding a few
514 lines of Perl to an existing script was a lot easier.)
519 This process starts with the same Pre-xml call as for text files. Non-ascii
520 characters in the source are transliterated, and the <index> elements are
521 removed. The docbook2texi script is then called to convert the XML file into a
522 Texinfo file. However, this is not quite enough. The converted file ends up
523 with "conceptindex" and "optionindex" items, which are not recognized by the
524 makeinfo command. These have to be changed to "cindex" and "findex"
525 respectively in the final .texinfo file. Furthermore, the main menu lacks a
526 pointer to the index, and indeed the index node itself is missing. These
527 problems are fixed by running the file through a script called TidyInfo.
528 Finally, a call of makeinfo creates a .info file.
530 There is one apparently unconfigurable feature of docbook2texi: it does not
531 seem possible to give it a file name for its output. It chooses a name based on
532 the title of the document. Thus, the main specification ends up in a file
533 called the_exim_mta.texi and the filter document in exim_filtering.texi. These
534 files are removed after their contents have been copied and modified by the
535 TidyInfo script, which writes to a .texinfo file.
538 CREATING THE MAN PAGE
540 I wrote a Perl script called x2man to create the exim.8 man page from the
541 DocBook XML source. I deliberately did NOT start from the xfpt source,
542 because it is the DocBook source that is the "standard". This comment line in
543 the DocBook source marks the start of the command line options:
545 <!-- === Start of command line options === -->
547 A similar line marks the end. If at some time in the future another way other
548 than xfpt is used to maintain the DocBook source, it needs to be capable of
549 maintaining these comments.
554 There are a number of unresolved problems with producing the Exim documentation
555 in the manner described above. I will describe them here in the hope that in
556 future some way round them can be found. Some of the problems are solved by
557 using SDoP instead of xmlto/fop to produce PostScript and PDF output.
559 (1) When a whole chain of tools is processing a file, an error somewhere
560 in the middle is often very hard to debug. For instance, an error in the
561 xfpt file might not show up until an XML processor throws a wobbly because
562 the generated XML is bad. You have to be able to read XML and figure out
563 what generated what. One of the reasons for creating the "test" series of
564 targets was to help in checking out these kinds of problem.
566 (2) There is a mechanism in XML for marking parts of the document as
567 "revised", and I have arranged for xfpt markup to use it. However, the
568 only xmlto output format that pays attention to this is the HTML output,
569 which sets a green background. If xmlto/fop is used to generate PostScript
570 and PDF, there are no revision marks (change bars). This problem
571 is not present when SDoP is used. However, the text and Texinfo output
572 format lack revision indications.
574 (3) The index entries in the HTML format take you to the top of the section
575 that is referenced, instead of to the point in the section where the index
578 (4) The HTML output supports only a single index, so the variable, options,
579 and concept index entries have to be merged.
581 (5) The index for the PostScript/PDF output created by xmlto/fop does not
582 merge identical page numbers, which makes some entries look ugly. This is
583 not a problem when SDoP is used.
585 (6) The HTML index and the PostScript/PDF indexes, when made with xmlto/fop,
586 make no use of textual markup; the text is all roman, without any italic
587 or boldface. For PostScript/PDF, this is not a problem when SDoP is used.
589 (7) I turned off hyphenation in the PostScript/PDF output produced by
590 xmlto/fop, because it was being done so badly. Needless to say, I made
591 SDoP do a better job. These comments apply to xmlto/fop:
593 (a) It seems to force hyphenation if it is at all possible, without
594 regard to the "tightness" or "looseness" of the line. Decent
595 formatting software should attempt hyphenation only if the line is
596 over some "looseness" threshold; otherwise you get far too many
597 hyphenations, often for several lines in succession.
599 (b) It uses an algorithmic form of hyphenation that doesn't always produce
600 acceptable word breaks. (I prefer to use a hyphenation dictionary,
601 which is what SDoP does.)
603 (8) The PostScript/PDF output produced by xmlto/fop is badly paginated:
605 (a) There seems to be no attempt to avoid "widow" and "orphan" lines on
606 pages. A "widow" is the last line of a paragraph at the top of a page,
607 and an "orphan" is the first line of a paragraph at the bottom of a
610 (b) There seems to be no attempt to prevent section headings being placed
611 last on a page, with no following text on the page.
613 Neither of these problems occurs when SDoP is used to produce the
614 PostScript/PDF output.
616 (9) The fop processor does not support "fi" ligatures, not even if you put the
617 appropriate Unicode character into the source by hand. Again, this is not
618 a problem if SDoP is used.
620 (10) There are no diagrams in the new documentation. This is something I hope
621 to work on. The previously used Aspic command for creating line art from a
622 textual description can output Encapsulated PostScript or Scalar Vector
623 Graphics, which are two standard diagram representations. Aspic could be
624 formally released and used to generate output that could be included in at
625 least some of the output formats.
627 (11) The use of a "zero-width space" works well as a way of specifying that
628 Exim option names can be split, without hyphens, over line breaks.
630 However, when xmlto/fop is being used and an option is not split, if the
631 line is very "loose", the zero-width space is expanded, along with other
632 spaces. This is a totally crazy thing to, but unfortunately it is
633 suggested by the Unicode definition of the zero-width space, which says
634 "its presence between two characters does not prevent increased letter
635 spacing in justification". It seems that the implementors of fop have
636 understood "letter spacing" also to include "word spacing". Sigh.
638 This problem does not arise when SDoP is used.
640 The consequence of (7), (8), and (9) is that the PostScript/PDF output as
641 produced by xmlto/fop looks as if it comes from some of the very early attempts
642 at text formatting of around 20 years ago. We can only hope that 20 years'
643 progress is not going to get lost, and that things will improve in this area.
644 My small contribution to this has been to write SDoP, which, though simple and
645 "non-standard", does get some of these formatting issues right.
650 Markup.txt Describes the xfpt markup that is used
651 HowItWorks.txt This document
652 Makefile The makefile
653 MyStyle-chunk-html.xsl Stylesheet for chunked HTML output
654 MyStyle-filter-fo.xsl Stylesheet for filter fo output
655 MyStyle-fo.xsl Stylesheet for any fo output
656 MyStyle-html.xsl Stylesheet for any HTML output
657 MyStyle-nochunk-html.xsl Stylesheet for non-chunked HTML output
658 MyStyle-spec-fo.xsl Stylesheet for spec fo output
659 MyStyle-txt-html.xsl Stylesheet for HTML=>text output
660 MyStyle.xsl Stylesheet for all output
661 MyTitleStyle.xsl Stylesheet for spec title page
662 MyTitlepage.templates.xml Template for creating MyTitleStyle.xsl
663 Myhtml.css Experimental css stylesheet for HTML output
664 PageLabelPDF Script to postprocess xmlto/fop PDF output
665 Pre-xml Script to preprocess XML
666 TidyHTML-filter Script to tidy up the filter HTML output
667 TidyHTML-spec Script to tidy up the spec HTML output
668 TidyInfo Script to sort index problems in Texinfo output
669 Tidytxt Script to compact multiple blank lines
670 filter.xfpt xfpt source of the filter document
671 spec.xfpt xfpt source of the specification document
672 x2man Script to make the Exim man page from the XML
676 Last updated: 31 August 2007
git://git.exim.org / exim.git / blob