On linux there is a tool called xsltproc which takes an XSL and XML and outputs the transform.
It also shows context around errors.
I've found this most useful when I'm developing as I can test the result of my changes without the need to have a development server up and running. It just works.
However, I've noticed that the results of the transform can differ from that of Chrome for example. I don't know why this is, whether my transform was non-conforming, if Chrome is non-conforming, or if xsltproc is non-conforming.
EDIT My comment about differences between Chrome and xsltproc rendering the transform slightly differently is likely invalid.
I had modified the XML schema somewhat, and since then, xsltproc was generating tags (based on type name of types in the schema) correctly, but Chrome was not.
I was doing hard reloads to avoid Chrome reusing the cache.
I could tell Chrome was using the new xsl as there was other changes included that were being rendered.
Only the schema related tests were not working in Chrome for some reason.
I've since found that now it is magically working, with no changes to the xsl, just on a different day.
So I guess some part of the xsl was being cached somehow (perhaps just the schema bit - totally guessing here)... hence why some debugging in Chrome would be super nice.
发布评论
评论（2）
xsl:include来消除路径问题xsl:include语句input用于打印xsl:variable值的标记。xsl:includeto eliminate path issuesxsl:includestatements referencing buggy templatesinputtags to printxsl:variablevalues.在 Linux 上，有一个名为 xsltproc 的工具，它接受 XSL 和 XML 并输出转换。
它还显示错误周围的上下文。
我发现这在开发时最有用，因为我可以测试更改的结果，而无需启动并运行开发服务器。它就是有效的。
但是，我注意到转换的结果可能与 Chrome 的结果不同。我不知道为什么会这样，我的转换是否不合格，Chrome 是否不合格，或者 xsltproc 是否不合格。
编辑 我对 Chrome 和 xsltproc 之间的差异（渲染转换略有不同）的评论可能是无效。
所以我猜想 xsl 的某些部分以某种方式被缓存了（也许只是模式位 - 完全在这里猜测）...因此为什么 Chrome 中的一些调试会非常好。
On linux there is a tool called xsltproc which takes an XSL and XML and outputs the transform.
It also shows context around errors.
I've found this most useful when I'm developing as I can test the result of my changes without the need to have a development server up and running. It just works.
However, I've noticed that the results of the transform can differ from that of Chrome for example. I don't know why this is, whether my transform was non-conforming, if Chrome is non-conforming, or if xsltproc is non-conforming.
EDIT My comment about differences between Chrome and xsltproc rendering the transform slightly differently is likely invalid.
So I guess some part of the xsl was being cached somehow (perhaps just the schema bit - totally guessing here)... hence why some debugging in Chrome would be super nice.