Re: DOCBOOK-APPS: Does JadeTeX work? ( Juan's response)
Adam Di Carlo [EMAIL PROTECTED] writes:
Kevin Dunn [EMAIL PROTECTED] writes:
From: Sebastian Rahtz [EMAIL PROTECTED]
its probably because the stylesheet puts the label on a containing
element which *does* start in page n-1
Yes, that's exactly what happens. And not just for the TOC and LOT,
any LINK or XREF to a table or figure will have the same problem.
Annoying. Can someone track down if this is the stylesheet's fault or
else perhaps the TeX backend on Jade or OpenJade?
I have tried to track it down some time ago. I'll attach the old mail
in case it helps you locate the problem:
From nobody Mon Sep 18 15:29:23 2000
To: Jade Devel [EMAIL PROTECTED]
Subject: Re: TeX backend fixed.
References: [EMAIL PROTECTED]
Organization: Open Systems Computing AS
From: Thomas Andre Berger [EMAIL PROTECTED]
Date: 18 Sep 2000 15:29:23 +0200
In-Reply-To: "Francis J. Lacoste"'s message of "Fri, 15 Sep 2000 18:00:39 -0400"
Message-ID: [EMAIL PROTECTED]
Lines: 148
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.6
"Francis J. Lacoste" [EMAIL PROTECTED] writes:
Hi,
I've finally fixed the pure virtual method called error !
You can download the new patch from
http://indev.insu.com/openjade/openjade-1.3-table.patch
The patch which has all the changes was updated as well :
http://indev.insu.com/openjade/openjade-1.3.patch
Please test those and give me feedback !
I can give you some output from our tex-file. I'm not sure of where
to start and end quoting, but I start somewhat before and after the
spots where the bug appears.
Some debug info for the "page-number" problem of mine.
[ Table of contents ]
One of the problematic enties is:
2.7. Shortcuts ... 25
2.6 and 2.7.1 is fine.
Here is that part of our tex:
{toc-page-number-mode}}\insertCurrentNodePageNumber%
{\def\Element%
{352}}\endNode{}\endLink{}\endPar{}\Par%
{\def\StartIndent%
{96\p@}\def\StartIndentFactor%
{0}\def\FirstLineStartIndent%
{-24\p@}\def\FirstLineStartIndentFactor%
{0}\def\fWeight%
{medium}\def\Quadding%
{start}}\Link%
{\def\Element%
{357}}\Seq%
{}\Seq%
{}\Seq%
{}2.7\endSeq{}. \endSeq{}\Node%
{\def\Element%
{358}\def\ProcessingMode%
{title-sosofo-mode}}Shortcuts\endNode{}\endSeq{}\endLink{}\Leader%
{}.\endLeader{}\Link%
{\def\Element%
{357}}\Node%
{\def\Element%
{357}\def\ProcessingMode%
{toc-page-number-mode}}\insertCurrentNodePageNumber%
{\def\Element%
{357}}\endNode{}\endLink{}\endPar{}\Seq%
{}\Par%
{\def\StartIndent%
{120\p@}\def\StartIndentFactor%
{0}\def\FirstLineStartIndent%
{-24\p@}\def\FirstLineStartIndentFactor%
{0}\def\fWeight%
{medium}\def\Quadding%
{start}}\Link%
{\def\Element%
{359}}\Seq%
{}\Seq%
{}\Seq%
{}2.7.1\endSeq{}. \endSeq{}\Node%
{\def\Element%
{360}\def\ProcessingMode%
{title-sosofo-mode}}Main Menu Shortcuts\endNode{}\endSeq{}\endLink{}\Leader%
{}.\endLeader{}\Link%
{\def\Element%
{359}}\Node%
{\def\Element%
[...]
and here is where the title of 2.7 is in the tex-file:
{356}}\Seq%
{\def\fWeight%
{bold}}Enter\endSeq{}\endNode{}.\endPar{}\endNode{}\endSeq{}\endDisplayGroup{}\endNode{}\Node%
{\def\Element%
{357}}\DisplayGroup%
{\def\StartIndent%
{48\p@}\def\StartIndentFactor%
{0}\def\sbNom%
{11\p@}\def\sbMin%
{11\p@}\def\sbMax%
{11\p@}\def\sbConditional%
{1}\def\saNom%
{11\p@}\def\saMin%
{11\p@}\def\saMax%
{11\p@}\def\saConditional%
{1}}\Seq%
{}\Seq%
{}\HeadPar%
{\def\fFamName{Arial}\def\fWeight%
{bold}\def\fPosture%
{upright}\def\fSize%
{19.008\p@}\def\LineSpacing%
{24.71\p@}\def\LineSpacingFactor%
{0}\def\StartIndent%
{0\p@}\def\StartIndentFactor%
{0}\def\FirstLineStartIndent%
{0\p@}\def\FirstLineStartIndentFactor%
{0}\def\Quadding%
{start}\def\HeadingLevel%
{2}\def\sbNom%
{14.256\p@}\def\sbMin%
{14.256\p@}\def\sbMax%
{14.256\p@}\def\sbConditional%
{1}\def\saNom%
{9.504\p@}\def\saMin%
{9.504\p@}\def\saMax%
{9.504\p@}\def\saConditional%
{1}\def\KeepWithNext%
{1}}2.7. \Node%
{\def\Element%
{358}\def\ProcessingMode%
{title-sosofo-mode}}Shortcuts\endNode{}\def\HeadingText{%
2.7. Shortcuts}%
\endHeadPar{}\endSeq{}\Node%
{\def\Element%
{358}}\endNode{}\Node%
{\def\Element%
{359}}\DisplayGroup%
{\def\StartIndent%
{48\p@}\def\StartIndentFactor%
Looks like that tex links to element number 357, and that is located
on page 25, but the title itself is element number 358, and TeX has
wrapped that to the next page.
Thanks for all your great work with openjade/jadetex!
--
Thomas A. Berger
--
Thomas André Berger Open Systems Computing AS
email: [EMAIL PROTECTED]Kongensgt. 9, N-0153 Oslo, Norway
phone +47 2220 4050, fax +47 22 20 02 85
http://www.osc.no/
Re: DOCBOOK-APPS: Does JadeTeX work? ( Juan's response)
On Sun, Mar 04, 2001 at 10:58:48AM +0100, Juan R. Migoya wrote: I'm using Jadetex 3.4, DSSSL 1.62 and Jade 1.2.1 and it works fine. Okay, but could I just confirm what you mean by "fine"? Specifically, can you tell me if you see any of these behaviours when you use JadeTeX: 1. Erroneous page numbers: when a figure or a section near the bottom of a page gets wrapped over to the next page, the page number in the Table of Contents/List of Figures is the previous page (n-1), not the actual page (n). 2. The DSSSL print stylesheet setting %two-side% is ignored. Or, in one-sided mode, extra blank pages appear at the end of chapters etc. 3. Page number restarts are ignored. So, instead of having small Roman pages in the front matter (i, ii, iii...) and restarted Arabic numbers in the body matter (1, 2, 3...), you just get Arabic numbers all the way through. If you can confirm that you don't encounter the above problems, then I agree that JadeTeX works "fine" for you. Thanks, David P.S.: I should tell you that RTF output works fine for me: It seems I only have a problem with JadeTeX.
Re: DOCBOOK-APPS: Does JadeTeX work? ( Juan's response)
David Nelson writes: 1. Erroneous page numbers: when a figure or a section near the bottom of a page gets wrapped over to the next page, the page number in the Table of Contents/List of Figures is the previous page (n-1), not the actual page (n). its probably because the stylesheet puts the label on a containing element which *does* start in page n-1 2. The DSSSL print stylesheet setting %two-side% is ignored. Or, in one-sided mode, extra blank pages appear at the end of chapters etc. thats fixed, or I am a chinaman, if you have the latest and greatest 3. Page number restarts are ignored. So, instead of having small Roman pages in the front matter (i, ii, iii...) and restarted Arabic numbers in the body matter (1, 2, 3...), you just get Arabic numbers all the way through. this is fixed in the version I have here. since someone introduced new macros into the output without telling me, I am not surprised it didn't work until today! sebastian
Re: DOCBOOK-APPS: Does JadeTeX work? ( Juan's response)
At 12:08 PM 3/5/01 +, Sebastian Rahtz wrote: 3. Page number restarts are ignored. So, instead of having small Roman pages in the front matter (i, ii, iii...) and restarted Arabic numbers in the body matter (1, 2, 3...), you just get Arabic numbers all the way through. this is fixed in the version I have here. since someone introduced new macros into the output without telling me, I am not surprised it didn't work until today! Yes, that is definitely fixed! It is great ... sebastian Regards --- Richard Sharpe, [EMAIL PROTECTED] Samba (Team member, www.samba.org), Ethereal (Team member, www.ethereal.com) Contributing author, SAMS Teach Yourself Samba in 24 Hours Author, Special Edition, Using Samba
Re: DOCBOOK-APPS: Does JadeTeX work? ( Juan's response)
I have looked again at the last manual I have done to be sure. Here are my answers: David Nelson wrote: On Sun, Mar 04, 2001 at 10:58:48AM +0100, Juan R. Migoya wrote: I'm using Jadetex 3.4, DSSSL 1.62 and Jade 1.2.1 and it works fine. Okay, but could I just confirm what you mean by "fine"? Specifically, can you tell me if you see any of these behaviours when you use JadeTeX: 1. Erroneous page numbers: when a figure or a section near the bottom of a page gets wrapped over to the next page, the page number in the Table of Contents/List of Figures is the previous page (n-1), not the actual page (n). Definitely not: I have sections (SECT!, SECT", etc...) wraped to the next page and the TOC points to the begining of the section. With list of figures and tables you are right: The list points to the previous page. 2. The DSSSL print stylesheet setting %two-side% is ignored. Or, in one-sided mode, extra blank pages appear at the end of chapters etc. It isn't ignored: I get diferent position for headers on odd than on even pages. The same for footers. The same for margins. 3. Page number restarts are ignored. So, instead of having small Roman pages in the front matter (i, ii, iii...) and restarted Arabic numbers in the body matter (1, 2, 3...), you just get Arabic numbers all the way through. Sorry: I don't use restart page feature. Regards, Juan R. Migoya If you can confirm that you don't encounter the above problems, then I agree that JadeTeX works "fine" for you. Thanks, David P.S.: I should tell you that RTF output works fine for me: It seems I only have a problem with JadeTeX.
Re: DOCBOOK-APPS: Does JadeTeX work?
I'm using Jadetex 3.4, DSSSL 1.62 and Jade 1.2.1 and it works fine. The only thing I had to change is the "oddleftmargin" and "evenleftmargin" in jadetex, to get it working with two-side (diferentes left margins for odd and even pages). Also, there were a question in this list just about your problem, some days ago. Sebastian replied saying that you should change "cleardoublepage" to "clearpage". Please check the archives because I have not this message here and I may be missing something. Regards, Juan R. Migoya David Nelson wrote: Hello everyone, This is a sincere question, I'd really like an answer: are you using JadeTeX? And if so, does it work for you? Because I've been using it, and I've found the results to be quite poor. Let me tell you the story of my woes. My system: Debian 2.2. I installed the stable packages for DocBook, DocBook stylesheets, Jade, JadeTeX, etc., and started work. HTML output was fine. I found the TeX output to be a bit ugly, but making a custom stylesheet helped. Then I started noticing problems. First, headings were appearing at the bottom of the pages, with their first paragraph breaking to the next page. Very ugly (but technically not incorrect). I searched this mailing list, and found that this was a bug which had been fixed. So, I installed the unstable JadeTeX package for Debian, and sure enough, the problem was solved. Next, I noticed that two-sided output was fine (headers footers aligned correctly; and \cleardoublepage at the end of chapters), but there was a problem with one-sided output: headers correct, but \cleardoublepage instead of \clearpage. So there were extraneous blank pages, which would be suitable for two-sided printing, but which were ugly superfluous for one-sided printing. So, I upgraded to the very latest version of JadeTeX (3.4), by downloading the sources, making a hugelatex.fmt, and compiling installing JadeTeX by hand. It worked, but the problem wasn't fixed. Then, I thought that maybe it was a problem with some of the other packages on my system. So, I upgraded to unstable docbook, docbook-stylesheets, and jade, and tried again. This is where it got interesting... The behaviour was REVERSED! Now, single-sided printing worked fine, but the two-side setting was ignored. You may think this was a bad custom style file, but it wasn't: I set other settings in my style file, and they worked okay. But two-sided printing was no longer possible. Then, I noticed another bug, which was not just annoying, it was a serious error. The page numbers were sometimes off, especially in the Table of Figures (ToF). For example: if a figure appeared near the end of page 7, but was wrapped around to page 8 because of its size, it would appear in the ToF as page 7, whereas it was really appearing on page 8. Bad, bad, bad. [snip...] Dave.
Re: DOCBOOK-APPS: Does JadeTeX work?
David Nelson writes: (stuff about double-sided) I lose track of all this. I just hope someone can analyze the problem and tell me what to fix Then, I noticed another bug, which was not just annoying, it was a serious error. The page numbers were sometimes off, especially in the Table of Figures (ToF). For example: if a figure appeared near the end of page 7, but was wrapped around to page 8 because of its size, it would appear in the ToF as page 7, whereas it was really appearing on page 8. Bad, bad, bad. interesting. I'd want to see some more proper analysis of what goes on there. I think you get the picture. In my experience, JadeTeX just doesn't work right, and I don't know why. Is it Jade, or JadeTeX, or the stylesheets, or the Debian setup, or me somehow? There are a lot of parts working together here, so I can't tell which one is broken. and from your description, I can't either. How about you? Does Jade + DSSSL + JadeTeX work okay for you? Or are you using something better? Would I be better off with something like OpenJade, or something else not DSSSL-based? it depends on what you are trying to do. for some things I would say this is a good route; for others I'd recommend a high-level transform to LaTeX; for others I'd say `make RTF and import to Word', etc etc I dont think we can do the analysis of your production process here... sebastian -- To unsubscribe from this elist send a message with the single word "unsubscribe" in the body to: [EMAIL PROTECTED]
DOCBOOK-APPS: Does JadeTeX work?
Hello everyone, This is a sincere question, I'd really like an answer: are you using JadeTeX? And if so, does it work for you? Because I've been using it, and I've found the results to be quite poor. Let me tell you the story of my woes. My system: Debian 2.2. I installed the stable packages for DocBook, DocBook stylesheets, Jade, JadeTeX, etc., and started work. HTML output was fine. I found the TeX output to be a bit ugly, but making a custom stylesheet helped. Then I started noticing problems. First, headings were appearing at the bottom of the pages, with their first paragraph breaking to the next page. Very ugly (but technically not incorrect). I searched this mailing list, and found that this was a bug which had been fixed. So, I installed the unstable JadeTeX package for Debian, and sure enough, the problem was solved. Next, I noticed that two-sided output was fine (headers footers aligned correctly; and \cleardoublepage at the end of chapters), but there was a problem with one-sided output: headers correct, but \cleardoublepage instead of \clearpage. So there were extraneous blank pages, which would be suitable for two-sided printing, but which were ugly superfluous for one-sided printing. So, I upgraded to the very latest version of JadeTeX (3.4), by downloading the sources, making a hugelatex.fmt, and compiling installing JadeTeX by hand. It worked, but the problem wasn't fixed. Then, I thought that maybe it was a problem with some of the other packages on my system. So, I upgraded to unstable docbook, docbook-stylesheets, and jade, and tried again. This is where it got interesting... The behaviour was REVERSED! Now, single-sided printing worked fine, but the two-side setting was ignored. You may think this was a bad custom style file, but it wasn't: I set other settings in my style file, and they worked okay. But two-sided printing was no longer possible. Then, I noticed another bug, which was not just annoying, it was a serious error. The page numbers were sometimes off, especially in the Table of Figures (ToF). For example: if a figure appeared near the end of page 7, but was wrapped around to page 8 because of its size, it would appear in the ToF as page 7, whereas it was really appearing on page 8. Bad, bad, bad. So, I thought to myself, "Time to revert back to the previous behaviour, and track down exactly what's going wrong." So I "downgraded" all relevant Debian packages, back to their stable versions. I tried again, but nothing had changed: the output was still locked into single-sided mode, and figures were still showing up under the wrong page in the Table of Figures. I think I'm now "stuckgraded"! It occurred to me that I should check an older .dvi file, which I had built before all this upgrading nonsense, to see that JadeTeX actually was behaving correctly before I upgraded. And NO, IT WASN'T! I hadn't noticed before, but THE PAGE NUMBERING WAS WRONG ALL ALONG. - I think you get the picture. In my experience, JadeTeX just doesn't work right, and I don't know why. Is it Jade, or JadeTeX, or the stylesheets, or the Debian setup, or me somehow? There are a lot of parts working together here, so I can't tell which one is broken. How about you? Does Jade + DSSSL + JadeTeX work okay for you? Or are you using something better? Would I be better off with something like OpenJade, or something else not DSSSL-based? Any advice would be appreciated. Dave.
