public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] [porting] web page widths
Date: Fri, 05 Jan 2001 11:36:00 -0000	[thread overview]
Message-ID: <20010105133932.A2609@visi.com> (raw)

First I'd like to compliment you guys on the nice clean HTML
used on your web pages.  That said, there is one minor thing
thing that bugs me -- but from what I know about HTML there
isn't much that can be done about it:

I've notced that the minimum width of the right hand column of
the web pages (white background with text) is set by the width
of any <pre></pre> sections (usually containing souce code
examples). On some pages those examples contain long lines,
resulting in tables where the normal (non-preformatted)
paragraphs have very long lines that don't wrap to fit
reasonable window widths. The user has to scroll left/right to
read the text.

I don't mind scrolling back and forth to see pre-formatted
source examples, but it would be nice if the normal paragaphs
wrapped to fit inside the browser window. Unfortunately, I
can't think of any suggestions on how to generate HTML that
would act that way, since the min column width is determined by
the widest object it contains. Arbitrarily wrapping source code
examples would be a bad idea, since it would make them harder
to understand. Changing to a smaller font size for fixed-width
text helps somewhat.

Like I said it's a minor problem, and I don't think there's
much that can be done about it...

-- 
Grant Edwards
grante@visi.com

             reply	other threads:[~2001-01-05 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 11:36 Grant Edwards [this message]
2001-01-05 12:30 ` Grant Edwards
2001-01-08  0:14 ` Jesper Skov
2001-01-08  7:38   ` Grant Edwards

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=20010105133932.A2609@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).