| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Vladimir Rusinov <vrusinov(at)google(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Remove trailing whitespaces from documentation |
| Date: | 2016-12-14 22:17:06 |
| Message-ID: | 20161214221706.ph2fdu5qhmruzghg@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Thinking about this, I'm wondering what is the connection between
> what psql does and what should be in the SGML (or XML) docs, anyway.
> Nobody says boo when we have to do s/</</g to an example in order
> to put it in the docs; why is stripping trailing whitespace a bigger
> issue?
Why do we need to put regular psql output verbatim in SGML/XML? One
idea is to add an output format to psql for docbook table markup, then
use that whenever we need to paste stuff into the docs.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-12-14 22:21:09 | Re: [PATCH] Remove trailing whitespaces from documentation |
| Previous Message | Stephen Frost | 2016-12-14 22:12:43 | Re: [PATCH] Remove trailing whitespaces from documentation |