Обсуждение: PDF 7.4?
Hey, Any reason why we don't have PDF's of the 7.4 manual set? Sincerely, Joshua D. Drake -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Joshua D. Drake wrote: > Hey, > > Any reason why we don't have PDF's of the 7.4 manual set? Yes, our SGML builds for PDF fail and we don't know why. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
On Mon, 22 Dec 2003, Bruce Momjian wrote: > Joshua D. Drake wrote: > > Hey, > > > > Any reason why we don't have PDF's of the 7.4 manual set? > > Yes, our SGML builds for PDF fail and we don't know why. Is there something missing on the VM that needs to be installed? First I've heard of this, is there something that I can run to generate the error, and test? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Marc G. Fournier wrote: > On Mon, 22 Dec 2003, Bruce Momjian wrote: > > > Joshua D. Drake wrote: > > > Hey, > > > > > > Any reason why we don't have PDF's of the 7.4 manual set? > > > > Yes, our SGML builds for PDF fail and we don't know why. > > Is there something missing on the VM that needs to be installed? First > I've heard of this, is there something that I can run to generate the > error, and test? No, the openjade toolset itself dump core so it is an openjade application problem. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
On Mon, 22 Dec 2003, Bruce Momjian wrote: > Marc G. Fournier wrote: > > On Mon, 22 Dec 2003, Bruce Momjian wrote: > > > > > Joshua D. Drake wrote: > > > > Hey, > > > > > > > > Any reason why we don't have PDF's of the 7.4 manual set? > > > > > > Yes, our SGML builds for PDF fail and we don't know why. > > > > Is there something missing on the VM that needs to be installed? First > > I've heard of this, is there something that I can run to generate the > > error, and test? > > No, the openjade toolset itself dump core so it is an openjade > application problem. 'k, a *very* quick scan of google, openjade uses the docbook for doing the PDF stuff? Is there a problem with the version that is in use? that VM has the following docbook packages installed: t1# ls -ld docbook-* drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-1.2_1 drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-241_2 drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-3.0_2 drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-3.1_2 drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-4.0_2 drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-4.1_2 maybe openjade is using the wrong version? Since, as far as I know, its *supposed* to work, if I can get a command to run to test with, I can hit the port maintainer to see if maybe I have something installed wrong? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Marc G. Fournier wrote: > > No, the openjade toolset itself dump core so it is an openjade > > application problem. > > 'k, a *very* quick scan of google, openjade uses the docbook for doing the > PDF stuff? Is there a problem with the version that is in use? that VM > has the following docbook packages installed: > > t1# ls -ld docbook-* > drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-1.2_1 > drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-241_2 > drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-3.0_2 > drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-3.1_2 > drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-4.0_2 > drwxr-xr-x 2 root wheel 512 Oct 15 14:50 docbook-4.1_2 > > maybe openjade is using the wrong version? > > Since, as far as I know, its *supposed* to work, if I can get a command to > run to test with, I can hit the port maintainer to see if maybe I have > something installed wrong? I have a fresh install of docbook 4.2 on my machine and it loops, and for Peter is core dumps, and no one else has gotten it working either. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>Yes, our SGML builds for PDF fail and we don't know why. > > > Hmm o.k. I will take a look at it. Any reason why we haven't moved to Docbook XML? J -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Joshua D. Drake wrote: > > >Yes, our SGML builds for PDF fail and we don't know why. > > > > > > > Hmm o.k. I will take a look at it. Any reason why we haven't moved > to Docbook XML? Peter know, I don't. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Joshua D. Drake wrote: > > >Yes, our SGML builds for PDF fail and we don't know why. > > > > > > > Hmm o.k. I will take a look at it. Any reason why we haven't moved > to Docbook XML? Peter knows, I don't. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>I have a fresh install of docbook 4.2 on my machine and it loops, and >for Peter is core dumps, and no one else has gotten it working either. > > > It loops for me as well... on the section about the date data types. J -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
On Mon, 22 Dec 2003, Joshua D. Drake wrote: > > >I have a fresh install of docbook 4.2 on my machine and it loops, and > >for Peter is core dumps, and no one else has gotten it working either. > > > > > > > > It loops for me as well... on the section about the date data types. so the problem is in the sgml itself, and not the tools... ? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
>so the problem is in the sgml itself, and not the tools... ? > > > Well, I have yet to get that far but I am running SuSe 8.2 and Fedora. I can duplicate the problem on both. I would suspect that something in the SGML is causing it to loop on itself. It may be a bug with openjade that is rearing its head because of something we are doing in the docs. I am going to dig a little more and see if I can find the exact problem. Sincerely, Joshua Drake >---- >Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) >Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > > -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
On Mon, 22 Dec 2003, Joshua D. Drake wrote:
>
> >so the problem is in the sgml itself, and not the tools... ?
> >
> >
> >
>
> Well, I have yet to get that far but I am running SuSe 8.2 and Fedora. I
> can duplicate
> the problem on both.
>
> I would suspect that something in the SGML is causing it to loop on
> itself. It may be
> a bug with openjade that is rearing its head because of something we are
> doing in
> the docs.
>
> I am going to dig a little more and see if I can find the exact problem.
'k, on the dev server, I get a whack of errors before it exits:
LaTeX Warning: Reference `26529' on page xxix undefined on input line 33613.
LaTeX Warning: Reference `26550' on page xxix undefined on input line 33643.
LaTeX Warning: Reference `26613' on page xxix undefined on input line 33673.
LaTeX Warning: Reference `26821' on page xxix undefined on input line 33703.
! TeX capacity exceeded, sorry [save size=5000].
\setnormal ...ing \let \fPosture \pageFontPosture
\let \fProportionateWidth ...
l.33711 {start}}
\Link%
! ==> Fatal error occurred, the output PDF file is not finished!
Transcript written on postgres.log.
gmake: *** [postgres.pdf] Error 1
gmake: *** Deleting file `postgres.pdf'
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Joshua D. Drake wrote:
>
> >so the problem is in the sgml itself, and not the tools... ?
> >
> >
> >
>
> Well, I have yet to get that far but I am running SuSe 8.2 and Fedora. I
> can duplicate
> the problem on both.
>
> I would suspect that something in the SGML is causing it to loop on
> itself. It may be
> a bug with openjade that is rearing its head because of something we are
> doing in
> the docs.
>
> I am going to dig a little more and see if I can find the exact problem.
I have it running on a dual Xeon 2.4G machine and the build is still
running after 2.5 hours. The strange thing is that the postgres.tex-pdf
file is growing by about 1mb per hour, and the contents show that it is
putting new information into the file that is unique (doesn't appear
earlier in the file), so it is doing something, just very slowly.
The most recent text I have in the file is:
Constructs an argument that consists of an array of bytes
which is from jdbc.sgml. I wonder if there is some non-linear behavior
for very large builds. I just phoned Tom and he suggested that idea,
and I was wondering that myself.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
>! TeX capacity exceeded, sorry [save size=5000]. >\setnormal ...ing \let \fPosture \pageFontPosture > > The above error I have seen before... when we were writing Practical PostgreSQL. It has been a long time but I just found this on google: http://www.tug.org/pipermail/texhax/2003-September/000928.html It may or may not fix the problem you are having. J > \let \fProportionateWidth ... >l.33711 {start}} > \Link% >! ==> Fatal error occurred, the output PDF file is not finished! >Transcript written on postgres.log. >gmake: *** [postgres.pdf] Error 1 >gmake: *** Deleting file `postgres.pdf' > > >---- >Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) >Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > > -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
>The most recent text I have in the file is: > > Constructs an argument that consists of an array of bytes > >which is from jdbc.sgml. I wonder if there is some non-linear behavior >for very large builds. I just phoned Tom and he suggested that idea, >and I was wondering that myself. > > > My file got to 150 megs before I killed it... I was watching and I got a lot of duplication. If I run in debug mode I get a lot of missing files: [root@srv1 sgml]# openjade -g -D . -c /usr/share/sgml/docbook/dsssl-stylesheets/catalog -d stylesheet.dsl -i output-html -t tex postgres.sgml openjade:problems.sgml:237:37:W: cannot generate system identifier for general entity "version" openjade:problems.sgml:237:37: open elements: BOOK PREFACE[1] SECT1[1] SECT2[1] PARA[1] ITEMIZEDLIST[1] LISTITEM[1] PARA[1] (#PCDATA[1]) openjade:problems.sgml:237:37:E: general entity "version" not defined and no default entity openjade:problems.sgml:237:37: open elements: BOOK PREFACE[1] SECT1[1] SECT2[1] PARA[1] ITEMIZEDLIST[1] LISTITEM[1] PARA[1] (#PCDATA[1]) openjade:problems.sgml:237:44:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:problems.sgml:237:44: open elements: BOOK PREFACE[1] SECT1[1] SECT2[1] PARA[1] ITEMIZEDLIST[1] LISTITEM[1] PARA[1] (#PCDATA[1]) openjade:start.sgml:320:24:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:start.sgml:320:24: open elements: BOOK PART[1] CHAPTER[1] SECT1[2] PARA[1] SCREEN[1] (#PCDATA[1]) openjade:start.sgml:360:20:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:start.sgml:360:20: open elements: BOOK PART[1] CHAPTER[1] SECT1[2] PARA[1] SCREEN[1] (#PCDATA[1]) openjade:installation.sgml:334:42:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:installation.sgml:334:42: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] (#PCDATA[1]) openjade:installation.sgml:336:53:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:installation.sgml:336:53: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] (#PCDATA[1]) openjade:installation.sgml:336:74:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:installation.sgml:336:74: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] (#PCDATA[1]) openjade:installation.sgml:339:37:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:installation.sgml:339:37: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] SCREEN[1] USERINPUT[1] (#PCDATA[1]) openjade:installation.sgml:340:37:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:installation.sgml:340:37: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] SCREEN[1] USERINPUT[1] (#PCDATA[1]) openjade:installation.sgml:343:32:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:installation.sgml:343:32: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] FILENAME[1] (#PCDATA[1]) openjade:installation.sgml:362:11:W: cannot generate system identifier for general entity "majorversion" openjade:installation.sgml:362:11: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] QUOTE[1] openjade:installation.sgml:362:11:E: general entity "majorversion" not defined and no default entity openjade:installation.sgml:362:11: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] QUOTE[1] openjade:installation.sgml:362:23:E: reference to entity "majorversion" for which no system identifier could be generated openjade:installation.sgml:362:10: entity was defined here openjade:installation.sgml:362:23: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] QUOTE[1] openjade:installation.sgml:409:64:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:installation.sgml:409:64: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PROCEDURE[1] STEP[1] PARA[1] (#PCDATA[1])openjade:installation.sgml:460:63:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:installation.sgml:460:63: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] (#PCDATA[1]) openjade:installation.sgml:1728:64:E: reference to entity "majorversion" for which no system identifier could be generated openjade:installation.sgml:362:10: entity was defined here openjade:installation.sgml:1728:64: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] FORMALPARA[1] PARA[1] (#PCDATA[1]) openjade:backup.sgml:442:24:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:backup.sgml:442:24: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] PROGRAMLISTING[1] (#PCDATA[1]) openjade:jdbc.sgml:88:53:E: reference to entity "majorversion" for which no system identifier could be generated openjade:installation.sgml:362:10: entity was defined here openjade:jdbc.sgml:88:53: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] SECT2[1] PARA[1] FILENAME[1] (#PCDATA[1]) openjade:jdbc.sgml:89:29:E: reference to entity "majorversion" for which no system identifier could be generated openjade:installation.sgml:362:10: entity was defined here openjade:jdbc.sgml:89:29: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] SECT2[1] PARA[1] FILENAME[1] (#PCDATA[1]) openjade:jdbc.sgml:90:29:E: reference to entity "majorversion" for which no system identifier could be generated openjade:installation.sgml:362:10: entity was defined here openjade:jdbc.sgml:90:29: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] SECT2[1] PARA[1] FILENAME[1] (#PCDATA[1]) openjade:xoper.sgml:99:34:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:xoper.sgml:99:34: open elements: BOOK PART[1] CHAPTER[1] SECT1[1] PARA[1] (#PCDATA[1]) openjade:ref/psql-ref.sgml:523:24:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:ref/psql-ref.sgml:523:24: open elements: BOOK PART[1] REFERENCE[1] REFENTRY[1] REFSECT1[1] REFSECT2[2] PARA[1] PROGRAMLISTING[1] (#PCDATA[1]) openjade:errcodes.sgml:31:48:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:errcodes.sgml:31:48: open elements: BOOK PART[1] APPENDIX[1] PARA[1] (#PCDATA[1]) openjade:keywords.sgml:14:10:E: reference to entity "version" for which no system identifier could be generated openjade:problems.sgml:237:36: entity was defined here openjade:keywords.sgml:14:10: open elements: BOOK PART[1] APPENDIX[1] PARA[1] (#PCDATA[1]) openjade:features.sgml:97:6:E: cannot find "features-supported.sgml"; tried "features-supported.sgml", "./features-supported.sgml", "/usr/share/sgml/features-supported.sgml" openjade:features.sgml:97:6: open elements: BOOK PART[1] APPENDIX[1] SECT1[1] PARA[1] INFORMALTABLE[1] TGROUP[1] (THEAD[1]) openjade:features.sgml:99:13:E: end tag for "TGROUP" which is not finished openjade:features.sgml:99:13: open elements: BOOK PART[1] APPENDIX[1] SECT1[1] PARA[1] INFORMALTABLE[1] TGROUP[1] (THEAD[1])openjade:features.sgml:124:6:E: cannot find "features-unsupported.sgml"; tried "features-unsupported.sgml", "./features-unsupported.sgml", "/usr/share/sgml/features-unsupported.sgml" openjade:features.sgml:124:6: open elements: BOOK PART[1] APPENDIX[1] SECT1[1] PARA[1] INFORMALTABLE[1] TGROUP[1] (THEAD[1])openjade:features.sgml:126:13:E: end tag for "TGROUP" which is not finished openjade:features.sgml:126:13: open elements: BOOK PART[1] APPENDIX[1] SECT1[1] PARA[1] INFORMALTABLE[1] TGROUP[1] (THEAD[1]) openjade:postgres.sgml:257:1:E: cannot find "bookindex.sgml"; tried "bookindex.sgml", "./bookindex.sgml", "/usr/share/sgml/bookindex.sgml" openjade:postgres.sgml:257:1: open elements: BOOK (BIBLIOGRAPHY[1]) -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Marc G. Fournier wrote: > LaTeX Warning: Reference `26821' on page xxix undefined on input line 33703. > > ! TeX capacity exceeded, sorry [save size=5000]. > \setnormal ...ing \let \fPosture \pageFontPosture The error above looks like a problem where you didn't modify your latex rules in the special way pdflatex requests. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Joshua D. Drake wrote:
>
> >The most recent text I have in the file is:
> >
> > Constructs an argument that consists of an array of bytes
> >
> >which is from jdbc.sgml. I wonder if there is some non-linear behavior
> >for very large builds. I just phoned Tom and he suggested that idea,
> >and I was wondering that myself.
> >
> >
> >
>
> My file got to 150 megs before I killed it... I was watching and I got a
> lot of duplication.
> If I run in debug mode I get a lot of missing files:
My file is only 7mb, and there are no messages at all:
#$ gmake postgres.pdf
openjade -V draft-mode -D . -c
/usr/local/share/sgml/docbook-dsssl/catalog -d stylesheet.dsl -t tex -V
tex-backend -i output-print -V texpdf-output -o postgres.tex-pdf postgres.sgml
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
On Mon, 22 Dec 2003, Joshua D. Drake wrote: > > >! TeX capacity exceeded, sorry [save size=5000]. > >\setnormal ...ing \let \fPosture \pageFontPosture > > > > > The above error I have seen before... when we were writing Practical > PostgreSQL. It has been a long > time but I just found this on google: > > http://www.tug.org/pipermail/texhax/2003-September/000928.html > > It may or may not fix the problem you are having. So the other errors are all benign? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
>My file is only 7mb, and there are no messages at all:
>
>
Change your openjade line to:
openjade -V draft-mode -g -D . -c
/usr/local/share/sgml/docbook-dsssl/catalog -d stylesheet.dsl -t tex -V
tex-backend -i output-print -V texpdf-output -o postgres.tex-pdf postgres.sgml
You should see errors at that point.
>
> #$ gmake postgres.pdf
> openjade -V draft-mode -D . -c
> /usr/local/share/sgml/docbook-dsssl/catalog -d stylesheet.dsl -t tex -V
> tex-backend -i output-print -V texpdf-output -o postgres.tex-pdf postgres.sgml
>
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
On Mon, 22 Dec 2003, Bruce Momjian wrote: > Marc G. Fournier wrote: > > LaTeX Warning: Reference `26821' on page xxix undefined on input line 33703. > > > > ! TeX capacity exceeded, sorry [save size=5000]. > > \setnormal ...ing \let \fPosture \pageFontPosture > > The error above looks like a problem where you didn't modify your latex > rules in the special way pdflatex requests. I realize ... was more concerned with the slew of errors scrolling up the screen previous to the error :) ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Marc G. Fournier wrote: > On Mon, 22 Dec 2003, Bruce Momjian wrote: > > > Marc G. Fournier wrote: > > > LaTeX Warning: Reference `26821' on page xxix undefined on input line 33703. > > > > > > ! TeX capacity exceeded, sorry [save size=5000]. > > > \setnormal ...ing \let \fPosture \pageFontPosture > > > > The error above looks like a problem where you didn't modify your latex > > rules in the special way pdflatex requests. > > I realize ... was more concerned with the slew of errors scrolling up the > screen previous to the error :) True, though sometimes you get meaningless errors and then the proper error appears. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
On Mon, 22 Dec 2003, Bruce Momjian wrote: > Marc G. Fournier wrote: > > On Mon, 22 Dec 2003, Bruce Momjian wrote: > > > > > Marc G. Fournier wrote: > > > > LaTeX Warning: Reference `26821' on page xxix undefined on input line 33703. > > > > > > > > ! TeX capacity exceeded, sorry [save size=5000]. > > > > \setnormal ...ing \let \fPosture \pageFontPosture > > > > > > The error above looks like a problem where you didn't modify your latex > > > rules in the special way pdflatex requests. > > > > I realize ... was more concerned with the slew of errors scrolling up the > > screen previous to the error :) > > True, though sometimes you get meaningless errors and then the proper > error appears. since you don't seem to generate any of the errors, even after a few hours, and svr1.postgresql.org does within a few minutes, how abot trying to do a 'gmake postgres.pdf' there and see if the errors make sense to you? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Marc G. Fournier wrote: > On Mon, 22 Dec 2003, Bruce Momjian wrote: > > > Marc G. Fournier wrote: > > > On Mon, 22 Dec 2003, Bruce Momjian wrote: > > > > > > > Marc G. Fournier wrote: > > > > > LaTeX Warning: Reference `26821' on page xxix undefined on input line 33703. > > > > > > > > > > ! TeX capacity exceeded, sorry [save size=5000]. > > > > > \setnormal ...ing \let \fPosture \pageFontPosture > > > > > > > > The error above looks like a problem where you didn't modify your latex > > > > rules in the special way pdflatex requests. > > > > > > I realize ... was more concerned with the slew of errors scrolling up the > > > screen previous to the error :) > > > > True, though sometimes you get meaningless errors and then the proper > > error appears. > > since you don't seem to generate any of the errors, even after a few > hours, and svr1.postgresql.org does within a few minutes, how abot trying > to do a 'gmake postgres.pdf' there and see if the errors make sense to > you? OK, testing now. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Marc G. Fournier wrote:
> > > I realize ... was more concerned with the slew of errors scrolling up the
> > > screen previous to the error :)
> >
> > True, though sometimes you get meaningless errors and then the proper
> > error appears.
>
> since you don't seem to generate any of the errors, even after a few
> hours, and svr1.postgresql.org does within a few minutes, how abot trying
> to do a 'gmake postgres.pdf' there and see if the errors make sense to
> you?
This is an error I got:
openjade:postgres.sgml:5:55:W: cannot generate system identifier
for public text "-//OASIS//DTD DocBook V4.2//EN"
You don't have Docbook 4.2 installed or it isn't being found. That is
attempting to build HEAD, not 7.4.X, which uses docbook 3.2, I think.
What I don't understand is why the official developer build can build
HTML.
I just checked out REL 7.4.X and got:
$ gmake postgres.pdf
LC_ALL=C /usr/bin/perl
/usr/local/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -f -g -o
bookindex.sgml -N
{ \
echo "<!entity version \"7.4.1\">"; \
echo "<!entity majorversion \"`expr 7.4.1 :
'\([0-9][0-9]*\.[0-9][0-9]*\)'`\">"; \
} >version.sgml
/usr/bin/perl ./mk_feature_tables.pl YES
../../../src/backend/catalog/sql_feature_packages.txt
../../../src/backend/catalog/sql_features.txt > features-supported.sgml
/usr/bin/perl ./mk_feature_tables.pl NO
../../../src/backend/catalog/sql_feature_packages.txt
../../../src/backend/catalog/sql_features.txt >
features-unsupported.sgml
openjade -D . -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -d
stylesheet.dsl -t tex -V tex-backend -i output-print -V texpdf-output -o
postgres.tex-pdf postgres.sgml
and I see the errors you see. Those look like missing index entries
generated by LaTeX. Usually you have to run latex 3 times to get all
the index entries fixed, but rerunning the gmake doesn't seem to help.
Basically, I think if you fixed the final error, the build would
complete and you could re-run the gmake a few times more to remove the
warnings.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
On Mon, 22 Dec 2003, Bruce Momjian wrote: > openjade:postgres.sgml:5:55:W: cannot generate system identifier > for public text "-//OASIS//DTD DocBook V4.2//EN" > > You don't have Docbook 4.2 installed or it isn't being found. That is > attempting to build HEAD, not 7.4.X, which uses docbook 3.2, I think. > What I don't understand is why the official developer build can build > HTML. Odd, there isn't even a v4.2 port available ... v4.1 is the latest ... do you know, off hand, where the install instructions are found, as I've never done docbook outside of ports ... > and I see the errors you see. Those look like missing index entries > generated by LaTeX. Usually you have to run latex 3 times to get all > the index entries fixed, but rerunning the gmake doesn't seem to help. 'k, and the stupid question here, but ... should you *have* to run it 3 times, or do we have something wrong in the sgml? Note that I know zip about sgml and TeX, so this just may be the norm, but sounds like a logical question to ask :) ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Marc G. Fournier wrote:
> On Mon, 22 Dec 2003, Bruce Momjian wrote:
>
> > openjade:postgres.sgml:5:55:W: cannot generate system identifier
> > for public text "-//OASIS//DTD DocBook V4.2//EN"
> >
> > You don't have Docbook 4.2 installed or it isn't being found. That is
> > attempting to build HEAD, not 7.4.X, which uses docbook 3.2, I think.
> > What I don't understand is why the official developer build can build
> > HTML.
>
> Odd, there isn't even a v4.2 port available ... v4.1 is the latest ... do
> you know, off hand, where the install instructions are found, as I've
> never done docbook outside of ports ...
I used our official SGML tools build docs --- seemed to work.
> > and I see the errors you see. Those look like missing index entries
> > generated by LaTeX. Usually you have to run latex 3 times to get all
> > the index entries fixed, but rerunning the gmake doesn't seem to help.
>
> 'k, and the stupid question here, but ... should you *have* to run it 3
> times, or do we have something wrong in the sgml? Note that I know zip
> about sgml and TeX, so this just may be the norm, but sounds like a
> logical question to ask :)
You have too. See sgml/Makefile:
%.pdf: %.tex-pdf
@rm -f $*.aux $*.log $*.out
pdfjadetex $<
pdfjadetex $<
pdfjadetex $<
Three builds are required because the index has to be built first, then
once you know the number of pages, you can then regenerate the index
with the new index size offset, then the last run I think is for the
table-of-contents.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Here is where you can grab the latest docbook: http://www.docbook.org/sgml/index.html >'k, and the stupid question here, but ... should you *have* to run it 3 >times, or do we have something wrong in the sgml? Note that I know zip >about sgml and TeX, so this just may be the norm, but sounds like a >logical question to ask :) > > > I know to generate the index correctly (at least it use to be this way) you have to run it at least twice because the first time generates the entries and the you use collateindex.pl to actually create it. >---- >Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) >Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > > -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Joshua D. Drake wrote: > Here is where you can grab the latest docbook: > > http://www.docbook.org/sgml/index.html > > > > >'k, and the stupid question here, but ... should you *have* to run it 3 > >times, or do we have something wrong in the sgml? Note that I know zip > >about sgml and TeX, so this just may be the norm, but sounds like a > >logical question to ask :) > > > > > > > I know to generate the index correctly (at least it use to be this way) > you have > to run it at least twice because the first time generates the entries > and the you use > collateindex.pl to actually create it. Right. I think Marc's build is getting much father than mine, and in fact I think I have the pdflatex changes so I will not fail the build. I just wonder what is different about his install. Is it the binary versions? Marc, what is your openjade version? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
> > >Right. I think Marc's build is getting much father than mine, and in >fact I think I have the pdflatex changes so I will not fail the build. >I just wonder what is different about his install. Is it the binary >versions? Marc, what is your openjade version? > > > Well I am running 1.3.2 and I am unable to build it. Still working through it though.. I noticed that I do get errors even when I build the html version though. J -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
On Mon, 22 Dec 2003, Bruce Momjian wrote: > Right. I think Marc's build is getting much father than mine, and in > fact I think I have the pdflatex changes so I will not fail the build. > I just wonder what is different about his install. Is it the binary > versions? Marc, what is your openjade version? svr1# openjade --version openjade:I: "openjade" version "1.3.2" openjade:I: "OpenSP" version "1.5" ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Marc G. Fournier wrote: > On Mon, 22 Dec 2003, Bruce Momjian wrote: > > > Right. I think Marc's build is getting much father than mine, and in > > fact I think I have the pdflatex changes so I will not fail the build. > > I just wonder what is different about his install. Is it the binary > > versions? Marc, what is your openjade version? > > svr1# openjade --version > openjade:I: "openjade" version "1.3.2" > openjade:I: "OpenSP" version "1.5" Those are the exact versions I have. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Hello, The below will produce a PDF. I am still working on things like the index but at least it generates now. jw -f docbook -b tex postgres.sgml jadetex postgres.tex dvipdf postgres.dvi Sincerley, Joshua D. Drake Bruce Momjian wrote: >Marc G. Fournier wrote: > > >>On Mon, 22 Dec 2003, Bruce Momjian wrote: >> >> >> >>>Right. I think Marc's build is getting much father than mine, and in >>>fact I think I have the pdflatex changes so I will not fail the build. >>>I just wonder what is different about his install. Is it the binary >>>versions? Marc, what is your openjade version? >>> >>> >>svr1# openjade --version >>openjade:I: "openjade" version "1.3.2" >>openjade:I: "OpenSP" version "1.5" >> >> > >Those are the exact versions I have. > > > -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Joshua D. Drake wrote: > Hello, > > The below will produce a PDF. I am still working on things like the > index but at least it generates now. > > jw -f docbook -b tex postgres.sgml Great. What is jw? > jadetex postgres.tex > dvipdf postgres.dvi -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Bruce Momjian wrote: >Joshua D. Drake wrote: > > >>Hello, >> >> The below will produce a PDF. I am still working on things like the >>index but at least it generates now. >> >>jw -f docbook -b tex postgres.sgml >> >> > >Great. What is jw? > > jadewrapper . It is part of docbook utils. > > >>jadetex postgres.tex >>dvipdf postgres.dvi >> >> > > > -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Bruce Momjian wrote: >>svr1# openjade --version >>openjade:I: "openjade" version "1.3.2" >>openjade:I: "OpenSP" version "1.5" > > > Those are the exact versions I have. Pardon my joining the discussion so late - are you trying to build this from CVS or the postgresql-docs-7.4.tar.bz2 file? Just in case anyone else out there wants to join the frustration? Thanks Alex
> > Pardon my joining the discussion so late - are you trying to build > this from CVS or the postgresql-docs-7.4.tar.bz2 file? > I am using the stock download. > Just in case anyone else out there wants to join the frustration? > > Thanks > Alex > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if > your > joining column's datatypes do not match -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Joshua D. Drake wrote: > Bruce Momjian wrote: > > >Joshua D. Drake wrote: > > > > > >>Hello, > >> > >> The below will produce a PDF. I am still working on things like the > >>index but at least it generates now. > >> > >>jw -f docbook -b tex postgres.sgml > >> > >> > > > >Great. What is jw? > > > > > > jadewrapper . It is part of docbook utils. I don't have those here. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
On Mon, 22 Dec 2003, Bruce Momjian wrote: > Joshua D. Drake wrote: > > Bruce Momjian wrote: > > > > >Joshua D. Drake wrote: > > > > > > > > >>Hello, > > >> > > >> The below will produce a PDF. I am still working on things like the > > >>index but at least it generates now. > > >> > > >>jw -f docbook -b tex postgres.sgml > > >> > > >> > > > > > >Great. What is jw? > > > > > > > > > > jadewrapper . It is part of docbook utils. > > I don't have those here. Me neither, and I checked through ports and can't seem to find it there either ... Joshua, do you have a URL for it? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
>>jadewrapper . It is part of docbook utils. >> >> > >I don't have those here. > > > Would this be a good time to start the BSD vs Linux war? ;) -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
http://freshmeat.net/projects/docbook-utils/ Marc G. Fournier wrote: >On Mon, 22 Dec 2003, Bruce Momjian wrote: > > > >>Joshua D. Drake wrote: >> >> >>>Bruce Momjian wrote: >>> >>> >>> >>>>Joshua D. Drake wrote: >>>> >>>> >>>> >>>> >>>>>Hello, >>>>> >>>>>The below will produce a PDF. I am still working on things like the >>>>>index but at least it generates now. >>>>> >>>>>jw -f docbook -b tex postgres.sgml >>>>> >>>>> >>>>> >>>>> >>>>Great. What is jw? >>>> >>>> >>>> >>>> >>>jadewrapper . It is part of docbook utils. >>> >>> >>I don't have those here. >> >> > >Me neither, and I checked through ports and can't seem to find it there >either ... Joshua, do you have a URL for it? > >---- >Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) >Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > >---------------------------(end of broadcast)--------------------------- >TIP 8: explain analyze is your friend > > -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
Joshua D. Drake writes: > Hmm o.k. I will take a look at it. Any reason why we haven't moved to > Docbook XML? Search the fine pgsql-docs archives. And take the whole thread there while you're at it.
Hello,
I reviewed the latest Docbook thread... the last email that i see is:
However you don't seem to have responded? So I will ask the question as well... Can you show
and example of the problem? Perhaps if I understand the root of the problem I can help find
a solution around it.
Sincerley,
Joshua D. Drake
Peter Eisentraut wrote:
I reviewed the latest Docbook thread... the last email that i see is:
On Fri, Nov 14, 2003 at 10:32:10AM +0100, Peter Eisentraut wrote: > XML disadvantage: > > - no arbitrary parameter entities I unsure if I understand, can you show some example of this problem? I think there is a lot of XML Docbook docs in a lot of projects and Iwill wonder if in the PostgreSQL docs is something special what disableuse XML instead SGML. > Follow-up to pgsql-docs ( at ) postgresql ( dot ) org please. Hmm.. I must subscribe first :-) Karel
However you don't seem to have responded? So I will ask the question as well... Can you show
and example of the problem? Perhaps if I understand the root of the problem I can help find
a solution around it.
Sincerley,
Joshua D. Drake
Peter Eisentraut wrote:
Joshua D. Drake writes:Hmm o.k. I will take a look at it. Any reason why we haven't moved to Docbook XML?Search the fine pgsql-docs archives. And take the whole thread there while you're at it. ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
-- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
Joshua D. Drake writes: > I reviewed the latest Docbook thread... the last email that i see is: Try this: http://archives.postgresql.org/pgsql-docs/2003-11/msg00049.php and this: http://archives.postgresql.org/pgsql-docs/2003-11/msg00069.php