-
Notifications
You must be signed in to change notification settings - Fork 3
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
External DTD Validation not working #8
Comments
Glad to hear you find it useful! Yeah, Exalt doesn't support SYSTEM identifiers at the moment. I'll see what I can do about that. |
@vaibhav-bansal: v0.3.2 should fix the issue. Can you try updating the plugin, restarting Sublime Text, and checking whether the issue is fixed for you? |
Thanks for the update and yes, it worked. |
By default, Exalt caches the schema for a document for performance reasons. You should be able to run the "Exalt: Clear Parser Cache" command after updating the DTD instead of restarting Sublime Text. Please let me know if that doesn't work, though. |
Yipee! It works perfectly. Thank you so much Sir!! |
Glad to hear it. I'll close this one, but feel free to comment if you discover any other aspects related to this issue. |
Exalt doesn't detect the external DTD file or maybe it detects but can't read the definitions in the file when I select Validate Document. It works perfectly with Internal DTD and XSD files.
And thank you for making this plugin. Really made my work easy.
1. Summary
Doesn't read the DTD definitions in the external DTD file.2. Expected Behavior
Should notify "Valid markup".3. Actual Behavior
Didn't read the definitions and notified "No declarations for element bookDB".4. Code Used
XML File- bookDB.xmlDTD File- bookDB.dtd
5. Environment
Operating System: Windows 8.1 x64 ENSublime Text: Build 3126
Thanks.
The text was updated successfully, but these errors were encountered: