[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [docbook-apps] Antenna House bug and Indexes
Ah, I'm still on 1.68.1. I'll try again with the newer version. > -----Original Message----- > From: Bob Stayton [mailto:bobs@sagehill.net] > Sent: Tuesday, March 07, 2006 2:03 PM > To: Andrew Savikas; docbook-apps@lists.oasis-open.org > Subject: Re: [docbook-apps] Antenna House bug and Indexes > > What version of the DocBook XSL stylesheets are you using? > The processing I was describing using the inline.or.block > template was added in version 1.69.1. > > Bob Stayton > Sagehill Enterprises > DocBook Consulting > bobs@sagehill.net > > > ----- Original Message ----- > From: "Andrew Savikas" <andrews@oreilly.com> > To: <docbook-apps@lists.oasis-open.org> > Sent: Tuesday, March 07, 2006 10:53 AM > Subject: RE: [docbook-apps] Antenna House bug and Indexes > > > > Here's a sample of what results in the weird line breaking: > > > > <sect1 role="" id="xpathpointer-CHP-1-SECT-1" label="1.1"> > > <title>Why XPath and XPointer?</title> > > <para>Detailed answers to the following > > <indexterm > id="IXT-1-230748"><primary>XPath</primary><secondary>reasons to > > use</secondary></indexterm> > > <indexterm > id="IXT-1-230749"><primary>XPointer</primary><secondary>reasons > > to > > use</secondary></indexterm>questions are implicit throughout > this > > book and explicit in a couple of spots: > > </para> > > </sect1> > > > > Regardless of actual whitespace in the XML, the line *always* > breaks just > > before the first <indexterm> (after the word "following"). > > > > Thanks, > > Andrew Savikas > > > > > -----Original Message----- > > > From: Bob Stayton [mailto:bobs@sagehill.net] > > > Sent: Tuesday, March 07, 2006 1:38 PM > > > To: Andrew Savikas; docbook-apps@lists.oasis-open.org > > > Subject: Re: [docbook-apps] Antenna House bug and Indexes > > > > > > Yes, there is a problem with hard coding $wrapper.name to > > > fo:inline. An indexterm can appear between two para > elements. > > > Such an indexterm would generate an fo:inline outside of a > > > fo:block, which would cause the FO processor to fail. The > > > template named inline.or.block should return the correct > > > choice of wrapper for each container element. But it sounds > > > like it is missing one. Can you provide an example of your > > > XML markup? > > > > > > Bob Stayton > > > Sagehill Enterprises > > > DocBook Consulting > > > bobs@sagehill.net > > > > > > > > > ----- Original Message ----- > > > From: "Andrew Savikas" <andrews@oreilly.com> > > > To: <docbook-apps@lists.oasis-open.org> > > > Sent: Tuesday, March 07, 2006 10:27 AM > > > Subject: [docbook-apps] Antenna House bug and Indexes > > > > > > > > > > Hello, > > > > > > > > When using AntennaHouse with axf extensions enabled, I was > > > getting strange > > > > behavior on the first line of paragraphs that followed a > > > <title> and > > > > contained an <indexterm> near their beginnings. > > > > > > > > For example, instead of: > > > > > > > > Foo The Bar > > > > The quick brown fox jumps over the lazy dog. > > > > The quick brown fox jumps over the lazy dog. > > > > > > > > I was getting: > > > > > > > > Foo The Bar > > > > The quick brown fox > > > > jumps over the lazy dog. The quick brown fox > > > > jumps over the lazy dog. The quck brown fox > > > > > > > > So the first line of the paragraph after a <title>, if it > > > contains an > > > > <indexterm>, breaks well before it should. > > > > > > > > Disabling axf extensions alleviated the problem, but of > course > > > then I lost > > > > my PDF bookmarks. > > > > > > > > I looked at fo/index.xsl, and noticed the variable > > > "wrapper.name" in the > > > > "indexterm" template, along with the comment about it being > a > > > workaround for > > > > a bug in AntennaHouse. And indeed, when I disable the axf > > > extensions, then > > > > my index has no page numbers (well, all 0), so I assume > that's > > > the bug > > > > referred to. > > > > > > > > So on the one hand, if I enable the extensions, I get a > correct > > > index, but > > > > weird line breaks after titles, and if I disable the > > > extensions, then I get > > > > OK line breaks, but a bum index. > > > > > > > > As an experiment, I changed the value of $wrapper.name to > > > "fo:inline", and > > > > that appears to solve both issues -- there's no weird line > > > breaks, and I get > > > > correct index page numbers. Is there anything problematic > with > > > this approach > > > > that I'm not aware of? (I'm fairly new to FO.) If it's a > > > reasonable > > > > approach, then I hope it helps others who might be having > the > > > same problem. > > > > If not, please let me know so I can fix my stylesheets > > > accordingly. > > > > > > > > Thanks, > > > > Andrew Savikas > > > > O'Reilly Media, Inc. > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------- > > > ------ > > > > To unsubscribe, e-mail: > > > docbook-apps-unsubscribe@lists.oasis-open.org > > > > For additional commands, e-mail: > > > docbook-apps-help@lists.oasis-open.org > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------- > ------ > > > To unsubscribe, e-mail: > docbook-apps-unsubscribe@lists.oasis-open.org > > > For additional commands, e-mail: > > > docbook-apps-help@lists.oasis-open.org > > > > > > > > > > > > > > --------------------------------------------------------------- > ------ > > To unsubscribe, e-mail: > docbook-apps-unsubscribe@lists.oasis-open.org > > For additional commands, e-mail: > docbook-apps-help@lists.oasis-open.org > > > > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]