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-21T16:46:05Z
Lists: pgsql-hackers
On 01/21/19 09:12, Alvaro Herrera wrote: >> (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) > > Well, if you have the time and inclination, and you think such changes > are improvements, feel free to propose them. Do keep in mind we have a > number of outputs that would be good to keep consistent. Well, "consistent" what I was half-thinking about, FSVO "consistent". For me, if I'm looking at an online document, I would prefer to see the descriptive text of the link, rather than a long jaggy URL. If I want to see the URL, I can hover over it, and if I want to go there, I can click it. But the point's well taken that in /printed output/, that's of no use. Which is, in a sense, an inconsistency: in one format, you can follow the links, while in another, you're out of luck. Maybe a simpler transform for printed output, rather than collecting all URLs into one section at the back, would just be to follow any <ulink> that has link text with a <footnote> containing the same ulink without the link text, so it shows the URL, and that would be right at the bottom of the same 'page'. That'd be an introductory XSL exercise.... In practice, applying such a transform "for printed output" would probably mean applying it when generating PDF output, which of course can also be viewed online (and probably most often is, these days). So preserving the original ulink run into the text is still of use, in a PDF viewer that can follow links, but adding the footnote ensures that an actual hard copy is still usable. I wouldn't think it important to apply the same treatment when making HTML. So maybe the right value of "consistent" is the one that comes from listing out the various output formats and specifying the right transformation to be applied to each one. (Now wonders if there's a way to do the same transform into HTML while styling the footnote and marker to hide behind @media print....) Regards, -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