From: Jan Hudec <bulb@ucw.cz>
To: Chris Riddoch <riddochc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: gitweb css - pixels?!
Date: Tue, 8 May 2007 10:36:44 +0200 [thread overview]
Message-ID: <20070508083644.GA9007@efreet.light.src> (raw)
In-Reply-To: <6efbd9b70705071613p23017509qaf9af12c1d14f9cb@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]
On Mon, May 07, 2007 at 17:13:42 -0600, Chris Riddoch wrote:
> Hi, folks.
>
> I've been gradually converting my ~/src directory full of tarballs
> I've found interesting enough to download to a ~/repos/ directory
> containing bare git repositories of the projects. I was thinking it
> might be worth my while to set up gitweb so I can peruse my collection
> of projects.
>
> I noticed myself squinting, on my 1400x1050 laptop screen, at the 10
> and 12-*pixel* font settings gitweb's CSS specifies before thinking to
> myself that I should bring this to the list's attention.
>
> I'm no CSS guru, or I'd just provide a patch. It seems that *all* the
> measurements specified in the CSS file are in pixels, not ems or
> percentages. There's got to be a better way. I can't be the only
> person who would rather use my nice screen to render attractive,
> readable fonts rather than to render the smallest possible fonts?
Well, there should be three ways to set font sizes:
1. Use the symbolic small, normal, large..., which are derived from user
settings (normal is user setting, large is one step larger etc.). IMHO
this would be the best variant.
2. Use *points* (pt) instead of *pixels* (px). Unfortunately most browsers
don't know what their DPI is and will treat 1pt as 1px, even though they
have more than 72dpi. I believe this applies to all Micro$oft browsers.
3. Use designation relative to previous font. One step up is 1.2em, one step
down is 0.8333333em. I am not sure this actually works in Micro$oft
browsers. Also rounding errors may quickly get you to completely
different font size that you wanted.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-08 8:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 23:13 gitweb css - pixels?! Chris Riddoch
2007-05-08 1:23 ` Allan Wind
2007-05-08 4:43 ` Chris Riddoch
2007-05-08 8:36 ` Jan Hudec [this message]
2007-05-09 1:41 ` [PATCH] gitweb: Do not use absolute font sizes Petr Baudis
2007-05-09 5:54 ` Junio C Hamano
2007-05-09 13:47 ` Petr Baudis
2007-05-09 6:48 ` Chris Riddoch
2007-05-14 16:53 ` Jakub Narebski
2007-05-15 1:06 ` David Kågedal
2007-05-15 15:09 ` Jan Hudec
2007-05-15 23:59 ` Jakub Narebski
2007-05-16 10:51 ` [PATCH] gitweb: Change base font size to "small" Jakub Narebski
2007-05-17 2:17 ` Petr Baudis
2007-05-17 4:07 ` Junio C Hamano
2007-05-17 8:31 ` Jakub Narebski
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=20070508083644.GA9007@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=riddochc@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.