-
Notifications
You must be signed in to change notification settings - Fork 93
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
Parse .ent
and .mod
files as DTD files
#380
Comments
Perhaps lsp4xml should provide a preference for thoses DTD file extensions? |
Yes sure but it's a little hard to do that because there are synatx coloration to manage in vscode, etc. After reading some documentation, it seems there are 3 extensions (as you said):
We need to support those extension |
For syntax coloration, we need wait for accept of my PR for vscode microsoft/vscode#77496 |
See #380 Signed-off-by: azerr <[email protected]>
See eclipse-lemminx/lemminx#380 Signed-off-by: azerr <[email protected]>
See #380 Signed-off-by: azerr <[email protected]>
See #380 Signed-off-by: azerr <[email protected]>
See #380 Signed-off-by: azerr <[email protected]>
See eclipse-lemminx/lemminx#380 Signed-off-by: azerr <[email protected]>
.ent
and .mod
files should be parsed as DTDs
.ent
and .mod
files should be parsed as DTDs.ent
and .mod
files as DTD files
DTDs frequently modularize long lists of entities using external files with the
.ent
extension. These should get syntax-checked as DTDs as well.Technically, any extension can be used for this purpose; I've also seen
.mod
.The text was updated successfully, but these errors were encountered: