public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-srcware at vinc17 dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug admin|web|git/11934] web pages: small fonts in CSS Date: Wed, 08 Feb 2012 02:12:00 -0000 [thread overview] Message-ID: <bug-11934-131-p8wJZqpDBd@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 #2 from Vincent Lefèvre <vincent-srcware at vinc17 dot net> 2012-02-08 02:11:29 UTC --- (In reply to comment #1) > The currently website uses `px' to specify exact font sizes in relation to the > page layout. We expect users to use browsers scaling support or assistive > technology to make the page view bigger. Well, it would be very annoying to have to scale the page each time one goes to a new site, because each site hardcodes the font size in inconsistent ways. Moreover not all browsers are able to easily enlarge the page without reformatting it (so that one doesn't have to do a horizontal scroll after reading each line). See Nokia's browser for the N900, for instance. > Using `px' and scaling makes the page > *much* more readable than using "em" and font size changes. The latter can > suffer from improper layout and difficult to read enlarged text, while the > former results in a uniformly scaled website that is easy to scroll and read. This is plainly wrong. The "em" (or percentage if you prefer) is a relative font size, so that if you scale the font, every font should be scaled in the same proportion. > We don't plan to change this any time soon, but if you still have problems > reading the page I'd be more than happy to work with you on the problem e.g. > configuring your browser or other technology. Actually the current settings now appear to be OK (at least consistent with my default choices). -- 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.
next prev parent reply other threads:[~2012-02-08 2:12 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 [this message] 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 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-p8wJZqpDBd@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: linkBe 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).