On 6/21/2012 7:29 PM, Lex Trotman wrote:
On 21 June 2012 23:52, ping <[email protected]> wrote:
thanks.
so it is the server issue I assume.
are there known workaround?
Hi,
Such advice is really beyond the scope of this ML. You would be more
likely to get help asking on the server software website, but if it is
beyond end-of-life I suspect their answer will be the same, upgrade.
Cheers
Lex
currently I can only generate a pdf instead of html as a workaround...
unfortunately the server is company IT owned gear and chances are slim that
they can upgrade it for me.
regards
ping
On Wednesday, June 20, 2012 1:05:32 PM UTC-4, wb wrote:
On Wed, 20 Jun 2012, ping wrote:
I got the server version, in case it is the server issue:
4.6.2-RELEASE FreeBSD 4.6.2-RELEASE #0: Wed Aug 14 21:23:26 GMT 2002
The 4.x branch of FreeBSD went end-of-life five years ago. It's
possible the server is running an equally outdated web server that can't
handle the Javascript or other features used in the TOC.
And it might not be that, but certainly that server is due for an
upgrade to at least FreeBSD 8, and the applications on it updated.
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/asciidoc/-/hburqiyxwEgJ.
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.
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.
thanks!
regards
ping
--
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.
