Re: .pdf generation error using the "newer" tools

Re: .pdf generation error using the "newer" tools

[Alan W. Irwin]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2757 bytes --]

Sorry for bringing this up again from the recent archives, but I am a newbie
on this list. 

I have exactly the same problem as Bill Brooks, and the suggested fix
doesn't work.

>    Using stylesheet:
>    /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
>    Working on: /home/wbrooks/box/work/foo/helloworld.docbook
>    This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
>    (Fatal format file error; I'm stymied)

Éric Bischoff responded:

TeX classical problem. The default configuration files do not allow
enough resources for docbook.

I believe Eric's response is correct, but his patch to texmf.cnf doesn't
solve the problem since it updates only the jadetex parameters which are
already generous on Redhat 6.2 and not the critical pdfjadetex ones.

On my other box (running Debian potato where I do not have this problem with
pdfjadetex) I have the following jadetex and pdfjadtex parameters.

grep 'jadetex =' texmf.cnf
TEXINPUTS.jadetex = .;$TEXMF/tex/{jadetex,plain,generic,}//
TEXINPUTS.pdfjadetex = .;$TEXMF/{pdftex,tex}/{jadetex,plain,generic,}//
pool_size.jadetex = 500000
pool_size.pdfjadetex = 500000
string_vacancies.jadetex = 45000
string_vacancies.pdfjadetex = 45000
max_strings.jadetex = 58500
max_strings.pdfjadetex = 58500
pool_free.jadetex = 47500
pool_free.pdfjadetex = 47500
nest_size.jadetex = 500
nest_size.pdfjadetex = 500
param_size.jadetex = 1504
param_size.pdfjadetex = 1504
save_size.jadetex = 10000
save_size.pdfjadetex = 10000
stack_size.jadetex = 1503
stack_size.pdfjadetex = 1503
extra_mem_bot.jadetex = 85000
extra_mem_bot.pdfjadetex = 8500
 
On my RH 6.2 box with exactly the same XML Cygnus system as Bill
(where I do have the pdfjadetex
problem) the parameters are

grep 'jadetex =' texmf.cnf
TEXINPUTS.jadetex = .;$TEXMF/tex/{jadetex,plain,generic,}//
TEXINPUTS.pdfjadetex = .;$TEXMF/{pdftex,tex}/{jadetex,plain,generic,}//
hash_extra.jadetex = 25000
pool_size.jadetex = 750000
max_strings.jadetex = 55000
save_size.jadetex = 15000

So all the jadextex parameters that Eric recommended updating are already
quite generous on RH 6.2, but there are no pdfjadetex parameters at all so I
presume that takes the small default which causes the "I am stymied"
problem.

I will now copy the Debian parameters that work for pdfjadetex to texmf.cnf
on my RedHat box, but I don't know how to proceed from there.  Is there some
command I run to reconfigure everything to use the new parameters?

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

Re: .pdf generation error using the "newer" tools

[Alan W. Irwin]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2757 bytes --]

Sorry for bringing this up again from the recent archives, but I am a newbie
on this list. 

I have exactly the same problem as Bill Brooks, and the suggested fix
doesn't work.

>    Using stylesheet:
>    /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
>    Working on: /home/wbrooks/box/work/foo/helloworld.docbook
>    This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
>    (Fatal format file error; I'm stymied)

Éric Bischoff responded:

TeX classical problem. The default configuration files do not allow
enough resources for docbook.

I believe Eric's response is correct, but his patch to texmf.cnf doesn't
solve the problem since it updates only the jadetex parameters which are
already generous on Redhat 6.2 and not the critical pdfjadetex ones.

On my other box (running Debian potato where I do not have this problem with
pdfjadetex) I have the following jadetex and pdfjadtex parameters.

grep 'jadetex =' texmf.cnf
TEXINPUTS.jadetex = .;$TEXMF/tex/{jadetex,plain,generic,}//
TEXINPUTS.pdfjadetex = .;$TEXMF/{pdftex,tex}/{jadetex,plain,generic,}//
pool_size.jadetex = 500000
pool_size.pdfjadetex = 500000
string_vacancies.jadetex = 45000
string_vacancies.pdfjadetex = 45000
max_strings.jadetex = 58500
max_strings.pdfjadetex = 58500
pool_free.jadetex = 47500
pool_free.pdfjadetex = 47500
nest_size.jadetex = 500
nest_size.pdfjadetex = 500
param_size.jadetex = 1504
param_size.pdfjadetex = 1504
save_size.jadetex = 10000
save_size.pdfjadetex = 10000
stack_size.jadetex = 1503
stack_size.pdfjadetex = 1503
extra_mem_bot.jadetex = 85000
extra_mem_bot.pdfjadetex = 8500
 
On my RH 6.2 box with exactly the same XML Cygnus system as Bill
(where I do have the pdfjadetex
problem) the parameters are

grep 'jadetex =' texmf.cnf
TEXINPUTS.jadetex = .;$TEXMF/tex/{jadetex,plain,generic,}//
TEXINPUTS.pdfjadetex = .;$TEXMF/{pdftex,tex}/{jadetex,plain,generic,}//
hash_extra.jadetex = 25000
pool_size.jadetex = 750000
max_strings.jadetex = 55000
save_size.jadetex = 15000

So all the jadextex parameters that Eric recommended updating are already
quite generous on RH 6.2, but there are no pdfjadetex parameters at all so I
presume that takes the small default which causes the "I am stymied"
problem.

I will now copy the Debian parameters that work for pdfjadetex to texmf.cnf
on my RedHat box, but I don't know how to proceed from there.  Is there some
command I run to reconfigure everything to use the new parameters?

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

Re: .pdf generation error using the "newer" tools

[Alan W. Irwin]

To answer my own question, apparently the command to use is fmtutil.  But to
recreate the *.fmt file one needs a *.ini file.  Eric, jadextex.ini and
pdfjadextex.ini are currently not included in the jadetex package.
Apparently, you also require configuration lines in fmtutil.cnf.  On my
Debian system these configuration lines are kept in a special location for
the jadetex package, and the whole special fmtutil.cnf is

# jadefmtutil.cnf: configuration file for fmtutil; jade flavor.
#                  invoke with 'fmtutil -cnffile <file>'
#
# format        engine  pattern-file    arguments
jadetex         tex     language.dat    &latex jadetex.ini
pdfjadetex      pdftex  language.dat    &pdflatex pdfjadetex.ini

Eric, could you please provide this special configuration file and
jadetex.ini and pdfjadetex.ini with the Cygnus jadetex package?  Without it
I don't believe we can change the sizes of anything with the ftmutil
command. (I have tried fmtutil --all, and it redoes every *.fmt file
*except* for jadetex.fmt and pdfjadetex.fmt, and I believe the cause is
these missing files from your jadetex package.

Thanks in advance.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

On Sat, 2 Dec 2000, Alan W. Irwin wrote:

> I will now copy the Debian parameters that work for pdfjadetex to texmf.cnf
> on my RedHat box, but I don't know how to proceed from there.  Is there some
> command I run to reconfigure everything to use the new parameters?
> 
> Alan

Re: .pdf generation error using the "newer" tools

[Alan W. Irwin]

To answer my own question, apparently the command to use is fmtutil.  But to
recreate the *.fmt file one needs a *.ini file.  Eric, jadextex.ini and
pdfjadextex.ini are currently not included in the jadetex package.
Apparently, you also require configuration lines in fmtutil.cnf.  On my
Debian system these configuration lines are kept in a special location for
the jadetex package, and the whole special fmtutil.cnf is

# jadefmtutil.cnf: configuration file for fmtutil; jade flavor.
#                  invoke with 'fmtutil -cnffile <file>'
#
# format        engine  pattern-file    arguments
jadetex         tex     language.dat    &latex jadetex.ini
pdfjadetex      pdftex  language.dat    &pdflatex pdfjadetex.ini

Eric, could you please provide this special configuration file and
jadetex.ini and pdfjadetex.ini with the Cygnus jadetex package?  Without it
I don't believe we can change the sizes of anything with the ftmutil
command. (I have tried fmtutil --all, and it redoes every *.fmt file
*except* for jadetex.fmt and pdfjadetex.fmt, and I believe the cause is
these missing files from your jadetex package.

Thanks in advance.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

On Sat, 2 Dec 2000, Alan W. Irwin wrote:

> I will now copy the Debian parameters that work for pdfjadetex to texmf.cnf
> on my RedHat box, but I don't know how to proceed from there.  Is there some
> command I run to reconfigure everything to use the new parameters?
> 
> Alan

pdfjadetex does not work! (was .pdf generation error using the"newer" tools)

[Alan W. Irwin]

Three pdfjadetex questions/comments, then details of my system.

(1) Has anybody gotten the pdfjadetex command to work with the latest Cygnus docbook?

My 100+ pages of documentation definitely don't work, but to reproduce the
bug in an easy way I use the hello world file from
http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/get-going.html#HELLO-WORLD
with the first 2 lines replaced by

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" [
]>

I created hello_world.tex using

jade -c /etc/sgml/catalog \
-d  /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl \
-t tex /usr/share/sgml/xml.dcl hello_world.xml

To check hello_world.tex is a good file I executed

jadetex hello_world.tex

The dvi file could be displayed with xdvi without problems.

******However, I cannot create a pdf version of this document**********

pdfjadetex hello_world.tex 
This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
(Fatal format file error; I'm stymied)

Note this command works fine on my Debian box with this simple example and
also my 100+ pages of documentation.

(2) Has anybody been able to recreate pdfjadetex.fmt (and jadetex.fmt) with
more resources on a Cygnus-RedHat 6.2 system?  Files are missing in the
jadetex rpm, but even when I replace those files, I cannot recreate
pdfjadetex.fmt or jadetex.fmt.  This is unlikely to be a tetex problem
because I can recreate all *.fmt files *except pdfjadetex.fmt and
jadetex.fmt*.

It has been suggested previously on this list that the "I'm stymied" problem
might be due to lack of resources.  I successfully create extra resources
for pdfjadetex.fmt and jadetex.fmt on my Debian box with the appropriate
pdfjadetex.ini and jadetex.ini files and the appropriate special
configuration file for fmtutil configuration file.  (These are the files
that are missing from the Cygnus jadetex.rpm file).  However, even when I
copy the missing files from my Debian box to the Cygnus RedHat 6.2 box, the
fmtutil command does nothing when the special configuration file is
specified.  The procedure returns after a second or two with no error
messages or any other kind of output.  OTOH, if I execute fmtutil --all
(i.e., using the standard configuration file) on the Cygnus box, all *.fmt
files are recreated with parameters specified in texmf.cnf except for
pdfjadetex.fmt and jadetex.fmt which remain completely unchanged with
the old dates.

(3) I am beginning to feel the pdfjadetex problem might be more fundamental
than lack of resources since hello_world takes up so few resources, and any
attempt to reformat pdfjadetex (and jadetex) with more resources also fails.
So I would be most interested whether anybody can get either (1) or (2) to
work.

****System Details****

(1) Redhat 6.2 box completely updated with latest bug, security, etc., fixes from
the Redhat site.

(2) Vanilla RedHat 6.2 Docbook stripped out.  Here is the list of package files
whose equivalent package was removed.
docbook-3.1-3.noarch.rpm
jade-1.2.1-9.i386.rpm
jadetex-2.7-2.i386.rpm
sgml-common-0.1-7.noarch.rpm
sgml-tools-1.0.9-5.i386.rpm
stylesheets-0.13rh-4.noarch.rpm

(3) Latest Cygnus DocBook installed.

docbook-dtd31-sgml-1.0-6.noarch.rpm
docbook-dtd41-sgml-1.0-6.noarch.rpm
docbook-dtd41-xml-1.0-2.noarch.rpm
docbook-style-dsssl-1.57-2.noarch.rpm
docbook-utils-0.6-1.noarch.rpm
jade-1.2.1-6.i386.rpm
jadetex-2.20-4.noarch.rpm
perl-SGMLSpm-1.03ii-3.noarch.rpm
sgml-common-0.4-1.noarch.rpm

******Background:

I am part of the documentation team for the plplot project
( http://www.plplot.org .), and we successfully build our 100+ pages of
documentation using the Debian DocBook tools.  But those in the group
without access to Debian need to build the documentation on RedHat 6.2, and
I would like to recommend the Cygnus solution to them for this purpose.  So
far it works fairly well except for this pdf generation problem, and I hope
somebody can help to get that straightened out.

Thanks in advance,

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

pdfjadetex does not work! (was .pdf generation error using the"newer" tools)

[Alan W. Irwin]

Three pdfjadetex questions/comments, then details of my system.

(1) Has anybody gotten the pdfjadetex command to work with the latest Cygnus docbook?

My 100+ pages of documentation definitely don't work, but to reproduce the
bug in an easy way I use the hello world file from
http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/get-going.html#HELLO-WORLD
with the first 2 lines replaced by

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" [
]>

I created hello_world.tex using

jade -c /etc/sgml/catalog \
-d  /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl \
-t tex /usr/share/sgml/xml.dcl hello_world.xml

To check hello_world.tex is a good file I executed

jadetex hello_world.tex

The dvi file could be displayed with xdvi without problems.

******However, I cannot create a pdf version of this document**********

pdfjadetex hello_world.tex 
This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
(Fatal format file error; I'm stymied)

Note this command works fine on my Debian box with this simple example and
also my 100+ pages of documentation.

(2) Has anybody been able to recreate pdfjadetex.fmt (and jadetex.fmt) with
more resources on a Cygnus-RedHat 6.2 system?  Files are missing in the
jadetex rpm, but even when I replace those files, I cannot recreate
pdfjadetex.fmt or jadetex.fmt.  This is unlikely to be a tetex problem
because I can recreate all *.fmt files *except pdfjadetex.fmt and
jadetex.fmt*.

It has been suggested previously on this list that the "I'm stymied" problem
might be due to lack of resources.  I successfully create extra resources
for pdfjadetex.fmt and jadetex.fmt on my Debian box with the appropriate
pdfjadetex.ini and jadetex.ini files and the appropriate special
configuration file for fmtutil configuration file.  (These are the files
that are missing from the Cygnus jadetex.rpm file).  However, even when I
copy the missing files from my Debian box to the Cygnus RedHat 6.2 box, the
fmtutil command does nothing when the special configuration file is
specified.  The procedure returns after a second or two with no error
messages or any other kind of output.  OTOH, if I execute fmtutil --all
(i.e., using the standard configuration file) on the Cygnus box, all *.fmt
files are recreated with parameters specified in texmf.cnf except for
pdfjadetex.fmt and jadetex.fmt which remain completely unchanged with
the old dates.

(3) I am beginning to feel the pdfjadetex problem might be more fundamental
than lack of resources since hello_world takes up so few resources, and any
attempt to reformat pdfjadetex (and jadetex) with more resources also fails.
So I would be most interested whether anybody can get either (1) or (2) to
work.

****System Details****

(1) Redhat 6.2 box completely updated with latest bug, security, etc., fixes from
the Redhat site.

(2) Vanilla RedHat 6.2 Docbook stripped out.  Here is the list of package files
whose equivalent package was removed.
docbook-3.1-3.noarch.rpm
jade-1.2.1-9.i386.rpm
jadetex-2.7-2.i386.rpm
sgml-common-0.1-7.noarch.rpm
sgml-tools-1.0.9-5.i386.rpm
stylesheets-0.13rh-4.noarch.rpm

(3) Latest Cygnus DocBook installed.

docbook-dtd31-sgml-1.0-6.noarch.rpm
docbook-dtd41-sgml-1.0-6.noarch.rpm
docbook-dtd41-xml-1.0-2.noarch.rpm
docbook-style-dsssl-1.57-2.noarch.rpm
docbook-utils-0.6-1.noarch.rpm
jade-1.2.1-6.i386.rpm
jadetex-2.20-4.noarch.rpm
perl-SGMLSpm-1.03ii-3.noarch.rpm
sgml-common-0.4-1.noarch.rpm

******Background:

I am part of the documentation team for the plplot project
( http://www.plplot.org .), and we successfully build our 100+ pages of
documentation using the Debian DocBook tools.  But those in the group
without access to Debian need to build the documentation on RedHat 6.2, and
I would like to recommend the Cygnus solution to them for this purpose.  So
far it works fairly well except for this pdf generation problem, and I hope
somebody can help to get that straightened out.

Thanks in advance,

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

jade catalog problems for Cygnus DocBook 4.1 XML

[Alan W. Irwin]

Eric, thanks for that earlier acknowledgment that you have at least seen my
pdfjadetex bug report.  Since you have so much to do I will be patient, and
I will try to help out as much as possible by what I hope are clear bug
reports and examples. While we wait for you to get a chance to sort out
these problems I have found, a subset of our team can build our
documentation on Debian DocBook 4.1 XML instead.  But we are looking forward
to when this will all work properly on Cygnus/RedHat as well.

This current post is a bug report for entities that Cygnus just cannot seem
to find although they are defined within the catalog chain.  I believe these
entity problems are completely independent of the pdfjadetex problem I
reported before. I am only copying that other bug report below so you will
know all the details of my system.  Sorry that I could not actually find a
solution of these entity problems, but here are the symptoms for a simple
example with egrave.

jade -c /etc/sgml/catalog -d
/usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl -t tex
/usr/share/sgml/xml.dcl hello_world.xml
jade:hello_world.xml:6:26:E: general entity "egrave" not defined and no
default entity

The example was identical to that used before to demonstrate the pdfjadetex
problem except that I put an è reference in the title to demonstrate
the problem that results in the above jade error message.  Here are the
first few hello_world.xml lines including the è

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" [
]>
<book>
<bookinfo>
<date>1997-10-11</date>
<title>My first bookl&egrave;t</title>

On Cygnus, I get this error message and the appropriate symbol is missing
from the *.ps output once jadetex and dvips are run.  On Debian I do not get
the above error and the appropriate symbol is in the postscript output.

For egrave, I worked backward through the chain of catalog entries in the
following way:

find /usr/share/sgml -type f | xargs grep egrave
/usr/share/sgml/sgml-iso-entities-8879.1986/ISOlat1.ent:<!ENTITY egrave SDATA "[egrave]"--=small e, grave accent-->

find /usr/share/sgml -type f | xargs grep ISOlat1.ent
/usr/share/sgml/sgml-iso-entities-8879.1986/catalog:PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN" ISOlat1.ent

find /etc/sgml/ -type f | xargs grep sgml-iso-entities-8879.1986/catalog
/etc/sgml/sgml-docbook-3.1.cat:CATALOG /usr/share/sgml/sgml-iso-entities-8879.1986/catalog
/etc/sgml/xml-docbook-4.1.cat:CATALOG /usr/share/sgml/sgml-iso-entities-8879.1986/catalog
/etc/sgml/sgml-docbook-4.1.cat:CATALOG /usr/share/sgml/sgml-iso-entities-8879.1986/catalog

cat /etc/sgml/catalog
CATALOG /etc/sgml/sgml-docbook-3.1.cat
CATALOG /etc/sgml/xml-docbook-4.1.cat
CATALOG /etc/sgml/sgml-docbook-4.1.cat

Perhaps there is some minor typo in this chain of catalogs, but I cannot
spot it so I have no idea why egrave is undefined as far as jade is
concerned.  This is just a wild guess, but perhaps jade cannot handle a
four-level deep catalog chain as above?

To test that wild guess I tried specifying two catalog entries as a
colon-separated list, i.e., 
jade -c \
/etc/sgml/catalog:/usr/share/sgml/sgml-iso-entities-8879.1986/ISOlat1.ent \
[...]

but jade does not allow specifying two separate catalogs as a colon-separated
list this way so that got nowhere.

I have just given you details of the egrave example, but we find similar
undefined problems for nbsp, ndash, and mdash entities on Cygnus that do not
occur on Debian.  Probably the solution for these additional undefined
entitities will be obvious once the egrave problem is solved.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

On Mon, 4 Dec 2000, Alan W. Irwin wrote:

> Three pdfjadetex questions/comments, then details of my system.
> 
> (1) Has anybody gotten the pdfjadetex command to work with the latest Cygnus docbook?
> 
> My 100+ pages of documentation definitely don't work, but to reproduce the
> bug in an easy way I use the hello world file from
> http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/get-going.html#HELLO-WORLD
> with the first 2 lines replaced by
> 
> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" [
> ]>
> 
> I created hello_world.tex using
> 
> jade -c /etc/sgml/catalog \
> -d  /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl \
> -t tex /usr/share/sgml/xml.dcl hello_world.xml
> 
> To check hello_world.tex is a good file I executed
> 
> jadetex hello_world.tex
> 
> The dvi file could be displayed with xdvi without problems.
> 
> ******However, I cannot create a pdf version of this document**********
> 
> pdfjadetex hello_world.tex 
> This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
> (Fatal format file error; I'm stymied)
> 
> Note this command works fine on my Debian box with this simple example and
> also my 100+ pages of documentation.
> 
> (2) Has anybody been able to recreate pdfjadetex.fmt (and jadetex.fmt) with
> more resources on a Cygnus-RedHat 6.2 system?  Files are missing in the
> jadetex rpm, but even when I replace those files, I cannot recreate
> pdfjadetex.fmt or jadetex.fmt.  This is unlikely to be a tetex problem
> because I can recreate all *.fmt files *except pdfjadetex.fmt and
> jadetex.fmt*.
> 
> It has been suggested previously on this list that the "I'm stymied" problem
> might be due to lack of resources.  I successfully create extra resources
> for pdfjadetex.fmt and jadetex.fmt on my Debian box with the appropriate
> pdfjadetex.ini and jadetex.ini files and the appropriate special
> configuration file for fmtutil configuration file.  (These are the files
> that are missing from the Cygnus jadetex.rpm file).  However, even when I
> copy the missing files from my Debian box to the Cygnus RedHat 6.2 box, the
> fmtutil command does nothing when the special configuration file is
> specified.  The procedure returns after a second or two with no error
> messages or any other kind of output.  OTOH, if I execute fmtutil --all
> (i.e., using the standard configuration file) on the Cygnus box, all *.fmt
> files are recreated with parameters specified in texmf.cnf except for
> pdfjadetex.fmt and jadetex.fmt which remain completely unchanged with
> the old dates.
> 
> (3) I am beginning to feel the pdfjadetex problem might be more fundamental
> than lack of resources since hello_world takes up so few resources, and any
> attempt to reformat pdfjadetex (and jadetex) with more resources also fails.
> So I would be most interested whether anybody can get either (1) or (2) to
> work.
> 
> ****System Details****
> 
> (1) Redhat 6.2 box completely updated with latest bug, security, etc., fixes from
> the Redhat site.
> 
> (2) Vanilla RedHat 6.2 Docbook stripped out.  Here is the list of package files
> whose equivalent package was removed.
> docbook-3.1-3.noarch.rpm
> jade-1.2.1-9.i386.rpm
> jadetex-2.7-2.i386.rpm
> sgml-common-0.1-7.noarch.rpm
> sgml-tools-1.0.9-5.i386.rpm
> stylesheets-0.13rh-4.noarch.rpm
> 
> (3) Latest Cygnus DocBook installed.
> 
> docbook-dtd31-sgml-1.0-6.noarch.rpm
> docbook-dtd41-sgml-1.0-6.noarch.rpm
> docbook-dtd41-xml-1.0-2.noarch.rpm
> docbook-style-dsssl-1.57-2.noarch.rpm
> docbook-utils-0.6-1.noarch.rpm
> jade-1.2.1-6.i386.rpm
> jadetex-2.20-4.noarch.rpm
> perl-SGMLSpm-1.03ii-3.noarch.rpm
> sgml-common-0.4-1.noarch.rpm
> 
> ******Background:
> 
> I am part of the documentation team for the plplot project
> ( http://www.plplot.org .), and we successfully build our 100+ pages of
> documentation using the Debian DocBook tools.  But those in the group
> without access to Debian need to build the documentation on RedHat 6.2, and
> I would like to recommend the Cygnus solution to them for this purpose.  So
> far it works fairly well except for this pdf generation problem, and I hope
> somebody can help to get that straightened out.
> 
> Thanks in advance,
> 
> Alan
> 
> email: irwin@beluga.phys.uvic.ca
> phone: 250-727-2902	FAX: 250-721-7715
> snail-mail:
> Dr. Alan W. Irwin
> Department of Physics and Astronomy,
> University of Victoria, P.O. Box 3055,
> Victoria, British Columbia, Canada, V8W 3P6 
> __________________________
> 
> Linux-powered astrophysics
> __________________________
> 
> 
> 

jade catalog problems for Cygnus DocBook 4.1 XML

[Alan W. Irwin]

Eric, thanks for that earlier acknowledgment that you have at least seen my
pdfjadetex bug report.  Since you have so much to do I will be patient, and
I will try to help out as much as possible by what I hope are clear bug
reports and examples. While we wait for you to get a chance to sort out
these problems I have found, a subset of our team can build our
documentation on Debian DocBook 4.1 XML instead.  But we are looking forward
to when this will all work properly on Cygnus/RedHat as well.

This current post is a bug report for entities that Cygnus just cannot seem
to find although they are defined within the catalog chain.  I believe these
entity problems are completely independent of the pdfjadetex problem I
reported before. I am only copying that other bug report below so you will
know all the details of my system.  Sorry that I could not actually find a
solution of these entity problems, but here are the symptoms for a simple
example with egrave.

jade -c /etc/sgml/catalog -d
/usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl -t tex
/usr/share/sgml/xml.dcl hello_world.xml
jade:hello_world.xml:6:26:E: general entity "egrave" not defined and no
default entity

The example was identical to that used before to demonstrate the pdfjadetex
problem except that I put an è reference in the title to demonstrate
the problem that results in the above jade error message.  Here are the
first few hello_world.xml lines including the è

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" [
]>
<book>
<bookinfo>
<date>1997-10-11</date>
<title>My first bookl&egrave;t</title>

On Cygnus, I get this error message and the appropriate symbol is missing
from the *.ps output once jadetex and dvips are run.  On Debian I do not get
the above error and the appropriate symbol is in the postscript output.

For egrave, I worked backward through the chain of catalog entries in the
following way:

find /usr/share/sgml -type f | xargs grep egrave
/usr/share/sgml/sgml-iso-entities-8879.1986/ISOlat1.ent:<!ENTITY egrave SDATA "[egrave]"--=small e, grave accent-->

find /usr/share/sgml -type f | xargs grep ISOlat1.ent
/usr/share/sgml/sgml-iso-entities-8879.1986/catalog:PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN" ISOlat1.ent

find /etc/sgml/ -type f | xargs grep sgml-iso-entities-8879.1986/catalog
/etc/sgml/sgml-docbook-3.1.cat:CATALOG /usr/share/sgml/sgml-iso-entities-8879.1986/catalog
/etc/sgml/xml-docbook-4.1.cat:CATALOG /usr/share/sgml/sgml-iso-entities-8879.1986/catalog
/etc/sgml/sgml-docbook-4.1.cat:CATALOG /usr/share/sgml/sgml-iso-entities-8879.1986/catalog

cat /etc/sgml/catalog
CATALOG /etc/sgml/sgml-docbook-3.1.cat
CATALOG /etc/sgml/xml-docbook-4.1.cat
CATALOG /etc/sgml/sgml-docbook-4.1.cat

Perhaps there is some minor typo in this chain of catalogs, but I cannot
spot it so I have no idea why egrave is undefined as far as jade is
concerned.  This is just a wild guess, but perhaps jade cannot handle a
four-level deep catalog chain as above?

To test that wild guess I tried specifying two catalog entries as a
colon-separated list, i.e., 
jade -c \
/etc/sgml/catalog:/usr/share/sgml/sgml-iso-entities-8879.1986/ISOlat1.ent \
[...]

but jade does not allow specifying two separate catalogs as a colon-separated
list this way so that got nowhere.

I have just given you details of the egrave example, but we find similar
undefined problems for nbsp, ndash, and mdash entities on Cygnus that do not
occur on Debian.  Probably the solution for these additional undefined
entitities will be obvious once the egrave problem is solved.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

On Mon, 4 Dec 2000, Alan W. Irwin wrote:

> Three pdfjadetex questions/comments, then details of my system.
> 
> (1) Has anybody gotten the pdfjadetex command to work with the latest Cygnus docbook?
> 
> My 100+ pages of documentation definitely don't work, but to reproduce the
> bug in an easy way I use the hello world file from
> http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/get-going.html#HELLO-WORLD
> with the first 2 lines replaced by
> 
> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1//EN" [
> ]>
> 
> I created hello_world.tex using
> 
> jade -c /etc/sgml/catalog \
> -d  /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl \
> -t tex /usr/share/sgml/xml.dcl hello_world.xml
> 
> To check hello_world.tex is a good file I executed
> 
> jadetex hello_world.tex
> 
> The dvi file could be displayed with xdvi without problems.
> 
> ******However, I cannot create a pdf version of this document**********
> 
> pdfjadetex hello_world.tex 
> This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
> (Fatal format file error; I'm stymied)
> 
> Note this command works fine on my Debian box with this simple example and
> also my 100+ pages of documentation.
> 
> (2) Has anybody been able to recreate pdfjadetex.fmt (and jadetex.fmt) with
> more resources on a Cygnus-RedHat 6.2 system?  Files are missing in the
> jadetex rpm, but even when I replace those files, I cannot recreate
> pdfjadetex.fmt or jadetex.fmt.  This is unlikely to be a tetex problem
> because I can recreate all *.fmt files *except pdfjadetex.fmt and
> jadetex.fmt*.
> 
> It has been suggested previously on this list that the "I'm stymied" problem
> might be due to lack of resources.  I successfully create extra resources
> for pdfjadetex.fmt and jadetex.fmt on my Debian box with the appropriate
> pdfjadetex.ini and jadetex.ini files and the appropriate special
> configuration file for fmtutil configuration file.  (These are the files
> that are missing from the Cygnus jadetex.rpm file).  However, even when I
> copy the missing files from my Debian box to the Cygnus RedHat 6.2 box, the
> fmtutil command does nothing when the special configuration file is
> specified.  The procedure returns after a second or two with no error
> messages or any other kind of output.  OTOH, if I execute fmtutil --all
> (i.e., using the standard configuration file) on the Cygnus box, all *.fmt
> files are recreated with parameters specified in texmf.cnf except for
> pdfjadetex.fmt and jadetex.fmt which remain completely unchanged with
> the old dates.
> 
> (3) I am beginning to feel the pdfjadetex problem might be more fundamental
> than lack of resources since hello_world takes up so few resources, and any
> attempt to reformat pdfjadetex (and jadetex) with more resources also fails.
> So I would be most interested whether anybody can get either (1) or (2) to
> work.
> 
> ****System Details****
> 
> (1) Redhat 6.2 box completely updated with latest bug, security, etc., fixes from
> the Redhat site.
> 
> (2) Vanilla RedHat 6.2 Docbook stripped out.  Here is the list of package files
> whose equivalent package was removed.
> docbook-3.1-3.noarch.rpm
> jade-1.2.1-9.i386.rpm
> jadetex-2.7-2.i386.rpm
> sgml-common-0.1-7.noarch.rpm
> sgml-tools-1.0.9-5.i386.rpm
> stylesheets-0.13rh-4.noarch.rpm
> 
> (3) Latest Cygnus DocBook installed.
> 
> docbook-dtd31-sgml-1.0-6.noarch.rpm
> docbook-dtd41-sgml-1.0-6.noarch.rpm
> docbook-dtd41-xml-1.0-2.noarch.rpm
> docbook-style-dsssl-1.57-2.noarch.rpm
> docbook-utils-0.6-1.noarch.rpm
> jade-1.2.1-6.i386.rpm
> jadetex-2.20-4.noarch.rpm
> perl-SGMLSpm-1.03ii-3.noarch.rpm
> sgml-common-0.4-1.noarch.rpm
> 
> ******Background:
> 
> I am part of the documentation team for the plplot project
> ( http://www.plplot.org .), and we successfully build our 100+ pages of
> documentation using the Debian DocBook tools.  But those in the group
> without access to Debian need to build the documentation on RedHat 6.2, and
> I would like to recommend the Cygnus solution to them for this purpose.  So
> far it works fairly well except for this pdf generation problem, and I hope
> somebody can help to get that straightened out.
> 
> Thanks in advance,
> 
> Alan
> 
> email: irwin@beluga.phys.uvic.ca
> phone: 250-727-2902	FAX: 250-721-7715
> snail-mail:
> Dr. Alan W. Irwin
> Department of Physics and Astronomy,
> University of Victoria, P.O. Box 3055,
> Victoria, British Columbia, Canada, V8W 3P6 
> __________________________
> 
> Linux-powered astrophysics
> __________________________
> 
> 
> 

Re: jade catalog problems for Cygnus DocBook 4.1 XML

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3153 bytes --]

"Alan W. Irwin" wrote:
> 
> Eric, thanks for that earlier acknowledgment that you have at least seen my
> pdfjadetex bug report.  Since you have so much to do I will be patient, and
> I will try to help out as much as possible by what I hope are clear bug
> reports and examples. While we wait for you to get a chance to sort out
> these problems I have found, a subset of our team can build our
> documentation on Debian DocBook 4.1 XML instead.  But we are looking forward
> to when this will all work properly on Cygnus/RedHat as well.

Thanks for your patience. For the moment, I'm putting the pressure on
supporting Asian languages in printed output, and my TODO list is
growing ;-).

> This current post is a bug report for entities that Cygnus just cannot seem
> to find although they are defined within the catalog chain.  I believe these
> entity problems are completely independent of the pdfjadetex problem I
> reported before. I am only copying that other bug report below so you will
> know all the details of my system.  Sorry that I could not actually find a
> solution of these entity problems, but here are the symptoms for a simple
> example with egrave.
> 
> jade -c /etc/sgml/catalog -d
> /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl -t tex
> /usr/share/sgml/xml.dcl hello_world.xml
> jade:hello_world.xml:6:26:E: general entity "egrave" not defined and no
> default entity

The cygnus packages come with a package named "docbook-utils", which
include scripts like "docbook2tex" (formerly db2tex) who make all this
catalog thingy transparent. Give them a try, it will avoid you building
complex command lines like this one.

I advice you *NOT* to use /etc/sgml/catalog. This is the "super-catalog"
that references indirectly *every* declared SGML file on you systems via
four levels of indirection. So it's both slow and is not guaranteed to
be bulletproof against declaration conflicts. It is meant as a "last
chance" solution.

> Perhaps there is some minor typo in this chain of catalogs, but I cannot
> spot it so I have no idea why egrave is undefined as far as jade is
> concerned.  This is just a wild guess, but perhaps jade cannot handle a
> four-level deep catalog chain as above?

It can ;-), but try using /etc/sgml/xml-docboook-4.1 to avoid
declaration conflicts.
Please also check that you have read access on every file on the chain.
If this does not work try declaring explicitely '-c
/usr/share/sgml/sgml-iso-entities-8879.1986/catalog" on the command line
and mail me privately.

> To test that wild guess I tried specifying two catalog entries as a
> colon-separated list, i.e.,
> jade -c \
> /etc/sgml/catalog:/usr/share/sgml/sgml-iso-entities-8879.1986/ISOlat1.ent \

The colon syntax works only for the SGML_CATALOG_FILES environment
variable. Use several -c arguments.

You're the first one to describe such a problem.
-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
in case of problems: ebisch@cybercable.tm.fr
+----------------------------------------------------------------------+

Re: jade catalog problems for Cygnus DocBook 4.1 XML

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3153 bytes --]

"Alan W. Irwin" wrote:
> 
> Eric, thanks for that earlier acknowledgment that you have at least seen my
> pdfjadetex bug report.  Since you have so much to do I will be patient, and
> I will try to help out as much as possible by what I hope are clear bug
> reports and examples. While we wait for you to get a chance to sort out
> these problems I have found, a subset of our team can build our
> documentation on Debian DocBook 4.1 XML instead.  But we are looking forward
> to when this will all work properly on Cygnus/RedHat as well.

Thanks for your patience. For the moment, I'm putting the pressure on
supporting Asian languages in printed output, and my TODO list is
growing ;-).

> This current post is a bug report for entities that Cygnus just cannot seem
> to find although they are defined within the catalog chain.  I believe these
> entity problems are completely independent of the pdfjadetex problem I
> reported before. I am only copying that other bug report below so you will
> know all the details of my system.  Sorry that I could not actually find a
> solution of these entity problems, but here are the symptoms for a simple
> example with egrave.
> 
> jade -c /etc/sgml/catalog -d
> /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl -t tex
> /usr/share/sgml/xml.dcl hello_world.xml
> jade:hello_world.xml:6:26:E: general entity "egrave" not defined and no
> default entity

The cygnus packages come with a package named "docbook-utils", which
include scripts like "docbook2tex" (formerly db2tex) who make all this
catalog thingy transparent. Give them a try, it will avoid you building
complex command lines like this one.

I advice you *NOT* to use /etc/sgml/catalog. This is the "super-catalog"
that references indirectly *every* declared SGML file on you systems via
four levels of indirection. So it's both slow and is not guaranteed to
be bulletproof against declaration conflicts. It is meant as a "last
chance" solution.

> Perhaps there is some minor typo in this chain of catalogs, but I cannot
> spot it so I have no idea why egrave is undefined as far as jade is
> concerned.  This is just a wild guess, but perhaps jade cannot handle a
> four-level deep catalog chain as above?

It can ;-), but try using /etc/sgml/xml-docboook-4.1 to avoid
declaration conflicts.
Please also check that you have read access on every file on the chain.
If this does not work try declaring explicitely '-c
/usr/share/sgml/sgml-iso-entities-8879.1986/catalog" on the command line
and mail me privately.

> To test that wild guess I tried specifying two catalog entries as a
> colon-separated list, i.e.,
> jade -c \
> /etc/sgml/catalog:/usr/share/sgml/sgml-iso-entities-8879.1986/ISOlat1.ent \

The colon syntax works only for the SGML_CATALOG_FILES environment
variable. Use several -c arguments.

You're the first one to describe such a problem.
-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
in case of problems: ebisch@cybercable.tm.fr
+----------------------------------------------------------------------+

Re: .pdf generation error using the "newer" tools

[Bill Brooks]

On Sat, 2 Dec 2000, Alan W. Irwin wrote:

> Sorry for bringing this up again from the recent archives, but I am a newbie
> on this list. 
> 
> I have exactly the same problem as Bill Brooks, and the suggested fix
> doesn't work.

Sorry for the late follow-up. Yes, the suggested fix didn't work for me
either. 

I really wonder what the developers of the Cygnus docbook tool chain are
using...if it doesn't work on RedHat, what will it work on? 

I filed a bug report about this with RedHat and their support person
mailed me back saying that the ones that ship with 6.2 work...the new
RPM's on the old cygnus site aren't supported. 

Bill

Re: .pdf generation error using the "newer" tools

[Bill Brooks]

On Sat, 2 Dec 2000, Alan W. Irwin wrote:

> Sorry for bringing this up again from the recent archives, but I am a newbie
> on this list. 
> 
> I have exactly the same problem as Bill Brooks, and the suggested fix
> doesn't work.

Sorry for the late follow-up. Yes, the suggested fix didn't work for me
either. 

I really wonder what the developers of the Cygnus docbook tool chain are
using...if it doesn't work on RedHat, what will it work on? 

I filed a bug report about this with RedHat and their support person
mailed me back saying that the ones that ship with 6.2 work...the new
RPM's on the old cygnus site aren't supported. 

Bill

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]

Bill Brooks wrote:
> 
> Sorry for the late follow-up. Yes, the suggested fix didn't work for me
> either.
> 
> I really wonder what the developers of the Cygnus docbook tool chain are
> using...if it doesn't work on RedHat, what will it work on?
> 
> I filed a bug report about this with RedHat and their support person
> mailed me back saying that the ones that ship with 6.2 work...the new
> RPM's on the old cygnus site aren't supported.

... which means they provide outdated DTDs and style sheets then, if I
understand correctly. If this is true, then it's not good. At cygnus you
can find:
- The 4.1 DTD in SGML and XML versions
- The 1.59 style sheets
- Jadetex version 2.20
Which versions does RedHat provide currently?

Basically, it's a TeX problem, not a DocBook one. If RedHat fixes it in
the DocBook package, then they are wrong, because it breaks the
principle of packages independancy that they themselves edicted. The
right thing is to fix it in TeX package. This way, it will both work for
old and new Cygnus packages.

BTW, Cygnus is owned by RedHat - I'm criticizing them here, but I must
also thank them for helping the DocBook-tools project by hosting it :-).

Having said that, I must recognize that I also have my part of
responsability. I took their old patch to texmf.cnf and found it too
violent, so I removed from it everything that I found not indispensable.
This was wrong, JadeTeX really needs *lots* of TeX ressources. But I
must also say that I never considered this patch as something official,
I was just sending it to people to help them.

Here is how we can fix it. Someone, please send me RedHat's texmf.cnf.
Then I will put the changes they did as a patch file somewhere on
Cygnus' site. And promised, I won't remove anything from it this time.
It will eat all your memory, folks, get prepared ;-).

-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
| (Old address, in case of problems:  mailto:ebisch@cybercable.tm.fr )  |
+----------------------------------------------------------------------+

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]

Bill Brooks wrote:
> 
> Sorry for the late follow-up. Yes, the suggested fix didn't work for me
> either.
> 
> I really wonder what the developers of the Cygnus docbook tool chain are
> using...if it doesn't work on RedHat, what will it work on?
> 
> I filed a bug report about this with RedHat and their support person
> mailed me back saying that the ones that ship with 6.2 work...the new
> RPM's on the old cygnus site aren't supported.

... which means they provide outdated DTDs and style sheets then, if I
understand correctly. If this is true, then it's not good. At cygnus you
can find:
- The 4.1 DTD in SGML and XML versions
- The 1.59 style sheets
- Jadetex version 2.20
Which versions does RedHat provide currently?

Basically, it's a TeX problem, not a DocBook one. If RedHat fixes it in
the DocBook package, then they are wrong, because it breaks the
principle of packages independancy that they themselves edicted. The
right thing is to fix it in TeX package. This way, it will both work for
old and new Cygnus packages.

BTW, Cygnus is owned by RedHat - I'm criticizing them here, but I must
also thank them for helping the DocBook-tools project by hosting it :-).

Having said that, I must recognize that I also have my part of
responsability. I took their old patch to texmf.cnf and found it too
violent, so I removed from it everything that I found not indispensable.
This was wrong, JadeTeX really needs *lots* of TeX ressources. But I
must also say that I never considered this patch as something official,
I was just sending it to people to help them.

Here is how we can fix it. Someone, please send me RedHat's texmf.cnf.
Then I will put the changes they did as a patch file somewhere on
Cygnus' site. And promised, I won't remove anything from it this time.
It will eat all your memory, folks, get prepared ;-).

-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
| (Old address, in case of problems:  mailto:ebisch@cybercable.tm.fr )  |
+----------------------------------------------------------------------+

Re: .pdf generation error using the "newer" tools

[Tim Waugh]

On Sat, Dec 09, 2000 at 12:57:41PM +0100, Eric Bischoff wrote:

> - The 4.1 DTD in SGML and XML versions
> - The 1.59 style sheets
> - Jadetex version 2.20
> Which versions does RedHat provide currently?

3.1(!) DTD, 1.57 stylesheets, openjade 1.3.

(Yes, it needs sorting out.)

Tim.
*/
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6Mh3/ONXnILZ4yVIRAlPWAJ0dnDQxBrVgELDjvDGCrF1L6EICmgCgjISn
0EfTjyHtNoy8qw+Dj2O3Igw=
=3p3Q
-----END PGP SIGNATURE-----

Re: .pdf generation error using the "newer" tools

[Tim Waugh]

On Sat, Dec 09, 2000 at 12:57:41PM +0100, Eric Bischoff wrote:

> - The 4.1 DTD in SGML and XML versions
> - The 1.59 style sheets
> - Jadetex version 2.20
> Which versions does RedHat provide currently?

3.1(!) DTD, 1.57 stylesheets, openjade 1.3.

(Yes, it needs sorting out.)

Tim.
*/
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6Mh3/ONXnILZ4yVIRAlPWAJ0dnDQxBrVgELDjvDGCrF1L6EICmgCgjISn
0EfTjyHtNoy8qw+Dj2O3Igw=
=3p3Q
-----END PGP SIGNATURE-----

Re: .pdf generation error using the "newer" tools

[Mirko Streckenbach]

Tim Waugh <twaugh@redhat.com> writes:

> On Sat, Dec 09, 2000 at 12:57:41PM +0100, Eric Bischoff wrote:
> 
> > - The 4.1 DTD in SGML and XML versions
> > - The 1.59 style sheets
> > - Jadetex version 2.20
> > Which versions does RedHat provide currently?
> 
> 3.1(!) DTD, 1.57 stylesheets, openjade 1.3.

BTW: Is it planned for the "new-trials" packages to move from
jade-1.2.1 to openjade-1.3?

The compiler in RedHat 7 does not compile jade-1.2.1 out of the box
and I double the official gcc-3 will, when it is
realeased. Historcially newer versions of gcc have always broken the
out of the box compilation for jade.


ciao,
mirko.

Re: .pdf generation error using the "newer" tools

[Mirko Streckenbach]

Tim Waugh <twaugh@redhat.com> writes:

> On Sat, Dec 09, 2000 at 12:57:41PM +0100, Eric Bischoff wrote:
> 
> > - The 4.1 DTD in SGML and XML versions
> > - The 1.59 style sheets
> > - Jadetex version 2.20
> > Which versions does RedHat provide currently?
> 
> 3.1(!) DTD, 1.57 stylesheets, openjade 1.3.

BTW: Is it planned for the "new-trials" packages to move from
jade-1.2.1 to openjade-1.3?

The compiler in RedHat 7 does not compile jade-1.2.1 out of the box
and I double the official gcc-3 will, when it is
realeased. Historcially newer versions of gcc have always broken the
out of the box compilation for jade.


ciao,
mirko.

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

Le Mercredi 13 Décembre 2000 10:32, vous avez écrit :
> Tim Waugh <twaugh@redhat.com> writes:
> > On Sat, Dec 09, 2000 at 12:57:41PM +0100, Eric Bischoff wrote:
> > > - The 4.1 DTD in SGML and XML versions
> > > - The 1.59 style sheets
> > > - Jadetex version 2.20
> > > Which versions does RedHat provide currently?
> >
> > 3.1(!) DTD, 1.57 stylesheets, openjade 1.3.
>
> BTW: Is it planned for the "new-trials" packages to move from
> jade-1.2.1 to openjade-1.3?

I haven't the time for this right now. If someone wants to do it, then fine, 
he can send me the resulting source package, and I will integrate it to the 
others (we will need a Provide: virtual capability to be able to use 
indifferently one or the other package) but I won't do it.

> The compiler in RedHat 7 does not compile jade-1.2.1 out of the box
> and I double the official gcc-3 will, when it is
> realeased. Historcially newer versions of gcc have always broken the
> out of the box compilation for jade.

It compiles out of the box on my LinuxPPC. For Caldera, I had to do a patch 
against gcc, that's true, but now it works. Another solution would be to test 
this patch on a vanilla RedHat. Volunteers please mail in private.

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]

Le Mercredi 13 Décembre 2000 10:32, vous avez écrit :
> Tim Waugh <twaugh@redhat.com> writes:
> > On Sat, Dec 09, 2000 at 12:57:41PM +0100, Eric Bischoff wrote:
> > > - The 4.1 DTD in SGML and XML versions
> > > - The 1.59 style sheets
> > > - Jadetex version 2.20
> > > Which versions does RedHat provide currently?
> >
> > 3.1(!) DTD, 1.57 stylesheets, openjade 1.3.
>
> BTW: Is it planned for the "new-trials" packages to move from
> jade-1.2.1 to openjade-1.3?

I haven't the time for this right now. If someone wants to do it, then fine, 
he can send me the resulting source package, and I will integrate it to the 
others (we will need a Provide: virtual capability to be able to use 
indifferently one or the other package) but I won't do it.

> The compiler in RedHat 7 does not compile jade-1.2.1 out of the box
> and I double the official gcc-3 will, when it is
> realeased. Historcially newer versions of gcc have always broken the
> out of the box compilation for jade.

It compiles out of the box on my LinuxPPC. For Caldera, I had to do a patch 
against gcc, that's true, but now it works. Another solution would be to test 
this patch on a vanilla RedHat. Volunteers please mail in private.

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

Re: .pdf generation error using the "newer" tools

[Alan W. Irwin]

Both the Cygnus DocBook packages and vanilla RedHat DocBook run on RedHat.
But you have to clearly choose Cygnus or vanilla.  If you try both on RedHat
they will interfere with each other. 

I don't want to get into a DocBook distribution war here, but my impression is the
Cygnus tools are generally better than the vanilla RedHat ones.  For example,
Cygnus is recommended to build the KDE documentation, and I have had more
troubles with the vanilla version than the Cygnus version for my documentation
project.

But to take advantage of Cygnus you have to get the latest version.  For
example, there was an upgraded package today at
ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials/RPMS that Eric
kindly prepared to fix another bug that I found.

The major problem with pdfjadetex hasn't been fixed yet, but Eric said on
this list that it is on his ToDo list.  He will have to delay looking at it
until another higher priority project was completed, but I am willing to
settle for that.

Debian has a reliable DocBook system where pdfjadetex (and everything else
for my documentation project) works reliably for me, but if you don't have
access to Debian, I think you are going to have to wait to build your pdf
documents on Cygnus (or else give the vanilla Redhat DocBook system a try to
see if you can work around other problems there.) While waiting for pdf on
Cygnus you can certainly validate your input by looking at html or
postscript output.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

On Fri, 8 Dec 2000, Bill Brooks wrote:

> On Sat, 2 Dec 2000, Alan W. Irwin wrote:
> 
> > Sorry for bringing this up again from the recent archives, but I am a newbie
> > on this list. 
> > 
> > I have exactly the same problem as Bill Brooks, and the suggested fix
> > doesn't work.
> 
> Sorry for the late follow-up. Yes, the suggested fix didn't work for me
> either. 
> 
> I really wonder what the developers of the Cygnus docbook tool chain are
> using...if it doesn't work on RedHat, what will it work on? 
> 
> I filed a bug report about this with RedHat and their support person
> mailed me back saying that the ones that ship with 6.2 work...the new
> RPM's on the old cygnus site aren't supported. 
> 
> Bill
> 
> 
> 

Re: .pdf generation error using the "newer" tools

[Alan W. Irwin]

Both the Cygnus DocBook packages and vanilla RedHat DocBook run on RedHat.
But you have to clearly choose Cygnus or vanilla.  If you try both on RedHat
they will interfere with each other. 

I don't want to get into a DocBook distribution war here, but my impression is the
Cygnus tools are generally better than the vanilla RedHat ones.  For example,
Cygnus is recommended to build the KDE documentation, and I have had more
troubles with the vanilla version than the Cygnus version for my documentation
project.

But to take advantage of Cygnus you have to get the latest version.  For
example, there was an upgraded package today at
ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials/RPMS that Eric
kindly prepared to fix another bug that I found.

The major problem with pdfjadetex hasn't been fixed yet, but Eric said on
this list that it is on his ToDo list.  He will have to delay looking at it
until another higher priority project was completed, but I am willing to
settle for that.

Debian has a reliable DocBook system where pdfjadetex (and everything else
for my documentation project) works reliably for me, but if you don't have
access to Debian, I think you are going to have to wait to build your pdf
documents on Cygnus (or else give the vanilla Redhat DocBook system a try to
see if you can work around other problems there.) While waiting for pdf on
Cygnus you can certainly validate your input by looking at html or
postscript output.

Alan

email: irwin@beluga.phys.uvic.ca
phone: 250-727-2902	FAX: 250-721-7715
snail-mail:
Dr. Alan W. Irwin
Department of Physics and Astronomy,
University of Victoria, P.O. Box 3055,
Victoria, British Columbia, Canada, V8W 3P6 
__________________________

Linux-powered astrophysics
__________________________

On Fri, 8 Dec 2000, Bill Brooks wrote:

> On Sat, 2 Dec 2000, Alan W. Irwin wrote:
> 
> > Sorry for bringing this up again from the recent archives, but I am a newbie
> > on this list. 
> > 
> > I have exactly the same problem as Bill Brooks, and the suggested fix
> > doesn't work.
> 
> Sorry for the late follow-up. Yes, the suggested fix didn't work for me
> either. 
> 
> I really wonder what the developers of the Cygnus docbook tool chain are
> using...if it doesn't work on RedHat, what will it work on? 
> 
> I filed a bug report about this with RedHat and their support person
> mailed me back saying that the ones that ship with 6.2 work...the new
> RPM's on the old cygnus site aren't supported. 
> 
> Bill
> 
> 
> 

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3178 bytes --]

"Alan W. Irwin" wrote:
> 
> Both the Cygnus DocBook packages and vanilla RedHat DocBook run on RedHat.
> But you have to clearly choose Cygnus or vanilla.  If you try both on RedHat
> they will interfere with each other.

This is an excellent reason for encouraging them to switch to the new
packages. They will get more powerful tools with more recent versions of
the DTD, Jadetex and the style sheets. Mandrake and Caldera already did
jump to the new versions. I've been told a port is currently happening
at Debian too.

> I don't want to get into a DocBook distribution war here, but my impression is the
> Cygnus tools are generally better than the vanilla RedHat ones.

What you call "vanilla RedHat DocBook" are the old Cygnus packages, the
ones that you do not find in new-trials/. Basically, Mark Galassi did
the old ones, I found them great, and started enhancing them. This all
sounds like schizophreny: RedHat hosts the DocBook-tools project, but
they don't include yet the newest versions in their own distribution
:-).

> For example,
> Cygnus is recommended to build the KDE documentation, and I have had more
> troubles with the vanilla version than the Cygnus version for my documentation
> project.

This is quite simple to explain. KDE's documentation project leader is
named Eric Bischoff. It's the same guy who attempts to perfect Mark
Galassi's scripts ;-). If you go to ftp://ftp.kde.org/pub/devel/docbook ,
you will find exactly the same packages as in
ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials .

> But to take advantage of Cygnus you have to get the latest version.  For
> example, there was an upgraded package today at
> ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials/RPMS that Eric
> kindly prepared to fix another bug that I found.

(the problem with the ISO entities in XML - fixed since yesterday).

> The major problem with pdfjadetex hasn't been fixed yet, but Eric said on
> this list that it is on his ToDo list. He will have to delay looking at it
> until another higher priority project was completed, but I am willing to
> settle for that.

(higher priority being support for Japanese, Korean and Chinese in
printed output).

> Debian has a reliable DocBook system where pdfjadetex (and everything else
> for my documentation project) works reliably for me, but if you don't have
> access to Debian, I think you are going to have to wait to build your pdf
> documents on Cygnus (or else give the vanilla Redhat DocBook system a try to
> see if you can work around other problems there.) While waiting for pdf on
> Cygnus you can certainly validate your input by looking at html or
> postscript output.

I'm doing the documentation for Caldera and we need to send PDF to the
printing company. So be sure it will get fixed sooner or later :-).
Meanwhile, you can use ps2pdf as a workaround. Have you already tried?

-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
| (Old address, in case of problems:  mailto:ebisch@cybercable.tm.fr )  |
+----------------------------------------------------------------------+

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3178 bytes --]

"Alan W. Irwin" wrote:
> 
> Both the Cygnus DocBook packages and vanilla RedHat DocBook run on RedHat.
> But you have to clearly choose Cygnus or vanilla.  If you try both on RedHat
> they will interfere with each other.

This is an excellent reason for encouraging them to switch to the new
packages. They will get more powerful tools with more recent versions of
the DTD, Jadetex and the style sheets. Mandrake and Caldera already did
jump to the new versions. I've been told a port is currently happening
at Debian too.

> I don't want to get into a DocBook distribution war here, but my impression is the
> Cygnus tools are generally better than the vanilla RedHat ones.

What you call "vanilla RedHat DocBook" are the old Cygnus packages, the
ones that you do not find in new-trials/. Basically, Mark Galassi did
the old ones, I found them great, and started enhancing them. This all
sounds like schizophreny: RedHat hosts the DocBook-tools project, but
they don't include yet the newest versions in their own distribution
:-).

> For example,
> Cygnus is recommended to build the KDE documentation, and I have had more
> troubles with the vanilla version than the Cygnus version for my documentation
> project.

This is quite simple to explain. KDE's documentation project leader is
named Eric Bischoff. It's the same guy who attempts to perfect Mark
Galassi's scripts ;-). If you go to ftp://ftp.kde.org/pub/devel/docbook ,
you will find exactly the same packages as in
ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials .

> But to take advantage of Cygnus you have to get the latest version.  For
> example, there was an upgraded package today at
> ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials/RPMS that Eric
> kindly prepared to fix another bug that I found.

(the problem with the ISO entities in XML - fixed since yesterday).

> The major problem with pdfjadetex hasn't been fixed yet, but Eric said on
> this list that it is on his ToDo list. He will have to delay looking at it
> until another higher priority project was completed, but I am willing to
> settle for that.

(higher priority being support for Japanese, Korean and Chinese in
printed output).

> Debian has a reliable DocBook system where pdfjadetex (and everything else
> for my documentation project) works reliably for me, but if you don't have
> access to Debian, I think you are going to have to wait to build your pdf
> documents on Cygnus (or else give the vanilla Redhat DocBook system a try to
> see if you can work around other problems there.) While waiting for pdf on
> Cygnus you can certainly validate your input by looking at html or
> postscript output.

I'm doing the documentation for Caldera and we need to send PDF to the
printing company. So be sure it will get fixed sooner or later :-).
Meanwhile, you can use ps2pdf as a workaround. Have you already tried?

-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
| (Old address, in case of problems:  mailto:ebisch@cybercable.tm.fr )  |
+----------------------------------------------------------------------+

.pdf generation error using the "newer" tools

[Bill Brooks]

Okay,

I'm using the rpm's of the docbook tools. I did a clean install of RedHat
6.2, and followed the recommendation of the page at
http://i18n.kde.org/doc/install.html by de-installing the RPM's that ship
with RedHat and installing the following:

   docbook-dtd30-sgml-1.0-6.noarch.rpm
   docbook-dtd31-sgml-1.0-6.noarch.rpm
   docbook-dtd40-sgml-1.0-6.noarch.rpm
   docbook-dtd41-sgml-1.0-6.noarch.rpm
   docbook-style-dsssl-1.57-2.noarch.rpm
   docbook-utils-0.5.5-1.noarch.rpm
   jade-1.2.1-6.i386.rpm
   jadetex-2.20-2.noarch.rpm
   perl-SGMLSpm-1.03ii-3.noarch.rpm
   sgml-common-0.3-1.noarch.rpm

I copied the simple "Hello World" example from
http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/get-going.html#HELLO-WORLD
into a file called "helloworld.docbook". 

As people have mailed this list pointing out, the documentation on the
sources site is outdated, so I had to guess as to what flags would work
with the docbook utilities. Here's what I tried:

   docbook2pdf \
   ?  -c /usr/share/sgml/docbook/sgml-dtd-3.1/catalog \
   ?  -d /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
   helloworld.docbook

Is this right? I'd be happy to mail Mark Galassi a patch to the
http://sources.redhat.com/docbook-tools/ web page that documents how to
use the flags with the file locations where the RPM's put things if
someone can get me started on the right path.

Also, it seems like there is a problem actually producing a .pdf, here's
what I get:

   Using catalogs: /etc/sgml/sgml-docbook-3.0.cat,
   /usr/share/sgml/docbook/sgml-dtd-3.1/catalog
   Using stylesheet:
   /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
   Working on: /home/wbrooks/box/work/foo/helloworld.docbook
   This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
   (Fatal format file error; I'm stymied)


...are other people able to get this working? 

Bill

.pdf generation error using the "newer" tools

[Bill Brooks]

Okay,

I'm using the rpm's of the docbook tools. I did a clean install of RedHat
6.2, and followed the recommendation of the page at
http://i18n.kde.org/doc/install.html by de-installing the RPM's that ship
with RedHat and installing the following:

   docbook-dtd30-sgml-1.0-6.noarch.rpm
   docbook-dtd31-sgml-1.0-6.noarch.rpm
   docbook-dtd40-sgml-1.0-6.noarch.rpm
   docbook-dtd41-sgml-1.0-6.noarch.rpm
   docbook-style-dsssl-1.57-2.noarch.rpm
   docbook-utils-0.5.5-1.noarch.rpm
   jade-1.2.1-6.i386.rpm
   jadetex-2.20-2.noarch.rpm
   perl-SGMLSpm-1.03ii-3.noarch.rpm
   sgml-common-0.3-1.noarch.rpm

I copied the simple "Hello World" example from
http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/get-going.html#HELLO-WORLD
into a file called "helloworld.docbook". 

As people have mailed this list pointing out, the documentation on the
sources site is outdated, so I had to guess as to what flags would work
with the docbook utilities. Here's what I tried:

   docbook2pdf \
   ?  -c /usr/share/sgml/docbook/sgml-dtd-3.1/catalog \
   ?  -d /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
   helloworld.docbook

Is this right? I'd be happy to mail Mark Galassi a patch to the
http://sources.redhat.com/docbook-tools/ web page that documents how to
use the flags with the file locations where the RPM's put things if
someone can get me started on the right path.

Also, it seems like there is a problem actually producing a .pdf, here's
what I get:

   Using catalogs: /etc/sgml/sgml-docbook-3.0.cat,
   /usr/share/sgml/docbook/sgml-dtd-3.1/catalog
   Using stylesheet:
   /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
   Working on: /home/wbrooks/box/work/foo/helloworld.docbook
   This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
   (Fatal format file error; I'm stymied)


...are other people able to get this working? 

Bill

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4054 bytes --]

Bill Brooks wrote:
> 
> Okay,
> 
> I'm using the rpm's of the docbook tools. I did a clean install of RedHat
> 6.2, and followed the recommendation of the page at
> http://i18n.kde.org/doc/install.html by de-installing the RPM's that ship
> with RedHat and installing the following:
> 
>    docbook-dtd30-sgml-1.0-6.noarch.rpm
>    docbook-dtd31-sgml-1.0-6.noarch.rpm
>    docbook-dtd40-sgml-1.0-6.noarch.rpm
>    docbook-dtd41-sgml-1.0-6.noarch.rpm
>    docbook-style-dsssl-1.57-2.noarch.rpm
>    docbook-utils-0.5.5-1.noarch.rpm
>    jade-1.2.1-6.i386.rpm
>    jadetex-2.20-2.noarch.rpm
>    perl-SGMLSpm-1.03ii-3.noarch.rpm
>    sgml-common-0.3-1.noarch.rpm
> 
> I copied the simple "Hello World" example from
> http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/get-going.html#HELLO-WORLD
> into a file called "helloworld.docbook".

You can find an updated and completed version of this tutorial at

	http://www.caldera.de/~eric/crash-course/HTML/index.html

It also has updated "hello world" examples in it.

> As people have mailed this list pointing out, the documentation on the
> sources site is outdated, so I had to guess as to what flags would work
> with the docbook utilities. Here's what I tried:
> 
>    docbook2pdf \
>    ?  -c /usr/share/sgml/docbook/sgml-dtd-3.1/catalog \
>    ?  -d /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
>    helloworld.docbook

The two -c and -d flags should not be necessary. But they ensure you use
"bare bones" Norman Walsh's stuff, and not our default stylesheet.

> Is this right? I'd be happy to mail Mark Galassi a patch to the
> http://sources.redhat.com/docbook-tools/ web page that documents how to
> use the flags with the file locations where the RPM's put things if
> someone can get me started on the right path.

If you volunteer to update the web pages, to me you're welcome ;-).
Mark?

> Also, it seems like there is a problem actually producing a .pdf, here's
> what I get:
> 
>    Using catalogs: /etc/sgml/sgml-docbook-3.0.cat,
>    /usr/share/sgml/docbook/sgml-dtd-3.1/catalog

The 3.0 catalog has been auto-detected by the docbook-utils because
you're trying to render a 3.0 (outdated) document.
The 3.1 catalog is used because you specified it on the command line.
This tells you you should remove the "-c" argument that forces here to
use a wrong catalog.

>    Using stylesheet:
>    /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
>    Working on: /home/wbrooks/box/work/foo/helloworld.docbook
>    This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
>    (Fatal format file error; I'm stymied)

TeX classical problem. The default configuration files do not allow
enough resources for docbook.

I think we have a corrected version on the web site. Attached is also a
patch we use at KDE.


-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/
--- texmf.cnf.orig       Thu Sep 24 21:40:14 1998
+++ texmf.cnf    Tue Oct  6 01:45:12 1998
@@ -371,6 +371,7 @@

 % Extra space for the hash table of control sequences (which allows 10K
 % names as distributed).
+hash_extra.jadetex = 15000
 hash_extra.context = 15000
 hash_extra.cont-en = 15000
 hash_extra.cont-nl = 15000
@@ -379,6 +380,7 @@

 % Max number of characters in all strings, including all error messages,
 % help texts, font names, control sequences.  These values apply to TeX and MP.
+pool_size.jadetex = 200000
 pool_size.context = 500000
 pool_size.cont-en = 500000
 pool_size.cont-nl = 500000
@@ -391,6 +393,7 @@
 string_vacancies.cont-nl = 45000
 string_vacancies.cont-de = 45000
 string_vacancies = 25000
+max_strings.jadetex = 50000
 max_strings.context = 55000
 max_strings.cont-en = 55000
 max_strings.cont-nl = 55000
@@ -434,6 +437,7 @@
 param_size.cont-nl = 1500
 param_size.cont-de = 1500
 param_size = 500        % simultaneous macro parameters
+save_size.jadetex = 15000
 save_size.context = 5000
 save_size.cont-en = 5000
 save_size.cont-nl = 5000

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4054 bytes --]

Bill Brooks wrote:
> 
> Okay,
> 
> I'm using the rpm's of the docbook tools. I did a clean install of RedHat
> 6.2, and followed the recommendation of the page at
> http://i18n.kde.org/doc/install.html by de-installing the RPM's that ship
> with RedHat and installing the following:
> 
>    docbook-dtd30-sgml-1.0-6.noarch.rpm
>    docbook-dtd31-sgml-1.0-6.noarch.rpm
>    docbook-dtd40-sgml-1.0-6.noarch.rpm
>    docbook-dtd41-sgml-1.0-6.noarch.rpm
>    docbook-style-dsssl-1.57-2.noarch.rpm
>    docbook-utils-0.5.5-1.noarch.rpm
>    jade-1.2.1-6.i386.rpm
>    jadetex-2.20-2.noarch.rpm
>    perl-SGMLSpm-1.03ii-3.noarch.rpm
>    sgml-common-0.3-1.noarch.rpm
> 
> I copied the simple "Hello World" example from
> http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/get-going.html#HELLO-WORLD
> into a file called "helloworld.docbook".

You can find an updated and completed version of this tutorial at

	http://www.caldera.de/~eric/crash-course/HTML/index.html

It also has updated "hello world" examples in it.

> As people have mailed this list pointing out, the documentation on the
> sources site is outdated, so I had to guess as to what flags would work
> with the docbook utilities. Here's what I tried:
> 
>    docbook2pdf \
>    ?  -c /usr/share/sgml/docbook/sgml-dtd-3.1/catalog \
>    ?  -d /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
>    helloworld.docbook

The two -c and -d flags should not be necessary. But they ensure you use
"bare bones" Norman Walsh's stuff, and not our default stylesheet.

> Is this right? I'd be happy to mail Mark Galassi a patch to the
> http://sources.redhat.com/docbook-tools/ web page that documents how to
> use the flags with the file locations where the RPM's put things if
> someone can get me started on the right path.

If you volunteer to update the web pages, to me you're welcome ;-).
Mark?

> Also, it seems like there is a problem actually producing a .pdf, here's
> what I get:
> 
>    Using catalogs: /etc/sgml/sgml-docbook-3.0.cat,
>    /usr/share/sgml/docbook/sgml-dtd-3.1/catalog

The 3.0 catalog has been auto-detected by the docbook-utils because
you're trying to render a 3.0 (outdated) document.
The 3.1 catalog is used because you specified it on the command line.
This tells you you should remove the "-c" argument that forces here to
use a wrong catalog.

>    Using stylesheet:
>    /usr/share/sgml/docbook/dsssl-stylesheets-1.57/print/docbook.dsl
>    Working on: /home/wbrooks/box/work/foo/helloworld.docbook
>    This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
>    (Fatal format file error; I'm stymied)

TeX classical problem. The default configuration files do not allow
enough resources for docbook.

I think we have a corrected version on the web site. Attached is also a
patch we use at KDE.


-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/
--- texmf.cnf.orig       Thu Sep 24 21:40:14 1998
+++ texmf.cnf    Tue Oct  6 01:45:12 1998
@@ -371,6 +371,7 @@

 % Extra space for the hash table of control sequences (which allows 10K
 % names as distributed).
+hash_extra.jadetex = 15000
 hash_extra.context = 15000
 hash_extra.cont-en = 15000
 hash_extra.cont-nl = 15000
@@ -379,6 +380,7 @@

 % Max number of characters in all strings, including all error messages,
 % help texts, font names, control sequences.  These values apply to TeX and MP.
+pool_size.jadetex = 200000
 pool_size.context = 500000
 pool_size.cont-en = 500000
 pool_size.cont-nl = 500000
@@ -391,6 +393,7 @@
 string_vacancies.cont-nl = 45000
 string_vacancies.cont-de = 45000
 string_vacancies = 25000
+max_strings.jadetex = 50000
 max_strings.context = 55000
 max_strings.cont-en = 55000
 max_strings.cont-nl = 55000
@@ -434,6 +437,7 @@
 param_size.cont-nl = 1500
 param_size.cont-de = 1500
 param_size = 500        % simultaneous macro parameters
+save_size.jadetex = 15000
 save_size.context = 5000
 save_size.cont-en = 5000
 save_size.cont-nl = 5000

Re: .pdf generation error using the "newer" tools

[Bill Brooks]

On Wed, 11 Oct 2000, Eric Bischoff wrote:

> The two -c and -d flags should not be necessary. But they ensure you use
> "bare bones" Norman Walsh's stuff, and not our default stylesheet.

Okay, I tried it again by just using the docbook2pdf helloworld.docbook
and still ran into some problems. Here's what I get with the same
helloworld document:

  docbook2pdf helloworld.docbook
  Using catalogs: /etc/sgml/sgml-docbook-3.0.cat
  Using stylesheet:
  /usr/share/sgml/docbook/utils-0.5.5/docbook-utils.dsl#print
  Working on: /home/wbrooks/box/work/foo/helloworld.docbook
  This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
  (Fatal format file error; I'm stymied)

So it looks like the correct version of the DTD and stylesheets are
getting used for this document, but it can't get pdfTeX to even begin
generating a .pdf file. 

> If you volunteer to update the web pages, to me you're welcome ;-).
> Mark?

Absolutely, I can either mail a patch to the existing web page or change
something in a CVS repository somewhere. 

> TeX classical problem. The default configuration files do not allow
> enough resources for docbook.
> [...]
> 
> I think we have a corrected version on the web site. Attached is also a
> patch we use at KDE.

My texmf.cnf file is substantially different than yours so applying the
patch failed. Can you send the whole file? Thanks in advance. 

Bill

Re: .pdf generation error using the "newer" tools

[Bill Brooks]

On Wed, 11 Oct 2000, Eric Bischoff wrote:

> The two -c and -d flags should not be necessary. But they ensure you use
> "bare bones" Norman Walsh's stuff, and not our default stylesheet.

Okay, I tried it again by just using the docbook2pdf helloworld.docbook
and still ran into some problems. Here's what I get with the same
helloworld document:

  docbook2pdf helloworld.docbook
  Using catalogs: /etc/sgml/sgml-docbook-3.0.cat
  Using stylesheet:
  /usr/share/sgml/docbook/utils-0.5.5/docbook-utils.dsl#print
  Working on: /home/wbrooks/box/work/foo/helloworld.docbook
  This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
  (Fatal format file error; I'm stymied)

So it looks like the correct version of the DTD and stylesheets are
getting used for this document, but it can't get pdfTeX to even begin
generating a .pdf file. 

> If you volunteer to update the web pages, to me you're welcome ;-).
> Mark?

Absolutely, I can either mail a patch to the existing web page or change
something in a CVS repository somewhere. 

> TeX classical problem. The default configuration files do not allow
> enough resources for docbook.
> [...]
> 
> I think we have a corrected version on the web site. Attached is also a
> patch we use at KDE.

My texmf.cnf file is substantially different than yours so applying the
patch failed. Can you send the whole file? Thanks in advance. 

Bill

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

Bill Brooks wrote:
> 
> On Wed, 11 Oct 2000, Eric Bischoff wrote:
> 
> > The two -c and -d flags should not be necessary. But they ensure you use
> > "bare bones" Norman Walsh's stuff, and not our default stylesheet.
> 
> Okay, I tried it again by just using the docbook2pdf helloworld.docbook
> and still ran into some problems. Here's what I get with the same
> helloworld document:
> 
>   docbook2pdf helloworld.docbook
>   Using catalogs: /etc/sgml/sgml-docbook-3.0.cat
>   Using stylesheet:
>   /usr/share/sgml/docbook/utils-0.5.5/docbook-utils.dsl#print
>   Working on: /home/wbrooks/box/work/foo/helloworld.docbook
>   This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
>   (Fatal format file error; I'm stymied)
> 
> So it looks like the correct version of the DTD and stylesheets are
> getting used for this document, but it can't get pdfTeX to even begin
> generating a .pdf file.

Right. It's a TeX problem, not a DocBook problem.

> > If you volunteer to update the web pages, to me you're welcome ;-).
> > Mark?
> 
> Absolutely, I can either mail a patch to the existing web page or change
> something in a CVS repository somewhere.

Let's wait for Mark's answer.

> > TeX classical problem. The default configuration files do not allow
> > enough resources for docbook.
> > [...]
> >
> > I think we have a corrected version on the web site. Attached is also a
> > patch we use at KDE.
> 
> My texmf.cnf file is substantially different than yours so applying the
> patch failed. Can you send the whole file? Thanks in advance.

The patch is not big and easy to read, so you can patch by hand. On the
contrary, if you get my file, it might break other things on your
machine.

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

Re: .pdf generation error using the "newer" tools

[Eric Bischoff]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

Bill Brooks wrote:
> 
> On Wed, 11 Oct 2000, Eric Bischoff wrote:
> 
> > The two -c and -d flags should not be necessary. But they ensure you use
> > "bare bones" Norman Walsh's stuff, and not our default stylesheet.
> 
> Okay, I tried it again by just using the docbook2pdf helloworld.docbook
> and still ran into some problems. Here's what I get with the same
> helloworld document:
> 
>   docbook2pdf helloworld.docbook
>   Using catalogs: /etc/sgml/sgml-docbook-3.0.cat
>   Using stylesheet:
>   /usr/share/sgml/docbook/utils-0.5.5/docbook-utils.dsl#print
>   Working on: /home/wbrooks/box/work/foo/helloworld.docbook
>   This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
>   (Fatal format file error; I'm stymied)
> 
> So it looks like the correct version of the DTD and stylesheets are
> getting used for this document, but it can't get pdfTeX to even begin
> generating a .pdf file.

Right. It's a TeX problem, not a DocBook problem.

> > If you volunteer to update the web pages, to me you're welcome ;-).
> > Mark?
> 
> Absolutely, I can either mail a patch to the existing web page or change
> something in a CVS repository somewhere.

Let's wait for Mark's answer.

> > TeX classical problem. The default configuration files do not allow
> > enough resources for docbook.
> > [...]
> >
> > I think we have a corrected version on the web site. Attached is also a
> > patch we use at KDE.
> 
> My texmf.cnf file is substantially different than yours so applying the
> patch failed. Can you send the whole file? Thanks in advance.

The patch is not big and easy to read, so you can patch by hand. On the
contrary, if you get my file, it might break other things on your
machine.

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/