Re: Consistent reference to RFCs in the documentation

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Daniel Gustafsson <daniel@yesql.se>, Pg Docs <pgsql-docs@lists.postgresql.org>
Date: 2020-12-02T19:21:42Z
Lists: pgsql-docs
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




Commits

  1. docs: ulink all references to RFC's