From: Bruce Momjian <bruce@momjian.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: Consistent reference to RFCs in the documentation
Date: Wed, 2 Dec 2020 14:21:42 -0500
Message-ID: <20201202192142.GA20285@momjian.us> (raw)
In-Reply-To: <a06ea0f1-8aa0-3cee-0587-f895387cda12@iki.fi>
References: <2C697878-4D01-4F06-8312-2FEDE931E973@yesql.se>
<a06ea0f1-8aa0-3cee-0587-f895387cda12@iki.fi>
On Tue, Dec 1, 2020 at 02:39:04PM +0200, Heikki Linnakangas wrote:
> On 05/11/2020 17:09, Daniel Gustafsson wrote:
> > When referencing RFC's, we have a mix of ulinking to the ietf.org entry and
> > not. Also, for subsequent mentions of the same RFC on the same page we have
> > some as <acronym> while others are not.
>
> I'm not sure how sensible the <acronym> tag is for these. I mean, yeah, it's
> an acronym, but it wouldn't make sense to write it open. It doesn't seem to
> affect the formatting in the HTML docs, at least I don't see any difference
> in my browser. But let's be consistent.
Ideally acronyms would use smallcaps, but I don't think we have that
configured in our style sheets.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, hlinnaka@iki.fi, daniel@yesql.se, pgsql-docs@lists.postgresql.org
Subject: Re: Consistent reference to RFCs in the documentation
In-Reply-To: <20201202192142.GA20285@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox