On 7/4/2012 12:49 AM, Lex Trotman wrote:
[...]
working with IT turn out to be no progress...they won't risk it with 1000+
employees are OK but only 1(me) is complaining...
But while keep reading, it looks I found some alternative to kind of
workaround this issue, without changing the server end.
so looks the TOC was generated by JS, are there a solution to bypass the
"dynamic TOC" generated by JavaScript code , but instead to generate "static
TOC"?
when I read more menu I found this:
http://www.methods.co.nz/asciidoc/userguide.html#_asciidoc_docbook_xsl_stylesheets_drivers
xhtml.xsl
Convert a DocBook XML file to a single XHTML file. For example:
$ python ../asciidoc.py -b docbook asciidoc.txt
$ xsltproc --nonet ../docbook-xsl/xhtml.xsl asciidoc.xml > asciidoc.html
so instead of generate html directly from asciidoc, do it from docbook
backend seems an alternative,
I'm feeling by this way we don't rely on the JS code to generate the TOC?
at least one of my webpage now displays correctly in the same server.
but at the moment this only give me a 2 level TOC and I can't generate a
deeper TOC, I tried this (-a toc -a toclevels=4) but no effect:
$ asciidoc -b docbook -a toc -a toclevels=4 asciidoc.txt
$ xsltproc --nonet ../docbook-xsl/xhtml.xsl asciidoc.xml > asciidoc.html
please advice.
Hi,
Remember that the XSLT is external to asciidoc so although we will
provide information if we know it, there is no guarantee of that. You
might be better asking those questions of that project.
Have a look at (from FAQ #3)
http://sagehill.net/docbookxsl/OptionsPart.html which describes the
options for XSL generated HTML.
Cheers
Lex
thanks!
regards
ping
after 1 hours searching/testing, feeling quite frustrated now..
I found some clues here, about the toc theory for xsltproc:
http://www.sagehill.net/docbookxsl/TOCcontrol.html
so it looks by default only 2 level toc was generated, exactly matching
what I see here.
but overall the article are talking about xml and options(elements) to
control the toc, without a commandline demonstrate HOW.
"
Use the toc.section.depth parameter to indicate how many levels of
section titles should appear in the TOCs. If you set it to a value of 3,
for example, then TOCs will include up to sect3 titles. The default
value is 2.
"
but then how??? I got following error anyway:
ping@640g-laptop:~/mx/RLI$ xsltproc --nonet
/etc/asciidoc/docbook-xsl/xhtml.xsl --stringparam toc.section.depth 3
RLI-12720.xml > RLI-12720.html
warning: failed to load external entity "--stringparam"
unable to parse --stringparam
warning: failed to load external entity "toc.section.depth"
unable to parse toc.section.depth
warning: failed to load external entity "3"
unable to parse 3
;
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/asciidoc?hl=en.
