|
List Info
Thread: RE: RE: Using HTML profiling breaks olinks and HTML navigation
|
|
| RE: RE: Using HTML profiling breaks
olinks and HTML navigation |

|
2007-08-06 16:57:26 |
|
I take it back. Profiling is working fine
with profile-eclipse.xsl, and there are no conflicts with olinks.
It turns out that my batch file was using
too many command-line parameters, and therefore the last “conditionsR21;
argument wasn’;t being passed. Now that I fixed the batch file, everything’s
working fine.
Regards,
Jeff Powanda
From: Jeff Powanda
Sent: Sunday, August 05, 2007
10:53 PM
To: 'mj johanneberg.com';
'docbook-apps lists.oasis-open.org'
Subject: RE: Using HTML profiling
breaks olinks and HTML navigation
If I remove the following parameters, I
found that profiling works:
- olink.debug
- collect.xref.targets
- targets.filename
- target.database.document
However, if I remove those parameters,
all the olinks in my output are broken.
I guess I can try two-pass profiling to
get the job done, but I hoped one pass would work. Has anyone found a way to
profile Eclipse Help with olinks in one pass?
Regards,
Jeff Powanda
-----
Original Message -----
From:
Mauritz Jeanson <mj <at> johanneberg.com>
Subject: RE: RE: Using HTML profiling breaks olinks and HTML navigation
Newsgroups: gmane.text.docbook.apps
Date: 2007-08-03 20:18:19 GMT (2 days, 7 hours and 15 minutes ago)
> -----Original Message----- > From: Jeff Powanda > > 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. All profile-*.xsl stylesheets rely on the exsl:node-set() extension function. The author of xsltproc has his own (valid, as I understand it) opinion on how that extension can be safely implemented, and that might be causing the problem you are seeing (but this is just a wild guess).
You can try
1. Another XSLT processor, for example Saxon.
2. Two-pass profiling (using profiling/profile.xsl).
If this does not help, you need to provide a complete but minimal
test case
(including an input XML file) that can be used to reproduce the
problem,
using the stock stylesheets.
/MJ
|
[1]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|