From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | pgsql-www(at)lists(dot)postgresql(dot)org |
Subject: | Re: Website patch request: documentation style update |
Date: | 2020-04-18 20:21:50 |
Message-ID: | 13726.1587241310@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
"Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
> On 4/18/20 3:34 PM, Tom Lane wrote:
>> Also, now that I look at it, I see the website style seems to be rendering
>> parents and brackets in the same font as the <code> items anyway. This
>> does not seem like an improvement over what happens without that.
> So, it seems like it's the same font, but it's a trompe-l'oeil: it is
> the default font of the site (Open Sans). However, it appears the
> old-style docs use a different browser/OS dependent font in "verdana".
> When I force it to verdana, we get the attached (enum_first has verdana,
> enum_list has Open Sans). This seems to get the desired effect on the
> function definition line, but it sets the descriptions to be verdana,
> which seems to clash with the rest of the site.
Hm. Let's just leave that alone for now. I agree that rendering these
in a subtly different font would be a bit weird.
Did you determine whether we're actually forcing a smaller font in
these tables?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Eldhose M Joy | 2020-04-20 18:47:14 | Addition of support for base path in pgAdmin Web |
Previous Message | Jonathan S. Katz | 2020-04-18 20:12:00 | Re: Website patch request: documentation style update |