Hello David,
Thank you very much for your prompt and informative reply.
I changed the template definition to exclude footnote parents, as you
suggested -- xsl:template match=para[not(parent::footnote)] -- and it
worked like a charm[?].
Thank you also for the information regarding the mailing
Hi Larry.
Nice and more simple than adding some customization as I have done.
Will use this method, as it allows to change where the TOC is to be placed
dynamically (depending on the source document).
Thanks !
Regards,
Fabien
-Message d'origine-
De : Rowland, Larry
Hi List.
I am generating documents (article in DB terminology) and thus get some
bibliography to handle.
It works pretty well, except that, when I generate tables, the
bibliographic link gets split like
[
195
]
When the column is too narrow.
This occurs in HTML and FOP output, thus I assume the
I am trying to publish an ASP document. Most of it is working, but there are
two parts (both variation of the same thing) that are giving me a hard time.
I need to put
%@ Page language=VB AutoEventWireup=false
MasterPageFile=~/FANUCRoboticsMasterPageMeta.master Title=FLEXIBLE PART
FEEDING%
Jirka Kosek writes:
Jochen Hayek wrote:
So the multi-lingual refers to a couple of aspects, even not too seriously
connected issues:
1.) With the currenty stylesheets to create HTML from DocBook Website
documents:
would it be possible to extractconvert parts of the documents labeled
Hi,
I'm not able to duplicate this problem. The output to FO or HTML will have line feed
characters before and after the xref, because there are line breaks in the source
file. Because entry allows mixed content (mixing elements and text), those literal
line feed characters are preserved in
Hi Daniel,
Your first example works for me when I use xsltproc. Not clear why it doesn't for
you.
Your second example actually fails when I try to process it with xsltproc. I get this
error message:
xsltParseTemplateContent: xslt:text content problem
That isn't surprising, since
Hi Keith,
On the webhelp branch, I have it working so that it builds the java indexer and
generates the webhelp docs (which also serve to demonstrate what webhelp output
looks like). The one thing I still need to figure out is why the html files in
the doc directory are excluded from the
