Please add more syntax highlighters (Pascal, EBNF)

[Eudox67]

Checklist

• Zettlr does not possess this feature (if it does, but the feature doesn't work out for you, propose an enhancement instead.)
• Zettlr's current features cannot be used to approximate this behaviour (otherwise, propose an enhancement instead.)
• I have searched the documentation to make sure I did not overlook it.
• I have searched both open and closed issues to see if someone has already proposed this.

Feature Proposal

The documentation asks us to propose languages for syntax highlighting. I would like as many as possible, but right now I am missing two crucial ones to help with parsing languages. One is EBNF/BNF, the other is Pascal (which a lot of parser examples utilize).

Thank you for this.

Example Workflow

Parsing is a difficult programming task. Parsing engines often are utilized to help with this. ANTLR, YCC/BISON, GOLD parsing engine etc. are tools that can be used to prevent the need for handwritten parsers. The documentation and examples utilize EBNF, BNF, and Pascal/Object Pascal is often used as an example language. To read the examples (which are extensive), it helps to have syntax highlighting--which is not available in Zettler.

Caveats

This is a simple syntax highlighting addition, no caveats.

Do you wish to attempt implementing this yourself?

No

Platforms

• Windows
• macOS
• Linux

Additional Information

No response

[boring-cyborg]

Thanks so much for opening up your first issue here on the repository! 🎉
We would like to warmly welcome you to the community behind the app! ☺️
We'll check in soon and have a look at your issue. In the meantime, you can
check your issue and make sure it aligns with our contribution guidelines!
Here's the comprehensive list:

NOTE: Please do not share screen captures of buggy behavior on YouTube.
If you have uploaded a video on YouTube and linked it already, don't
worry! But, we would like to ask you to remove the video from YouTube
and upload it directly to GitHub instead, by editing your comment.
Read more here.

Enhancements

An enhancement takes a feature and improves or alters its behaviour. Please
make sure to argue how your proposition will aid non-technical text workers,
and why it can't be emulated easily with other features or apps!

Feature requests

Feature requests introduce whole new features into the app. This requires a
lot of work, so these might be turned down if the implementation costs
supersede the benefits we expect to see from implementing it. Please do not
be disappointed if that happens. It likely has nothing to do with your great
request but simply with us and our missing resources!

You can of course always ask someone to implement this feature, because a PR
with a working new feature has much higher chances of being merged! :)

Bug reports

Please note that one of the main reasons for why bug reports cannot be
addressed is that there's not enough information for us to find and fix the
bug you describe, so make sure you try to pinpoint the bug as close as
possible.

The ideal bug report for us has two qualities:

1. The bug is always reproducible, at least within a certain context.
2. We know exactly what specifically goes wrong, and there is consensus on
   what should happen instead.

Please note that if you encounter behaviour that does not align with your
expectations of what would happen, this might as well be simply intended
behaviour and we need to simply clarify why the behaviour is the way it is.
This is not to be considered a bug and such issues may be closed! Suggest an
enhancement instead!

But now, have a great day and thank you again!