[bug-gs] 8.12: minor issues: doc

der Mouse mouse at Rodents.Montreal.QC.CA
Mon Dec 22 15:16:02 PST 2003


[Ray Johnston <ray.johnston at artifex.com>]
> A single bug report with all of the issues is fine since [...].
> If it is convenient to send the documentation issues separately from
> the build issues, that's slightly preferable, [...]

Okay, here are the doc issues.

In doc/Language.htm:

	<b><tt>%statementedit</tt></b>, <b><tt>%os%</tt></b>, and (if configured)
	<b><tt>%pipe%</tt></b> and <b><tt>%disk0%</tt></b> through <b><tt>%disk0%</tt></b>.
	</ul>

    Surely that's not right (disk0 through disk0?).

In doc/Language.htm:

	        <td>values (samples \xc3\x97 components)<br>for1-, 2-, 4-, or 8-bit samples
	        <td>&nbsp;

    (a) what's that between "samples" and "components"?  It appears to
    be the UTF-8 encoding of U00d7, which is the × character.  But I
    didn't see anything anywhere that indicates what character set or
    encoding those files are supposed to be in; wouldn't it be better
    to stick to ASCII?  There are only two other places where non-ASCII
    characters are used (the Ulrichskötter name in Make.htm and a © in
    README), and they are both simple 8859 rather than UTF-8.

    (b) "for1-" is missing a space.

In doc/Language.htm:

	There is no file name conflicts because
	<b><tt>lib</b></tt> does not contain subdirectories, but <b><tt>Resource</b></tt>

    Plural/singular clash (is...conflicts).

In doc/Issues.htm:

	<h3>bbox device doesn't allow min coords < 0.</h3>

    I'm no HTML expert, and this does seem to "work" in lynx, but
    wouldn't it be better to s/ < / \&lt; / here?

In doc/Install.htm:

	to many modern software packages. In general the following with suffice
	to build ghostscript:

    s/with/will/ surely?

In doc/Make.htm:

	in extracting files.  The Ghostscript source archive puts all files under a
	directory <b><tt>gs</tt></b>#.##, so using <b><tt>tar</tt></b> to unpack a
	compressed archive should always properly create that directory, which we
	will call the "gs directory".  Make sure you're positioned in the

    ghostscript-8.12.tar.bz2 unpacks to ghostscript-8.12, not gs8.12.

In doc/Make.htm:

    Should it maybe mention where the various makefiles are to be
    found?  I had to use find to discover where they were lurking.

In doc/Make.htm:

	subset of the available device drivers.  The complete list of features is
	in a comment at the beginning of <b><tt>gs.mak</tt></b>, and the complete

    but gs.mak specifically says the list there is _not_ complete:

	#               There are quite a number of other sub-features that can be
	#               selectively included in or excluded from a configuration,
	#               but the above are the ones that are most likely to be of
	#               interest.

In src/unix{-gcc,ansi}.mak:

    Maybe the shared-library sections should explain the settings
    (0-vs-1) for the SHARE_* variables?  My reaction on seeing them set
    to 0 was "is there some funky shared library scheme that uses .0
    instead of .so?", though that was followed fairly quickly by a
    "nah, couldn't be", which turned out to lead to the correct
    conclusion.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse at rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B


More information about the bug-gs mailing list