I think the <PRE> tag is a great idea, too. The problem with not
having newlines significant is that it makes it difficult to do
indenting, etc. One of the reasons the <PRE> tag is nice is that you
can take text (eg, manual entries) and not worry about formatting:
eg
OPTIONS
-b this option performs the blah command. And if this line is
reasonably long, I can demonstrate what I'm talking about.
-f this option performs the foo command. Another annoying prob-
lem is hyphenation.
This sort of thing caused me quite a lot of bother in the first
version of my manual page formatter. If the newline is not
significant, then does it put lots of spaces between the 'is' and the
'reasonably', or does it join them with a space? Also, if the new
break was to be between 'can' and 'demonstrate' (for example), how
would the browser know where to start the new line ('demonstrate').
The only misgiving I have about it is that you are formatting text for
a set width, something avoided in the past, but I think the value of
having good-looking formatted text outweighs this.
rik.
-- Rik Harris - [email protected] +61 3 571-2895 (AH & ans.mach) +61 3 573-2679 (BH) (both soon changing) Faculty of Computing and Information Technology, Caulfield Campus, Monash University, Australia (soon moving to Clayton)