This is to remind and propose (for anyone interested) that since EBNF grammar notations/specifications do not use JSON format, but a rather similar textual format, for example
EBNF
a_rule ::= symbol1
| symbol2
| 'literal symbol'
| ..
;
or even:
EBNF
a_rule ::= <symbol1>
| <symbol2>
| 'literal symbol'
| ..
;
Although it is rather straightforward to transform the above examples into a JSON grammar for highlight. It is even better to have a transformation tool for that.
Given that JSON grammar (as used by *-grammar highlighter add-ons) can accept and parse EBNF/PEG notation. The task is even easier. For example, just split each rule as rule_name => rule_definition and create a JSON-like object from that (more correctly the Syntax part of the overall JSON grammar).
This is to remind and propose (for anyone interested) that since
EBNFgrammar notations/specifications do not useJSONformat, but a rather similar textual format, for exampleEBNF
or even:
EBNF
Although it is rather straightforward to transform the above examples into a
JSONgrammar for highlight. It is even better to have a transformation tool for that.Given that
JSONgrammar (as used by*-grammarhighlighter add-ons) can accept and parseEBNF/PEGnotation. The task is even easier. For example, just split each rule asrule_name => rule_definitionand create aJSON-like object from that (more correctly theSyntaxpart of the overallJSONgrammar).