Re: House style for DocBook documentation?
Chapman Flack <chap@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>,
Markus Winand <markus.winand@winand.at>, Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-01-19T20:24:22Z
Lists: pgsql-hackers
Hi, On 01/19/19 08:35, Alvaro Herrera wrote: >> Is there, somewhere, a written-up "house style" for what DocBook 4.2 >> elements to use for which types of content in the manual? >> ... > I don't think we do. I'd suggest to come up with something and then see > if it makes sense to patch the docs to apply it regularly. I think my ambition at the moment is just to complete a particular addition to func.sgml and do so as consistently as I can manage with what's there now. I have noticed a couple of things: - 'SQL' is often marked up as <acronym>SQL</acronym>, but far from always. - no such markup is applied to 'JSON' or 'XML' at all, at least not in func.sgml. - there is a README.links with this guideline: o Do not use text with <ulink> so the URL appears in printed output but a grep -r in doc/src/sgml turns up 112 uses that observe the guideline, and 147 that supply link text. (thinks to self half-seriously about an XSL transform for generating printed output that could preserve link-texted links, add raised numbers, and produce a numbered URLs section at the back) -Chap
Commits
-
Improve documentation about our XML functionality
- 728c49779ba8 11.6 landed
- 603a28b44973 10.11 landed
-
Improve documentation about our XML functionality.
- 12d46ac392d0 12.0 landed
-
Add volatile qualifier missed in commit 2e616dee9.
- b2b819019f44 12.0 landed
-
Fix crash with old libxml2
- 2e616dee9e60 12.0 landed
-
Fix minor deficiencies in XMLTABLE, xpath(), xmlexists()
- 251cf2e27bec 12.0 cited
-
Fix the BY {REF,VALUE} clause of XMLEXISTS/XMLTABLE
- eaaa5986ad03 12.0 landed
-
doc: Update README.links
- b060e6c1f5b4 12.0 landed
-
XPath fixes:
- 3963574d1338 8.3.0 cited