Hi Theno,
I have got your mail with examples and schema. Now I have understood what you want to do. I thought you did a mistake when have defined ASP style with include of
asp:normal.
I didn't make it with inherit because there are differences in keywords from the VB or VBS. Some keywords are written in wrong classes for example some methods were written in objects etc. So I would need to redefine all of the keywords even I inherit so I wanted to make a new syntax that includes all of the VB and VBS keywords in correct places and some new keywords classes too.
If you see that standard schemes for VB and VBS is incomplete or contain error, it is better to change them directly. Just send me your updates, if you think they are relevant for most users of VB and VBS and I will update them. So you will not need to redefine them.
Also there is a way to reuse keywords and block from other style syntax (I have forgotten this in FAQ, now updated):
inherit (any id of existing style with/without syntax prefix) – technical attribute, which tells to copy information from other style to this one. Copied are keywords, blocks, settings, but not containers. This is a better way than duplicate keyword sets. Example can be found in css_spec.xml (inherit="html:elements")
I made a new ASP syntax and added it into the HTML syntax. I tried to make a syntax like PHP and tried to implement it into HTML too like PHP.
Yes I see now what you want. Schemes are Ok, from first look. But adding *.asp to ASP schema will not work. Because you document base language is HTML you need to add
asp extension to HTML definition, as this done for PHP.
But better to go with inheritance way, if possible. You can use my schema, with inheritance from HTML, but when include ASP style use not standard VB/VBS schema but your extension. If it will not be possible to achieve with modification of standard ones.
I tried your syntax with 1.48 but scope problem continues. And If I can't define a new syntax for ASP this means I need to add all of keywords to your syntax and override the older ones.
Yes, I see the bug. I will fix it in new 1.48 beta.
I have checked your files with my schema (I have added vb:normal and vb:comment as close containers, post before has been updated) and have replaced all %> with {space}%> (in source files) and for me results were OK.