Re: [DOCS] xsltproc very slow

2003-11-24 Thread Sean Chittenden
> I've just tried out how xsltproc (1.0.8) performs compared to > openjade (1.3.1). I'm not impressed. While openjade is already > notoriously slow, 12 minutes for a full documentation build on my > system, with xsltproc it took 55 minutes. Can anyone try it out on > his system to see whether ot

Re: [DOCS] DocBook V4.2, on the way to XML

2003-11-24 Thread Peter Eisentraut
Halley Pacheco de Oliveira writes: > Please tell me from where I can download this upgraded > documentation so I can try by myself. It's in the CVS repository, but there is nothing exciting in there that's worth trying out. -- Peter Eisentraut [EMAIL PROTECTED] ---(e

Re: [DOCS] DocBook V4.2, on the way to XML

2003-11-24 Thread Halley Pacheco de Oliveira
Dear Peter, Please tell me from where I can download this upgraded documentation so I can try by myself. Thanks, Halley > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > I've upgraded our documentation to DocBook V4.2 > SGML. ___

[DOCS] xsltproc very slow

2003-11-24 Thread Peter Eisentraut
I've just tried out how xsltproc (1.0.8) performs compared to openjade (1.3.1). I'm not impressed. While openjade is already notoriously slow, 12 minutes for a full documentation build on my system, with xsltproc it took 55 minutes. Can anyone try it out on his system to see whether other versio

Re: [DOCS] DocBook V4.2, on the way to XML

2003-11-24 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > I've upgraded our documentation to DocBook V4.2 SGML. The developer docs build seems busted ... http://developer.postgresql.org/docs/postgres/buildlog.html regards, tom lane ---(end of broadcast)--

[DOCS] DocBook V4.2, on the way to XML

2003-11-24 Thread Peter Eisentraut
I've upgraded our documentation to DocBook V4.2 SGML. I was able to install 4.2 by going to http://www.docbook.org/sgml/4.2/, unzipping the file in a suitable place and adding the docbook.cat file to the environment variable SGML_CATALOG_FILES. Packages are also available for several operating sy

Re: [pgsql-www] [DOCS] 7.4 official docs : Fonts?

2003-11-24 Thread Dave Page
> -Original Message- > From: Josh Berkus [mailto:[EMAIL PROTECTED] > Sent: 20 November 2003 17:49 > To: Roberto Mello; Bruce Momjian > Cc: Michael Glaesemann; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: Re: [pgsql-www] [DOCS] 7.4 official docs : Fonts? > > Yeah. In Kate (with t

[DOCS] error in plpgsql-statements.html#PLPGSQL-SELECT-INTO

2003-11-24 Thread Marcos Truchado
Hi. I have just learned how to create my own triggers on plpgsql language, and I think I have discover an error into the doc: http://www.postgresql.org/docs/current/static/plpgsql-statements.html#PLPGSQL-SELECT-INTO DECLARE users_rec RECORD; full_name varchar; BEGIN SELECT INT

Re: [DOCS] 7.4 official docs : Fonts?

2003-11-24 Thread Randolf Richardson, DevNet SysOp 29
[sNip] >> http://www.postgresql.org/docs/current/static/functions-string.html [sNip] > Whatever we had in 7.3 we should switch back to: > > http://www.postgresql.org/docs/7.3/static/functions-string.html I think the fancy fonts should be abandonded altogether in favour of using the web b

Re: [pgsql-www] [DOCS] 7.4 official docs : Fonts?

2003-11-24 Thread elein
It is *much* more important to have legible black and white text than it is to introduce colors. Don't run off track with the colors--it would be a bonus extra. Also, wrt colors, it is important to choose colors in a way that handle color blindness. I had a great URL on this that I can't find ri

[DOCS] error in plpgsql-statements.html#PLPGSQL-SELECT-INTO

2003-11-24 Thread Marcos Truchado
Hi. I have just learned how to create my own triggers on plpgsql language, and I think I have discover an error into the doc: http://www.postgresql.org/docs/current/static/plpgsql-statements.html#PLPGSQL-SELECT-INTO DECLARE

[DOCS] PostgreSQL 7.4 Documentation - create_sequence.sgml

2003-11-24 Thread Halley Pacheco de Oliveira
In the create_sequence.sgml is written: The optional clause INCREMENT BY increment specified, which value is added to the current sequence value to create a new value. I think it is wrong and could be: The optional clause INCREMENT BY increment specifies the value to be added to the current sequ