On 11/08/2012 11:55:19 AM, Karl O. Pinc wrote:
On 11/08/2012 11:10:39 AM, Robert Haas wrote:
Ah, well, as to that, I think you'd have to take that suggestion to
pgsql-www. The style sheets used for the web site are - just to
make
things exciting - stored in a completely different source
On Tue, Nov 6, 2012 at 5:44 PM, Karl O. Pinc k...@meme.com wrote:
In your generated output I see:
tr
td colspan=2span class=bold EMPHASIS c3Class 00 —
Successful Completion/span/td
/tr
It's just matter of CSS rule like
td .EMPHASIS { font-size: 140%; }
to
On 11/08/2012 11:10:39 AM, Robert Haas wrote:
On Tue, Nov 6, 2012 at 5:44 PM, Karl O. Pinc k...@meme.com wrote:
In your generated output I see:
tr
td colspan=2span class=bold EMPHASIS c3Class 00 —
Successful Completion/span/td
/tr
It's just matter of
On 11/6/12 12:09 PM, Karl O. Pinc wrote:
--snip
On 11/06/2012 10:41:04 AM, Stefan Seefeld wrote:
On 11/06/2012 11:27 AM, Karl O. Pinc wrote:
Hi,
I'm trying to improve a table of PostgreSQL error codes
in the PostgreSQL docs.
On 11/05/2012 09:41:13 PM, Karl O. Pinc wrote:
The attached patch, errorcode_table_v2.patch, is an attempt to
do it the right way.
Since I'm stuck I asked about this patch on the docbook-apps
mailing list.
https://lists.oasis-open.org/archives/docbook-apps/201211/msg00027.html
I got the
On 11/06/2012 12:09 PM, Karl O. Pinc wrote:
Postgresql uses Docbook 4.2 and openjade/dsssl style sheets.
Is there even a remote chance for you to migrate to XSL stylesheets ?
I'm not sure the DSSL ones are maintained at all at this point, so
improvements, fixes, and customizations are much
Note: This email is not immediately relevant to Postgres,
although someday it may be.
On 11/06/2012 11:38:07 AM, Andrew Dunstan wrote:
On 11/06/2012 12:09 PM, Karl O. Pinc wrote:
Postgresql uses Docbook 4.2 and openjade/dsssl style sheets.
I don't recall what the arguments against moving
On Mon, Nov 5, 2012 at 10:41 PM, Karl O. Pinc k...@meme.com wrote:
So at this point I'm out of ideas. Unless somebody
can chime in with a clue I'm ready to give up.
Frankly, I don't view this as enough of a problem to be worth spending
time on. Actually, I'm not sure I view the formatting of
On 11/06/2012 01:40:56 PM, Robert Haas wrote:
On Mon, Nov 5, 2012 at 10:41 PM, Karl O. Pinc k...@meme.com wrote:
So at this point I'm out of ideas. Unless somebody
can chime in with a clue I'm ready to give up.
Frankly, I don't view this as enough of a problem to be worth
spending
time
On 11/06/2012 01:40:56 PM, Robert Haas wrote:
Frankly, I don't view this as enough of a problem to be worth
spending
time on. Actually, I'm not sure I view the formatting of that table
as a problem at all, but if it is a problem it's not a big enough one
to justify knocking ourselves out
On Fri, Oct 26, 2012 at 10:03 AM, Karl O. Pinc k...@meme.com wrote:
This patch adds an empty row before each section header
in the error codes table in the docs.
I tried not putting an empty row before the first
section, but it looks better to always have
an empty row. IMO.
File:
Robert Haas robertmh...@gmail.com writes:
On Fri, Oct 26, 2012 at 10:03 AM, Karl O. Pinc k...@meme.com wrote:
This patch adds an empty row before each section header
in the error codes table in the docs.
This doesn't seem like a particularly good idea to me, but what do
other people think?
On Mon, Nov 5, 2012 at 3:40 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Oct 26, 2012 at 10:03 AM, Karl O. Pinc k...@meme.com wrote:
This patch adds an empty row before each section header
in the error codes table in the docs.
This doesn't seem
On 11/05/2012 02:40:12 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Oct 26, 2012 at 10:03 AM, Karl O. Pinc k...@meme.com
wrote:
This patch adds an empty row before each section header
in the error codes table in the docs.
This doesn't seem like a particularly
14 matches
Mail list logo
