From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, alvherre(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: 9.5 release notes |
Date: | 2015-06-14 15:21:35 |
Message-ID: | 9154.1434295295@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> OK, new idea. What about, instead of having the last name be all-caps,
> we have the last name start with an uppercase letter, then use smallcaps
> for the rest of the last name:
> https://en.wikipedia.org/wiki/Small_caps
> That way, the last name will not appear too large, but will be clear as
> something different from other names. Peter, I assume small-caps is
> possible.
FWIW, I vote strongly against having any contributor names in caps in the
release notes. It would be visually distracting, and it would make the
name look like the most important thing in the entry, while in point of
fact it's the *least* important. (Maybe not to the contributor, but
certainly to anybody else.)
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-06-14 15:22:49 | Re: On columnar storage |
Previous Message | Tom Lane | 2015-06-14 15:13:21 | Re: Problem with CREATE TABLE ... (LIKE ... INCLUDING INDEXES) |