Paul@digicool.com said:

Let's say I quote a snippet of Python and I put in a break where the author didn't intend a break to be. Hmm, that seems like bad style.

In that case, I always make my preview window reasonably small, and redo the lines by manually breaking them and appending backslashes until they fit. Python programmers will understand this in program snippets, because it is valid syntax. Unix people understand it in shell commands because the backslash as escape character seems to be hardwired in their minds. As for MS-DOS - you don't want to have long command lines there ;-) (but in emergency cases, a small note at the start of the text will help). If STX cannot handle this, it may be a good idea to add it - nothing irritates a lot of people more than pages that don't resize with their browser for non-obvious reasons (the obvious reasons being broad images or tables). -- Cees de Groot http://www.cdegroot.com <cg@cdegroot.com>

Paul Everitt wrote:

Cees wrote:

...

bob@rocnet.com said:

...

TEXT Does NOT wrap! It requires using scroll bars to read.

I noticed the same with Netscape. Even though my laptop does 1024x768, it's a PITA and bad style to have non-wrapping text.

OK, I'll bite...let's say I have a <PRE> block encoding the rewrite rule for Apache. Putting in a line break would break it.

But do they have to be indented that much? smaller indents, or placing the code within a colored table cell instead of using <PRE>, might work better. Michael Bernstein.