23rd September 2021: PostgreSQL 14 RC 1 Released!
Unsupported versions: 6.5
This documentation is for an unsupported version of PostgreSQL.
You may want to view the same page for the current version, or one of the other supported versions listed above instead.

Hardcopy Generation for v6.5

The hardcopy Postscript documentation is generated by converting the SGML source code to RTF, then importing into ApplixWare-4.4.1. After a little cleanup (see the following section) the output is "printed" to a postscript file.

Text Hardcopy

INSTALL and HISTORY are updated for each release. For historical reasons, these files are in plain text, but are derived from the newer SGML sources.

Plain Text Generation

Both INSTALL and HISTORY are generated from existing SGML sources. They are extracted from the same intermediate RTF file.

  1. Generate RTF by typing:

    % cd doc/src/sgml
    % make installation.rtf
  2. Import installation.rtf into Applix Words.

  3. Set the page width and margins.

    1. Adjust the page width in File.PageSetup to 10 inches.

    2. Select all text. Adjust the right margin using the ruler to 9.5 inches. This will give a maximum column width of 79 characters, within the 80 columns upper limit goal.

  4. Lop off the parts of the document which are not needed.

    For INSTALL, remove all release notes from the end of the text, except for those from the current release. For HISTORY, remove all text up to the release notes, preserving and modifying the title and ToC.

  5. Export the result as “ASCII Layout”.

  6. Using emacs or vi, clean up the tabular information in INSTALL. Remove the “mailto” URLs for the porting contributors to shrink the column heights.

Postscript Hardcopy

Several items must be addressed in generating Postscript hardcopy:

Applixware RTF Cleanup

Applixware does not seem to do a complete job of importing RTF generated by jade/MSS. In particular, all text is given the “Header1” style attribute label, although the text formatting itself is acceptable. Also, the Table of Contents page numbers do not refer to the section listed in the table, but rather refer to the page of the ToC itself.

  1. Generate the RTF input by typing (for example):

    % cd doc/src/sgml
    % make tutorial.rtf
  2. Open a new document in Applix Words and then import the RTF file.

  3. Print out the existing Table of Contents, to mark up in the following few steps.

  4. Insert figures into the document. Center each figure on the page using the centering margins button.

    Not all documents have figures. You can grep the SGML source files for the string “graphic” to identify those parts of the documentation which may have figures. A few figures are replicated in various parts of the documentation.

  5. Work through the document, adjusting page breaks and table column widths.

  6. If a bibliography is present, Applix Words seems to mark all remaining text after the first title as having an underlined attribute. Select all remaining text, turn off underlining using the underlining button, then explicitly underline each document and book title.

  7. Work through the document, marking up the ToC hardcopy with the actual page number of each ToC entry.

  8. Replace the right-justified incorrect page numbers in the ToC with correct values. This only takes a few minutes per document.

  9. Save the document as native Applix Words format to allow easier last minute editing later.

  10. “Print” the document to a file in Postscript format.

  11. Compress the Postscript file using gzip. Place the compressed file into the doc directory.