public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at systemhalted dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug admin|web|git/11934] web pages: small fonts in CSS
Date: Fri, 10 Feb 2012 21:39:00 -0000	[thread overview]
Message-ID: <bug-11934-131-lXseMPwzyJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11934-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=11934

--- Comment #5 from Carlos O'Donell <carlos at systemhalted dot org> 2012-02-10 21:39:10 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > Scaling pages is the best way to get consistently readable text, you need to
> > scale the layout elements along with the text size to maintain readability. 
> 
> No, having the pages always in a readable font size is the best way to get
> readable text.

Good point.

> > I didn't say "em" was *not* scaled, I said `px' and page scaling is in my
> > opinion *much* more readable. Why? Scaling fonts does not scale the layout
> > elements that contain the fonts,
> 
> You're wrong! If you specify a layout element to have some width in "em" and
> scale the font, the element will be scaled in the same proportion.

You are correct.

> > often resulting in overlapping text that is unreadable.
> 
> Because the pages are not well-designed. The main text (which is particularly
> important to be readable) should be allowed to be rendered in elements that do
> not have a fixed size, and adapt to the window width. Element widths can also
> often be determined automatically from the text they contain, thus avoiding
> overlapping text.

Good point.

This is in fact the way the main text on the new glibc website is laid out. The
central column does not have a fixed size and adapts to the window width.
Though below a minimum width it begins to wrap oddly.

> > On device with small screens you need to scale the entire rendered
> > view and pan to read (or detect the device and rendering a completely
> > different page).
> 
> And that's very bad. Horizontal scrolling (at each line) makes reading very
> difficult. Good web designers know to handle small screens in the same way as
> large screens. Contrary to formats with a fixed rendering such as PDF, HTML/CSS
> has been designed to allow the document to be rendered on various media (not
> necessarily graphic BTW).

I agree that it's bad.

Thank you for your feedback!

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-02-10 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11934-131@http.sourceware.org/bugzilla/>
2012-02-07 18:58 ` carlos at systemhalted dot org
2012-02-08  2:12 ` vincent-srcware at vinc17 dot net
2012-02-08 14:28 ` carlos at systemhalted dot org
2012-02-10  9:30 ` vincent-srcware at vinc17 dot net
2012-02-10 21:39 ` carlos at systemhalted dot org [this message]
2012-02-11  2:13 ` vincent-srcware at vinc17 dot net
2012-02-11 23:21 ` carlos at systemhalted dot org
2014-06-30  8:14 ` [Bug admin/11934] " fweimer at redhat dot com

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=bug-11934-131-lXseMPwzyJ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).