X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP
	id 61AB8D1B578; Thu, 20 Nov 2003 20:57:01 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 08107-10; Thu, 20 Nov 2003 16:56:32 -0400 (AST)
Received: from cookie.varlena.com (adsl-64-142-36-103.sonic.net
	[64.142.36.103]) by svr1.postgresql.org (Postfix) with ESMTP
	id 9A178D1C969; Thu, 20 Nov 2003 16:56:29 -0400 (AST)
Received: by cookie.varlena.com (Postfix on SuSE Linux 7.3 (i386),
	from userid 500) id 8E3FE38C85; Thu, 20 Nov 2003 13:55:01 -0800 (PST)
Date: Thu, 20 Nov 2003 13:55:01 -0800
From: elein <elein@varlena.com>
To: Guillaume LELARGE <gleu@wanadoo.fr>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	Michael Glaesemann <grzm@myrealbox.com>, pgsql-www@postgresql.org,
	pgsql-docs@postgresql.org
Subject: Re: [DOCS] 7.4 official docs : Fonts?
Message-ID: <20031120135501.A7775@cookie.varlena.com>
Mail-Followup-To: Guillaume LELARGE <gleu@wanadoo.fr>,
	Bruce Momjian <pgman@candle.pha.pa.us>,
	Michael Glaesemann <grzm@myrealbox.com>, pgsql-www@postgresql.org,
	pgsql-docs@postgresql.org
References: <200311201636.hAKGaJw00609@candle.pha.pa.us>
	<200311201914.53031.gleu@wanadoo.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200311201914.53031.gleu@wanadoo.fr>
User-Agent: Mutt/1.3.22.1i
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200311/366
X-Sequence-Number: 3013

It is *much* more important to have legible black and
white text than it is to introduce colors.

Don't run off track with the colors--it would be a bonus
extra.  Also, wrt colors, it is important to choose
colors in a way that handle color blindness.  I had
a great URL on this that I can't find right now,
but the topic is google-able. 

Also, especially since not everyone sees the same
colors, you will *never* agree on syntax colors.
(That is why I inevitably edit my vim syntax files.)

--elein


On Thu, Nov 20, 2003 at 07:14:53PM +0000, Guillaume LELARGE wrote:
> Le Jeudi 20 Novembre 2003 16:36, Bruce Momjian a écrit :
> > Michael Glaesemann wrote:
> > > >> As Peter has pointed out, the CSS can handle a lot of it. It doesn't
> > > >> have to be hardcoded into the SGML-to-HTML transformation. One option
> > > >> would be to use colors as well (I'm not talking a rainbow of fruit
> > > >> flavors here :). In particular, I find italics often difficult to read
> > > >> on the web. I'll try to get a few styles worked up by tomorrow that
> > > >
> > > > I think it is the monospace italics that really look bad.
> > >
> > > I'd have to agree with you. Making them a color other than the text
> > > (black) or the links (blue/purple depending on your eyes) would set
> > > them off quite well. Serif fonts at small sizes can also be pretty
> > > nasty, though this isn't an issue with the PostgreSQL docs.
> >
> > If we go with color, making them printable on a non-color printer
> > becomes a problem.
> This is not totaly true.
> 
> You can have alternate stylesheets depending on the media : on colorized for 
> screen, one black and white for printer. Latest releases of current browers 
> (mozilla, ie6) are able to handle these tags :
>   <link rel="stylesheet" type="text/css" href="2columnspg.css" media="screen"
>     title="TwoColumn">
>   <link rel="stylesheet" type="text/css" href="printpg.css" media="print">
> 
> Adding a title make them available for stylesheet switching in the browser 
> (mozilla).
> 
> 
> -- 
> Guillaume
>   <!-- http://absfr.tuxfamily.org/
>        http://pgsql-fr.tuxfamily.org/ -->.
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match