View mode: basic / threaded / horizontal-split · Log in · Help
March 09, 2007
Re: New look for archives
Walter Bright wrote:
> vanh wrote:
>> Would be nicer if the quote text is in different color or gray out.
> 
> It is in a slightly different color. I think greying it out would make 
> it harder to read.
> 
> If you look closely, you'll see that each nested quote has a slightly 
> smaller font <g>.
Yes, but it's only 2 level how about couple more level that would cover 
~ 80% :-)

vtp
March 11, 2007
Re: New look for archives
Walter Bright Wrote:

> Vladimir Panteleev wrote:
>> I'd still suggest making the text inside the <pre> blocks 
>> wrappable.  You can do this either by using ordinary <div>s 
>> instead of <pre>s for the PostingBody, or adding the 
>> following CSS attribute to the PostingBody class in 
>> /d/style.css:
>> 
>> white-space: normal;
>> 
>> This will make user-agents rewrap text, eliminating 
>> horizontal scroll bars.
> 
> I tried it, but it wraps code, too, goofing it all up.

Not to mention that:
- it would destroy indentation as it did before, unless you 
explicitly convert leading spaces, multiple spaces and tabs to 
&nbsp;

- it would create a mess of line breaks in strange places for 
some of us, who may be using lower-resolution displays or a 
large font.

But a good course of action, at least IMO, would be handle 
format=flowed messages by setting word wrap and using explicit 
<br> for the hard line breaks.

BTW I noticed a bug - it fails to replace & with &amp;.  As well 
as being just one cause of the many validation errors, it's 
bound to alter what some people wrote, including here.

Stewart.
March 11, 2007
Re: New look for archives
Vladimir Panteleev Wrote:

<snip>
> I'd still suggest making the text inside the <pre> blocks 
> wrappable.  You can do this either by using ordinary <div>s 
> instead of <pre>s for the PostingBody, or adding the following 
> CSS attribute to the PostingBody class in /d/style.css:
> 
>     white-space: normal;
<snip>

What would be the point of using <pre> at all if you're just 
going to cancel out its semantics with CSS?

Stewart.
March 12, 2007
Re: New look for archives
Stewart Gordon wrote:
> Walter Bright Wrote:
>> I tried it, but it wraps code, too, goofing it all up.
> 
> Not to mention that:
> - it would destroy indentation as it did before, unless you 
> explicitly convert leading spaces, multiple spaces and tabs to 
> &nbsp;
> 
> - it would create a mess of line breaks in strange places for 
> some of us, who may be using lower-resolution displays or a 
> large font.
> 
> But a good course of action, at least IMO, would be handle 
> format=flowed messages by setting word wrap and using explicit 
> <br> for the hard line breaks.

I did it a simpler way - I just put the line wrapping in the converter 
program.

> BTW I noticed a bug - it fails to replace & with &amp;.  As well 
> as being just one cause of the many validation errors, it's 
> bound to alter what some people wrote, including here.

Oops.
Next ›   Last »
1 2
Top | Discussion index | About this forum | D home