Grant Edwards wrote:
On 2010-09-30, Dale<rdalek1...@gmail.com> wrote:
Grant Edwards wrote:
On 2010-09-30, Darren Kirby<bulli...@gmail.com> wrote:
On Thu, Sep 30, 2010 at 11:13 AM, Grant Edwards
<grant.b.edwa...@gmail.com> wrote:
I can understand that things like example code blocks or sample
command input/output blocks might need to be wide enough to require
horizontal scrolling of a browser window, but normal text paragraphs
with 160 characters per line?
I'm not seeing a problem here. Sure, the lines are long but my screen
is large and my resolution is high. A quick play with firefox and konq
shows that the text reformats itself quite elegantly when you resize
your browser window to say, 2/3 of screen width.
I'm using firefox, and the text doesn't reformat for me. I just end
up with a change in the size of the horizontal scrollbar. Are you
sure you're looking at the same pages I was talking about?
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1
The link above works fine although a bit wide. No horizontal scrollbar.
And what happens when you narrow the window to say 2/3 of that width?
Do the text paragrphs reformat to the new width, or do you just end up
with a scrollbar and paragraphs that you have to scroll right to read?
If I narrow it a good bit, it does give me a scrollbar. The line
lengths look OK tho. At least for this page. The line lengths could be
shorter and still be good to tho.
http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1&chap=2
This one has a horizontal scrollbar but only adjust about a half inch or
so. It almost fits.
Are the text paragraphs re-wrapped as you narrow the window?
That one has a scrollbar no matter what. It appears that section "Code
Listing 2.4: Using SH4 cross-compiler" is making it really long. It has
a line in that box that is pretty long. It's the longest line I saw in
the whole page.
So, it appears as someone else posted that the pretty blue boxes set the
minimum width. Whatever is the longest line sets the width. How would
one go about changing that I wonder? I know when someone posts a long
command on this mailing list, it makes it hard to understand when
Seamonkey shops it up into two lines. Most people are good enough to
post that the command has to be all on one line tho. It appears that a
email problem is also a website problem too. When to wrap a line and
when not to?
Dale
:-) :-)
