Uploaded jadetex 2.5-3 (source all) to master
pdfjadetex is still giving errors and doesn't seem to work
at all. However, since this is an improvement over the previous
version I am uploading it. If you need a working pdfjadetex,
I suggest you stick with 2.2-1.
The error message is included. TeX expertise is requested. The
upstream maintainer has been notified. No, I do not think this
really is a capacity limit problem but rather a bad recursion;
but I'd be happy to be proven wrong.
! TeX capacity exceeded, sorry [parameter stack size=4000].
\@lduseb@x #1->
\@lduseb@x {#1}\set@color
l.530 {0}}\Character{8226}\endLineField
{}\endSeq{}\Node%
! ==> Fatal error occurred, the output PDF file not finished!
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.5
Date: Tue, 27 Apr 1999 23:44:07 -0400
Source: jadetex
Binary: jadetex
Architecture: source all
Version: 2.5-3
Distribution: unstable
Urgency: low
Maintainer: Adam Di Carlo <aph@debian.org>
Description:
jadetex - LaTeX macros for SGML to DVI/PS/PDF conversion with Jade
Changes:
jadetex (2.5-3) unstable; urgency=low
.
* README.capacity_exceeded: up the stack size to 6000, from
J.H.M. Dassen (closes Bug#36615), raise a few other parameters that
have bit me recently
* jadetex.dtx: workaround bug, 'Incomplete \ifnum; all text was ignored
after line 1410'
* debian/rules: ship older babel from the 'cooked' subdir, fixing a
nasty interaction with newer tetexen (closes Bug#36614, Bug#36268)
Files:
5dc2ceb820f4421871fc6cbb3eb3dd00 610 tex optional jadetex_2.5-3.dsc
e3ca273524de73fcbfc4dd81210d717c 11062 tex optional jadetex_2.5-3.diff.gz
6e1a80fb1676045739818857237891aa 393272 tex optional jadetex_2.5-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
iQCVAwUBNyaHF4/8QF79WmfNAQES9QP8D1JEHQabQQtSrTpPB/VppksluyDakSLT
ywn3ymwpbiOnTm8UWLPSymy12CpeFsRcN/PnfFCRkSu5q9Txqc+4ZsV10TfPAtM+
N8tWUF52FWhYOvNI8Qma62kuOA5wMf4Jgq3mT3HgUYsMxkzPkdlHhYAMAYsyledo
XbAnmcaLW2o=
=Moyx
-----END PGP SIGNATURE-----
Reply to: