OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] Re: why does qandaset suck so badly?


Resending to the list (why does this ML just send it to the original 
poster only by default?)

Glen

Glen Mazza wrote:

> Igor Rosenberg wrote:
> 
>> Hello there!
>> I'm experiencing the same problems, namely quandaset exhibiting some 
>> fop bug. It seems to happen on quandasets with several entries. Where 
>> should I report the error?
>>
>> BUG description
>> 1) create a docbook file with lots of qandaentry in the same 
>> qandaset/qandadiv
>> 2) run the ant xslt task to generate fo output, then run the fop task.
>> 3) usual output :
>> org.apache.fop.apps.FOPException: file:/home/me/Manual.pdf.fo:8367:262 
>> The id "N156DD" already exists in this document
>>
>> And forcing unique ids into every single tag of the docbook xml does 
>> not change the problem. The id which fop tries to regenerate is used in
>>   <fo:list-item-label end-indent="label-end()" id="N156DD">
>>
>> Bob Stayton wrote:
>> ---------------
>> First I'll ask the obvious question: did you cut and paste a quandaentry
>> which already had an id attribute, thereby creating a duplicate id in 
>> your
>> document?
>>
>> If not, then you might peek in the fo file to see where the id="N1000F"
>> occurs, as that might provide some clues as to what is going on.  If 
>> there
>> is only one such id value, then FOP is exhibiting a bug.  
> 
> 
> True, FOP is exhibiting a bug here (it erroneously duplicates the ID in 
> certain circumstances), but it is one that is easily fixed via Docbook 
> customization.
> 
> This has happened to us for qandaset, the solution was as follows:
> 
> 1.)  Confirm that there is only *one* id="N10???" in the FO, as Bob says.
> 
> 2.)  Determine precisely which FO element has the "id" property added to 
> it.
> 
> 3.)  Override the qandaset in your foCustomization.xsl file, *removing* 
> the part that generates the "id" property for the formatting object 
> *under qandaset* (not globally) in question (it may end up being for two 
> or three FO's under qandaset.)
> 
> qandaset should work fine for you after this, because the stylesheet 
> will no longer generate any ID's for the elements in question under this 
> tag, hence creating no duplication.
> 
> Glen
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]