Bug 690275

Summary:	Ghostscript history contains horizontal scrolling segments
Product:	Ghostscript	Reporter:	goldart.geo
Component:	Documentation	Assignee:	Chris Liddell (chrisl) <chris.liddell>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	christinedelight.top85
Priority:	P4
Version:	8.64
Hardware:	All
OS:	All
Customer:		Word Size:	---

Description goldart.geo 2009-02-06 19:12:00 UTC

In the Ghostscript 8.64 change log, there are many log entries contain very long
lines that are not wrapped to the width of browser window, which will require
horizontal scrolling to view the contents. Not only the viewing experience is
disruptive, it can lead to readers missing crucial contents.
------------------------------------------------------------------------
Ghostscript version (or include output from "gs -h"): 8.64
------------------------------------------------------------------------
Where you got Ghostscript: Ghostscript.com
------------------------------------------------------------------------
Hardware system you are using (including printer model if the problem
involves printing):

Memory: 384MB
CPU: Intel Pentium II 400
Sound: ESS Solo-1
Video: Neomagic MagicMedia 256AV
------------------------------------------------------------------------
Operating system you are using: Windows 98SE
------------------------------------------------------------------------
Suggested fix, if any:

The change logs contain too many preformatted sections that clearly serve no
purposes, and eventually lead to some lines not properly wrapped, and thus
horizontal scrolling. Unless there are texts that need to be rendered in
preformatted fashion (eg: code fragment), all change log entries must not be
preformatted. If preformatted texts are needed, only preformat the necessary
portions. Similarly, if monospaced texts are needed, only apply <tt>...</tt> to
the necessary portions. That can reduce the chance of manual entry errors
ruining the document's appearance, and make the logs more readable, and has the
side benefit for reducing the log's page count by reducing unnecessary white
spaces and monospaced texts.
------------------------------------------------------------------------
Other comments:

Comment 1 Hin-Tak Leung 2010-08-02 00:32:10 UTC

Re-assigning bugs which still have work to do.

Comment 2 Ray Johnston 2010-09-09 18:15:09 UTC

Changing this to use put the log message in <tt> ... </tt> keeps the
distinction from the "title" line, then the toolbin/split_changelog.py
can be changed to detect empty lines in the log message and insert <p>.

This will compensate for those log messages which aren't pre-formatted
as they sometimes are.

Comment 3 Chris Liddell (chrisl) 2013-05-07 16:10:01 UTC

We try to stick to the git commit message protocol now, so I feel we're okay on this one.