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 18:35:47 +0000 (UTC)	[thread overview]
Message-ID: <i82la3$t1v$1@dough.gmane.org> (raw)
In-Reply-To: i82k9i$m5v$1@dough.gmane.org

On 2010-09-30, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> On 2010-09-30, Darren Kirby <bulliver@gmail.com> wrote:
>> On Thu, Sep 30, 2010 at 11:13 AM, Grant Edwards
>><grant.b.edwards@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
>   http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1&chap=2  

OK, I think the problem is caused by "literal" blocks (the ones
containing command-line examples with the light-blue background where
nothing ever wraps).  The _minimum_ line-wrap length for normal text
paragraphs is determined by the _maximum_ line length in a literal
block. Resizing the browser window horizontally only reformats text
_if_ the window is wider than the longest literal block line.  For
many of the pages that requires more screen width than I, for one,
have.

IOW, for any pages with long command line examples (or program output
examples), you end up with very unweildy text paragraphs.

I'm not sure what formatting system the manual pages use (to me the
pages look way too clean, consistent, and neat to be hand-coded).  
Using asciidoc, for example, you avoid this problem by specifying a
maxmimum width for normal text blocks so that they won't end up being
arbitrarily long depending on what command line examples you happen to
have in the document.  I find 40em to be a nice max width:

  asciidoc -a data-uri -a toc -a max-width=40em <input-file>

>> I think that's a better solution than imposing some arbitrary line
>> length on everyone no matter their screen size and resolution.

No, I wouldn't want to impose an arbitrary line lenth on everybody,
but that's exactly what we have now.  The arbitrary line length that's
imposed is (length >= max(lengths-of-lines-in-literal-blocks)).

For pages without any wide literal blocks, it's not an issue, and the
normal paragaphs reflow as they should.  For most of the manual pages
that I look at, it is an issue.

I'd prefer to have the line lengths determined by the browser window,
and that's not what we have now for much of the manual.

-- 
Grant Edwards               grant.b.edwards        Yow! Edwin Meese made me
                                  at               wear CORDOVANS!!
                              gmail.com            




  parent reply	other threads:[~2010-09-30 18:36 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 [this message]
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
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='i82la3$t1v$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