From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: 9.5 release notes |
Date: | 2015-06-16 19:17:01 |
Message-ID: | 20150616191700.GT133018@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> On Sun, Jun 14, 2015 at 11:21:35AM -0400, Tom Lane wrote:
> > For pretty much the same reason, I'm not in favor of small caps either.
> > Even assuming we can do that consistently (which I bet we can't; we
> > do not have all that much control over how web browsers render HTML),
> > it would be calling attention to itself, which is exactly not the result
> > I think we should be after.
>
> I am sure almost every browser can render smallcaps, even if it doesn't
> have a smallcaps-specific font installed --- same for PDF.
For HTML, smallcaps is a CSS property. The way it works is that you
write in lowercase, and then the browser displays smallcaps. So for the
browsers that don't do it correctly, it would just work fine by
displaying as lower case.
One trouble is how to write the SGML so that the smallcaps bits reach
the generated HTML.
I don't know about PDF.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2015-06-16 21:41:32 | Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
Previous Message | Alvaro Herrera | 2015-06-16 18:58:44 | Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |