Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 0CABC633F97 for ; Tue, 31 Aug 2010 14:37:56 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 89037-09 for ; Tue, 31 Aug 2010 17:37:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by mail.postgresql.org (Postfix) with ESMTP id A1EC5633F46 for ; Tue, 31 Aug 2010 14:37:48 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id o7VHbgG24526; Tue, 31 Aug 2010 13:37:42 -0400 (EDT) From: Bruce Momjian Message-Id: <201008311737.o7VHbgG24526@momjian.us> Subject: Re: [pgsql-www] Example indenting In-Reply-To: To: Thom Brown Date: Tue, 31 Aug 2010 13:37:42 -0400 (EDT) CC: Tom Lane , jd@commandprompt.com, Kevin Grittner , Dave Page , pgsql-docs@postgresql.org, Erik Rijkers X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201008/158 X-Sequence-Number: 5982 Thom Brown wrote: > In a way I am. Users have the ability (although not often exercised) > to change the default font and size. I gave the HTML tag a font-size, > so that anything under it would be based on that. We use relative > font sizes in our CSS, which means usually we'd be proportional to > whatever the user had set. But what I've done is set a base size > (17px in this case, and only in documentation) which everything else > will be based on. So the downside is whatever the user set their > default font size to in their browser will be ignored (or not fallen > back to if you prefer). This doesn't, however, prevent them from > using a text zoom (available in pretty much every web browser) to > increase the size of all rendered fonts. > > The problem is, by default, Firefox sets proportional fonts to 16px, > and monospace to 12px, so there's always a visual discrepancy when > these fonts appear alongside one another. > > But the benefit of the javascript hack was that we weren't setting a > base font size for everything, we just bump up the relative font size > for elements which are monospaced by default. > > There's pros and cons to both approaches. I'm not sure which one you > guys prefer. If we are using Javascript, why can't we probe the font size and do something reasonable, e.g. make monospace larger only if it smaller than proportional? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +