Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

The installation of jadetex does not increase the standard sizes of certain
buffers in 
TeX which causes jadetex and pdfjadetex to fail, with errormessages like the
following: 

! TeX capacity exceeded, sorry [save size=5000]. 
<to be read again> 
                   \relax 
l.6553 {} 
         12-\/4\endSeq{}. \endSeq{}\Node% 
!  ==> Fatal error occurred, the output PDF file is not finished! 
Transcript written on BlenderManual.log. 

This problem is know, and also decribed on the project homepage of jadetex 
http://jadetex.sourceforge.net/.  According to the jadetex webpage, the default 
memory settings of tetex are too small, see also 
http://www.redhat.com/mirrors/LDP/HOWTO/mini/DocBook-Install/install.html. 

This bug prevents users from compiling complex documents with jadetex (e.g.
complex 
docbook documents, that have been converted docbook2tex). 

Upgrading to the newest tetex (tetex-2.0.2). 

Reproducible: Always
Steps to Reproduce:
1. Convert a complex docbook file to jadetex (e.g. Blender documentation from 
www.blender.org) 
2. run jadetex or pdfjadetex on the resulting document 
3. 
Actual Results:  
pdfjadetex fails with error: ! TeX capacity exceeded, sorry [save size=5000]

Could you propose a solution ? Files/Number changes ? Thanks.

Reading jadetex.sourceforge.net it seems that all you have to do is add 40
lines to the bottom of /usr/share/texmf/web2c/texmf.cnf then regenerate the
latex.fmt file, before building jadetex. However I still get the "save
size=5000" error.

Even if the jadetex install did hack texmf.cnf, it would still have to redo it
whenever tetex was upgraded. Can gentoo cope with that?

In the short term the patch to texmf.cnf should go into the tetex ebuild rather
than jadetex.

Bob

Oops - jadetex.org recommended values have save_size=5000, so
it is not too surprising that we run out with save size=5000.
When I up that to 50000 it goes further (dies with
"TeX capacity exceeded, sorry [grouping levels=255]"). It
isn't obvious what to change to fix that.

At any rate the point remains that tetex should put bigger
values in texmf.cnf (as per jadetex.org or bigger). Getting
jadetex ebuild to update texmf.cnf will cause the change to
be lost whenever tetex is updated.

Bob

Sorry, I havent commented back.

I had quite a look at this bug when I was investigating jadetex just recently (in relation to sgmltools-lite) but I didnt come up with an effective, update-proof way to modify texmf.cnf. The basic situation is:

need to modify texmf.cnf
then remake jadetex.fmt/pdfjadetex.fmt

This isnt that hard to do, but choosing where (which ebuild/what time) is the critical thing I think.

The last option I came up with was, perhaps we could:

copy texmf to somewhere in ${D}
modify it and remake jadetex/pdfjadetex.fmt
install these modified versions

and do that all within the jadetex ebuild.

has this bug been resolved?

What I'm thinking now is to move texmf.cnf to /etc/texmf/texmf.cnf and make
a symink to /usr/share/texmf/web2c/texmf.cnf (so texmf.cnf will be
CONFIG_PROTECTED). Also, I suggest we create /etc/texmf/texmf.d, put parts 
of texmf.cnf into it, and generate texmf.cnf from them just like we create
site-gentoo.el from ??-*-gentoo.el for emacs.

After that, we can put (for example) 60jadetex.cnf on /etc/texmf/texmf.d and
remake jadetex.fmt/pdfjadetex.fmt.

It's not completely resolved but texmf.cnf in 
tetex-beta is config-protected, so things are 
better now....

It is now configurable by tetex-3.0 and /etc/texmf/texmf.d/80jadetex.cnf.
Sorry for taking so long time to fix it :(