Thanks Tobias, I will keep this in mind.
+1 we are also interested in having this work for SFTP connections.
Improper highlight for C directives
Improper highlight for C directives
Sure, makes sense.
Ideally the GitHub project would become part of an organization. Maybe hosted as part of the DocBook organization if anyone knows its admin?
Synchronize with pull request by Tony Graham on: https://github.com/docbook/xslt10-stylesheets/pull/182
Try to avoid breaking the entire XSLT processing when highlighter breaks:
Try to avoid breaking the entire XSLT processing when highlighter breaks:
You seem to have added a separate issue for your unhandled exception and it is not related with this current issue: https://sourceforge.net/p/xslthl/bugs/14/ I comitted a fix also for that issue, but I did not look at your attached patch, if you have another idea about how to make this work maybe we can talk on that issue.
Guard against case when the Java code is incomplete:
@kosek I added a fix for the issue + test case.
Added fix for SIOB for issue: https://sourceforge.net/p/xslthl/bugs/15/
Thanks. I made some changes, fixed about 4 broken links.
Home
Home
Home
Home
Where did you encounter that link? On what html page?
Avoid string index out of bounds, fix + TC.
Work on special JSON highligher.
Removed extra unnecessary patch, use Java proxy instantiation to create dummy object.
Thanks for the hint, I committed an update to the "java-hl.xml" from the SVN repository of the project.
Two more Java keywords per patch:
Linking to the discussion Bob Stayton started on the Docbook Apps list: https://lists.oasis-open.org/archives/docbook-apps/201708/msg00007.html One more thing I discovered and added on the same forum thread: https://www.oxygenxml.com/forum/viewtopic.php?f=6&t=14812&p=43711#p43722 Even if you set UTF-8 encoding by default Saxon 6 will still escape all special characters for "html" output. It has a special "saxon:" namespaced attribute which can be set on the xsl:output to avoid this but for some reason...
Default encoding for HTML-based outputs
Besides older versions of Saxon 9.1 the highlig...
Test commit rights.
Thanks Norm.
It seems that because I used XML elements most of my post is gone and it also seems...
Issues with Docbook 5.1 CR3 RNG-based schemas
Connector works also with Saxon 9.6
Code block marked as containing CSS (but actually contains XML) breaks processing
Guarded NPE + added TC
https://sourceforge.net/p/xslthl/bugs/11/
XSLTHL breaks processing XML fragment (String Index out of Bounds)
Committed TC + small fix.
https://sourceforge.net/p/xslthl/bugs/12/
Committed Saxon EE connector.
Add support for XSLT extension to work with latest Saxon EE processor
https://sourceforge.net/p/xslthl/bugs/10/
XSLTHL breaks processing XML fragment (String Index out of Bounds)
Code block marked as containing CSS (but actually contains XML) breaks processing
Add support for XSLT extension to work with latest Saxon EE processor
Word to DITA no longer works [D4P 0.9.19RC12]
Hi Bertrand, Thanks for the answers, I will look more into this when a stable DITA...
Missing DTDs from "net.sourceforge.dita4publishers.doctypes\doctypes\d4p_simpleEnumerationDomain\dtd" [0.9.19RC12]
Common CSS commonltr.css not included in EPUB, Kindle outputs [0.9.19RC12]
Method "relpath:getParent" does not properly work on Windows
If that error is corrected the output breaks again later on: D:\projects\eXml\frameworks\dita\DITA-OT\build.xml:53:...
The XSL: DITA-OT\plugins\net.sourceforge.dita4publishers.graphviz\xsl\map2graphvizImpl.xsl...
Graphviz output no longer works (D4P 0.9.19RC12)
The TC would be something like: String in = "<html><p>\uD840\uDC00</p></html> ";...
Surrogate characters handling in XHTML importer
All these build files: build_transtype-html2_template.xml build_transtype-kindle_template.xml...
Coming back to the XSL I mentioned earlier: "xsl\html\pi.xsl" in the template: <xsl:template...
References with dbhtml-include PI are not interpreted relative to XML when using profiling-docbook.xsl