Thanks. I downloaded DocBook XSL 1.73.0 and tried importing
profile-eclipse.xsl instead of eclipse.xsl in my customization layer,
but the conditions don't seem to work (that is, all DocBook elements
with condition attributes are excluded from the output). Is there
something else I need to do?
 
I'm using xsltproc to generate the output. I pass in the
profile.condition parameter to specify the condition(s) I want included
in the output:
 

call  %xsltproc_home%\xsltproc.exe --nonet --xinclude --stringparam
profile.condition %conditions% --stringparam olink.debug 0 --stringparam
collect.xref.targets no    --stringparam targets.filename
%doc_root%\%branch_id%\xml\%doc_id%_targets.xml --stringparam
target.database.document %olink_file% --stringparam current.docid
%doc_id% --stringparam eclipse.plugin.name %eclipse.plugin.name%
--stringparam eclipse.plugin.id %eclipse.plugin.id%
%tools_root%\myeclipse.xsl %doc_src%\%book_file%

 
Regards,
Jeff Powanda
 
________________________________


Subject: RE: [docbook-apps] RE: Using HTML profiling breaks olinks and
HTML navigation

*       From: "Mauritz Jeanson" <[EMAIL PROTECTED]> 
*       To: "'Jeff Powanda'" <[EMAIL PROTECTED]>,
<[email protected]> 
*       Date: Thu, 2 Aug 2007 20:56:28 +0200 

________________________________

size=2 width="100%" align=center> 
> -----Original Message-----
> From: Jeff Powanda 
> 
> BTW, I posted an earlier question about using profiling with 
> the Eclipse Help stylesheet but didn't receive a response. Is 
> it possible to get profiling to work for Eclipse Help output?
 
 
Yes. In DocBook XSL 1.73.0, there is a profile-eclipse.xsl stylesheet
(two-pass profiling works in earlier versions).
 
/MJ

 

Reply via email to