https://saxonica.plan.io/https://saxonica.plan.io/favicon.ico2023-04-19T15:25:40ZSaxonica Developer CommunitySaxon - Support #5980: Should setting parser property affect XsltCompiler?https://saxonica.plan.io/issues/5980?journal_id=235682023-04-19T15:25:40ZMichael Kaymike@saxonica.com
<ul></ul><p>The standard parse options set at configuration level are not used when parsing stylesheets because we want to have more control: for example we force schema and DTD validation to be off and line numbering to be on.</p>
<p>If you use the API <code>XsltCompiler.compile(Source)</code> then you can supply an <code>AugmentedSource</code> which contains parse options, and these will be used largely unchanged; except that some options will be force-set, see <code>StylesheetModule.makeStylesheetParseOptions()</code>.</p> Saxon - Support #5980: Should setting parser property affect XsltCompiler?https://saxonica.plan.io/issues/5980?journal_id=235772023-04-20T09:53:44ZMartin Honnenmartin.honnen@gmx.de
<ul></ul><p>Thanks, Mike, that makes sense.</p> Saxon - Support #5980: Should setting parser property affect XsltCompiler?https://saxonica.plan.io/issues/5980?journal_id=244732023-08-06T16:34:42ZMichael Kaymike@saxonica.com
<ul></ul><p>This came up again in <a class="issue tracker-1 status-7 priority-2 priority-default closed" title="Bug: XML Reader seems to be reused instead of re-creating (Resolved)" href="https://saxonica.plan.io/issues/6152">#6152</a>. The documentation is very poor at explaining exactly what is affected when you set parser options at configuration level. The problem is that there are about 100 places that do use the Configuration's parser options, and plenty of others that don't, which makes it very difficult to make any kind of definitive statement; it also means that any changes we make to try and rationalise things are almost certain to break something.</p>