[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK-APPS: callouts and spacing with fo
/ David Cramer <david_cramer@broadjump.com> was heard to say: | Actually, I've ruled out tabs as the problem (tested it again after doing an | untabify on the whole buffer), as well as my original theory about < vs. | <. I've simplified the test further (see below). The result is the same: | lineone is correct. In the case of linetwo-linefive, in the .fo output, I I'm now pretty confident that this is a FOP problem. The attached zip contains my test document (derived from yours) and three PDFs: FOP, TeX, and XEP. Only the FOP PDF is wrong. And when I look in the FO file, I see no reason why subsequent programlisting lines are indented. | I'm using Apache fop 0.17.0. I couldn't tell if they support pngs, but it | looks like it supports gifs. In both cases, when I run it, it reports: | Error while creating area : no protocol: ../images/callouts/1.png... | or for gifs: | Error while creating area : no protocol: ../images/callouts/1.gif... This is also a FOP bug. It appears not to support relative URIs in external-graphic. | I'm mystified. In some ways, I like the idea of using <co id="foo"/> better | in the listing, but I can't get those to work with Saxon or Xalan-c. It's a | big help just to hear that programlistingco is supposed to work with fo | (they work fine for me with html). I'm just not sure what to try next. In what way do <co id="foo"/> elements not work in Saxon or Xalan-C?
Be seeing you, norm -- Norman Walsh <ndw@nwalsh.com> | A man can believe a considerable http://www.oasis-open.org/docbook/ | deal of rubbish, and yet go about Chair, DocBook Technical Committee | his daily work in a rational and | cheerful manner.--Norman Douglas
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC