-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xinclude schema validation issues #845
Comments
I think it is a bug with file association, because if you remove the file association and you use xml-model processing instruction it is working (you don't have those errors), BUT you have new errors because of 2 I think.
I don't know how to fix that for the moment, but you have the same error when you open the ptx root file (see my screenshot). XINclude is for the moment experimental, we need to find some time to improve it. I will fix the file association problem at first. |
I will provide soon a fix for that.
In docbook there is the same idea, you can declare a |
|
@oscarlevin the PR eclipse-lemminx/lemminx#1421 has been merged. Tomorrow you could install the prerelease and it should fix your issue with DOCTYPE. |
Thanks @angelozerr . I'll check that out. Assuming that works, I think we can close this. I've figured out how to add new elements to |
@oscarlevin could you try the prerelease and check if the issue 1 is fixed? |
Fixed with eclipse-lemminx/lemminx#1421 @oscarlevin if you find some issues with xinclude, please reopen it. |
I'm very thankful that vscode-xml now helps validate PreTeXt documents against it's RelaxNG schema. I have enabled the xinclude validation, and it does appear that the files included this way get checked as well. However, there are two issues.
The schema has start element
<pretext>
and the<chapter>
element is in the right place, but it is the root element ofch_intro.ptx
file.<xi:include />
, the root element of that "fragment" is not<pretext>
(it is usually<chapter>
or<section>
) so that gives a validation error (that the element is not allowed there.I understand that the 2nd issue might be impossible to really fix (apparently oXygen doesn't fix it), but perhaps the error can be made less severe in settings for the top element of any document. The first issue seems like a bug of the xinclude mechanism.
The text was updated successfully, but these errors were encountered: