| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>, Asko Oja <ascoja(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal: new border setting in psql |
| Date: | 2008-08-29 04:20:44 |
| Message-ID: | 26826.1219983644@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> On Sat, 23 Aug 2008, Andrew Dunstan wrote:
>> I think we should probably confine ourselves to output formats that are in
>> very wide use or we'll be supporting a vast multitude. CSV and XML both
>> qualify here - not sure that ReST does.
> ReST is accepted by Trac, one of the more popular SCM+Project Management
> tools available. And the Python Docutils package is pretty popular too,
> with a growing infrastructure of packages springing up around it. For
> example, it's trivial to take the ReST document, feed it through Sphinx
> (the tool used to generate the Python documentation nowadays:
> http://sphinx.pocoo.org/ ) , and turn the result into HTML, LaTeX, or PDF
> files.
You're ignoring the fact that D'Arcy's patch doesn't output valid ReST.
It outputs something that might pass for ReST, but only so long as there
are no special characters in the data.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2008-08-29 05:01:11 | Re: Proposal: new border setting in psql |
| Previous Message | Greg Smith | 2008-08-29 03:18:06 | Re: Proposal: new border setting in psql |