From: "Jonathan F. Dill" <jfdill@jfdill.suite.net>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: cvs tag release-19990824
Date: Thu, 26 Aug 1999 21:54:00 -0000 [thread overview]
Message-ID: <37C61A93.F41543C@jfdill.suite.net> (raw)
In-Reply-To: <76g119dsx4.fsf@odie.lanl.gov>
Awesome!
Perhaps this is premature, but I'm having problems with pdfjadetex--I
increased the stack sizes in texmf.conf per an old posting regarding
jadetex (plus I had to add a little more to param_size.pdfjadetex and
stack_size.pdfjadetex--See the diff vs. the "virgin" texmf.cnf at the
end of this message).
However, when I set param_size.pdfjadetex > 6000, db2pdf is still
bombing with "TeX capacity exceeded, sorry [parameter stack
size=6000]." I am not a TeX whiz--is that value being cropped due to
some other parameter? (the settings I used are listed in the diff at the
end)
Future docbook-tools wishes that I have:
1) db2X support for ugly "8.3" names eg. "*.sgm" works as well as
"*.sgml"--when I have the time, I may come up with a patch for that
2) Support to use TeX other than tetex if desired via the PATH variable
or some other mechanism, eg. I have TL4 installed, but I'm not sure
what's involved in getting the db2X scripts to use that TeX instead of
tetex--may be another simple patch
I also have a stupid db q to throw in here: I need to make the body of
a "book" double-spaced--I just copied cygnus-both.dsl and doubled
%line-spacing-factor% to 2.6 with the line:
;; increase the line-spacing-factor for double-space
(define %line-spacing-factor% 2.6)
However, I have an informaltable within the book, and that also gets
double spaced and it looks, frankly, stupid. Is there anything I can do
about this and still maintain the continuity of chapter and page
numbers? I read something in the DSSSL Cookbook v2 about "flexible
spacing" via mucking with "min-leading" but I don't quite grep the
concept of what I would need to do in the actual markup to take
advantage of it.
If this message doesn't spawn some "unsubscribe" messages posted to the
list, I don't know what will ;->
[root@mystery web2c]# rcsdiff -r1.1 -r1.3 texmf.cnf
===================================================================
RCS file: RCS/texmf.cnf,v
retrieving revision 1.1
retrieving revision 1.3
diff -r1.1 -r1.3
411a412,432
>
> % Patch to get PDF out of jadetex
> hash_extra.jadetex = 15000
> hash_extra.pdfjadetex = 15000
> pool_size.jadetex = 500000
> pool_size.pdfjadetex = 500000
> string_vacancies.jadetex = 45000
> string_vacancies.pdfjadetex = 45000
> max_strings.jadetex = 55000
> max_strings.pdfjadetex = 55000
> pool_free.jadetex = 47500
> pool_free.pdfjadetex = 47500
> nest_size.jadetex = 500
> nest_size.pdfjadetex = 500
> param_size.jadetex = 1500
> param_size.pdfjadetex = 9000
> save_size.jadetex = 5000
> save_size.pdfjadetex = 5000
> stack_size.jadetex = 1500
> stack_size.pdfjadetex = 9000
>
Regards,
--
"Jonathan F. Dill" (jfdill@jfdill.suite.net)
prev parent reply other threads:[~1999-08-26 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-24 9:50 Mark Galassi
1999-08-26 21:54 ` Jonathan F. Dill [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37C61A93.F41543C@jfdill.suite.net \
--to=jfdill@jfdill.suite.net \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).