On 05 May 2003 14:59:53 +0200, Uwe Pross wrote:
>
> On 30 Apr 2003 at 14:48:23 +0000, Mikhael Goikhman wrote:
>
> > > A line break inside a command descriptions may confuse the
> > > user. That's why <pre> was used. I would leave it as it is
> > > or add a statement that the following command must be without a
> > > linebreak.
> >
> > I think css allows to define different margins/alighment for continuation
> > lines than the corresponding properties for the leading lines.
> > If you may find the css solution to reduce a confusion, it would be nice.
>
> I noticed that you have changed <pre class="cvs"> to
> <p class="cmdline"> in file dev_cvs.php already. A better
> way to achieve linebreaks is using <pre class="cvs"> and
> allow line breaking explicitly. With
>
> pre.cvs {
> white-space:normal;
> }
>
> This makes all "command line text" in the same style in the
> file and works with all browsers. If browsers don't obey to
> style sheet lines are not wrapped put displayed in fixed
> font.
So the old browsers show the same original problem this thread is started
from. Also this does not solve the confusion between the continuation
lines and the leading lines. What exactly this would solve?
> I would like to turn it back to <pre class="cvs">.
We don't really should use a monospace font (usually wide) for commands.
<p> or <div> with <br> would look nicer for a visitor, although it needs a
bit more work to write. For me, we should write all commands inside
<p class="cmdline">, but if you see a better solution, do it.
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
