public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: ridiculously wide handbook pages
Date: Thu, 30 Sep 2010 19:42:05 +0000 (UTC)	[thread overview]
Message-ID: <i82p6d$k6r$1@dough.gmane.org> (raw)
In-Reply-To: 4CA4E19D.7000303@gmail.com

On 2010-09-30, Dale <rdalek1967@gmail.com> wrote:
> Grant Edwards wrote:
>
>>>>     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.

I think that's definitely the issue.

> Whatever is the longest line sets the width.  How would one go about
> changing that I wonder?

I think it can probably be set in the CSS stylesheet, but I'm pretty
fuzzy when it comes to CSS details.

I do know that the web pages I generate with asciidoc don't have this
problem.  In general, the width of the text paragraphs is determined
by the browser width, but listing blocks don't get wrapped and you may
have to scroll over to see the ends of the really wide ones.  I
usually set a max text width as well, so that if you do widen your
browser window to see the really wide listing blocks, you still end up
with text columns that max out at a reasonable width.  Setting a
max-width for text is probably more a matter of taste/style, but I
don't think that anybody can argue that having the minium text width
determined by the maximum listing width is right.

> 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.

We definitely don't want to wrap things like command lines, config
file listings, code listings, and program input/output.  That's why
you (directly or indirectly) assign them a different CSS style or
object type -- so that you can do things like wrap normal text and not
listings or examples.

> 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?

I don't think listings/code/shell-examples should not be wrapped, and
AFAIK, nobody's arguing that they should be.

However, I do assert that normal text paragraphs should be wrapped to
fit within the browser window.

In text-only e-mail messages, there's no way to tell the difference
between the two.

Whatever's generating the HTML/CSS for the Gentoo manual web pages
does know the difference, and should be able to do The Right
Thing(tm). The manual HTML is definitely machine-generated, but I
can't tell you by what at this point, so I can't offer a specific
fix...

-- 
Grant Edwards               grant.b.edwards        Yow! Can you MAIL a BEAN
                                  at               CAKE?
                              gmail.com            




  reply	other threads:[~2010-09-30 19:42 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 17:13 [gentoo-user] ridiculously wide handbook pages Grant Edwards
2010-09-30 17:26 ` Volker Armin Hemmann
2010-09-30 17:57   ` [gentoo-user] " Grant Edwards
2010-09-30 17:59 ` [gentoo-user] " Darren Kirby
2010-09-30 18:18   ` [gentoo-user] " Grant Edwards
2010-09-30 18:31     ` Darren Kirby
2010-09-30 18:36       ` Grant Edwards
2010-09-30 18:55         ` Darren Kirby
2010-09-30 19:23           ` Grant Edwards
2010-09-30 20:34             ` Jörg Schaible
2010-09-30 20:55               ` Grant Edwards
2010-09-30 21:13               ` Grant Edwards
2010-09-30 18:35     ` Grant Edwards
2010-09-30 18:39     ` Dale
2010-09-30 18:50       ` Grant Edwards
2010-09-30 19:14         ` Dale
2010-09-30 19:42           ` Grant Edwards [this message]
2010-09-30 19:50             ` Dale
2010-09-30 20:05               ` Grant Edwards
2010-09-30 20:41                 ` Dale
2010-09-30 18:11 ` [gentoo-user] " Al
2010-09-30 18:19   ` [gentoo-user] " Grant Edwards
2010-09-30 18:23 ` Nikos Chantziaras
2010-09-30 18:34 ` [gentoo-user] " Mark Knecht
2010-09-30 18:39   ` Darren Kirby
2010-09-30 18:49     ` [gentoo-user] " Grant Edwards
2010-09-30 18:39   ` Grant Edwards
2010-09-30 22:53 ` [gentoo-user] " Jacob Todd
2010-09-30 23:15   ` [gentoo-user] " Grant Edwards
2010-09-30 23:18     ` Jacob Todd
2010-10-01  0:27       ` Dale
2010-10-01  0:59         ` Jacob Todd
2010-10-01 22:18 ` [gentoo-user] " Renat Golubchyk
2010-10-02  2:16   ` Stroller
2010-10-02  9:06     ` Renat Golubchyk
2010-10-03 17:32       ` Peter Humphrey
2010-10-04  2:00         ` Renat Golubchyk
2010-10-04  6:24           ` Mick
2010-10-04 10:20           ` Peter Humphrey
2010-10-02  3:21   ` [gentoo-user] " Grant Edwards
2010-10-04 17:06   ` [gentoo-user] " Fatih Tümen
2010-10-04 18:24     ` [gentoo-user] " Grant Edwards
2010-10-04 18:27     ` [gentoo-user] " Derek Tracy
2010-10-04 19:20       ` Fatih Tümen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='i82p6d$k6r$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox