Description of Problem: How Reproducible: 100% Steps to Reproduce: 1. db2ps <filename> Actual Results: If I have a long directory path in a document it goes off the side of the page. Expected Results: Long pathnames should be split or put on a separate line so that they don't go off the edge of the page. Additional Information: Using docbook-utils-0.6-13. Will attach SGML file and resulting postscript.
Created attachment 22708 [details] bug.sgml
Created attachment 22709 [details] bug.ps
This problem goes away when this is commented out of /usr/share/sgml/docbook/utils-*/docbook-utils.dsl: ;;What quadding do you want by default; start, center, justify, or end? (define %default-quadding% 'justify) David, do you think that this is the correct solution? (docbook-utils.dsl is actually the GNOME stylesheet..)
I don't think that solves the problem across the board does it? I always understood this to be an odd TeX problem that Norman Walsh said was almost impossible to correct from the DSSSL side. If we see that more cases are corrected without the quadding we can change it though
Oh, okay, I see how that comes about. How about getting jadetex to put '\setlength\emergencystretch{2in}' at the beginning of its output? That way, in case of overfull hboxes, an extra stretchable length gets added to the end of the lines. To see, try this: $ docbook2tex bug.sgml $ echo '\setlength\emergencystretch{2in}' > fix.tex $ cat bug.tex >> fix.tex $ jadetex fix.tex; jadetex fix.tex; jadetex fix.tex $ dvips -o fix.ps fix.dvi Doing that gives me this result (attached). I wonder if there's some reason that jadetex doesn't already set \emergencystretch.
Created attachment 25431 [details] fix.ps
*ahem* I mean openjade of course, not jadetex.
thats exactly the issue I believe. I will ask Sebastian Rahtz the next time I see him online... I believe he is one of the people responsible
Right. Looking further into this actually I probably _do_ mean jadetex, since that's where this stuff should get set.
Created attachment 25551 [details] Here's the fix that I'm currently considering putting into jadetex.
I have applied this fix in jadetex-3.6-2.