Re: Large Debiandoc SGML and PS/PDF problem
Thanks Julien Beans. This seems to be a problem with Latex.
(I acccidentally erased your messasge, so I am responding to my original
Adam Di Carlo, (boot-floppies mainatiner) responded back to me
confirming that LATEX instability (bi-stable state) exists and
debiandoc2latexpdf's persisting problem with this. He does max. 6 level
recursive call in his Makefile to solve it in his boot-floppies package.
I will try Adam's trick in his package.
I wonder if there is some easy way out?
I also wonder which document processing backend platform shall be used
in woody for debiandoc processing. In potato, it is simple but I am
confused for Woody.
On Tue, Feb 19, 2002 at 01:42:13AM -0800, Osamu Aoki wrote:
> More info:
> On Mon, Feb 18, 2002 at 10:38:26PM -0800, Osamu Aoki wrote:
> > When I try to compile large Debiandoc SGML to PS or PDF, LATEX fails
> > due to error.
> > Source compiles no problem with text or html.
> > It looks like wide section <example>
> > Loooooooooooooooooooooooooooooooooooooooooooooonnnnnnnnnnnnnnggggggggggggg
> > line </example> causes too many \hbox width errors.
> > Is there any easy way to avoid failed build?
> > Source at DDP CVS :pserver:firstname.lastname@example.org:/cvs/debian-doc/ at
> > ddp/manuals.sgml/quick-reference .
> -v option results in ...
> Appendix A.
>  
> Appendix B.
> Overfull \hbox (142.97896pt too wide) in paragraph at lines 7339--7341
> \T1/ptm/m/n/10.95 The orig-i-nal SGML files used to cre-ate this doc-u-ment a
> re also avail-able in CVS at: \T1/pcr/m/n/10.95 :pserver:email@example.com.
>  (qref.en.aux)
> LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
> (see the transcript file for additional information)
> Output written on qref.en.dvi (156 pages, 312556 bytes).
> Transcript written on qref.en.log.
> debiandoc2latexps: ERROR: qref.en.dvi could not be generated properly
> make: *** [qref.en.ps] Error 1
> ?????????? What does anyone make out of this?
> + Osamu Aoki <firstname.lastname@example.org> @ Cupertino, CA USA +
+ Osamu Aoki <email@example.com> @ Cupertino, CA USA +