| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Markus Winand <markus(dot)winand(at)winand(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: House style for DocBook documentation? |
| Date: | 2019-01-25 14:37:35 |
| Message-ID: | 5C4B1F2F.2000106@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/25/19 09:01, Peter Eisentraut wrote:
> On 19/01/2019 21:24, Chapman Flack 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)
>
> External links already create footnotes in the PDF output. Is that
> different from what you are saying?
That might, only, indicate that I was just thinking aloud in email and
had not gone and checked in PDF output to see how the links were handled.
Yes, it could very possibly indicate that.
If they are already processed that way, does that mean the
o Do not use text with <ulink> so the URL appears in printed output
in README.links should be considered obsolete, and removed even, and
doc authors should feel free to put link text in <ulink> without
hesitation?
Regards,
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-01-25 15:19:21 | Re: using expression syntax for partition bounds |
| Previous Message | Heikki Linnakangas | 2019-01-25 14:33:54 | Re: Speeding up text_position_next with multibyte encodings |