feature: avoid conflict with Pandoc markdown's subscript

[Dupond]

Did you check the tree-sitter docs?

• I have read all the tree-sitter docs if it relates to using the parser

Is your feature request related to a problem? Please describe.

Hello!

In Pandoc's markdown "subscripts may be written by surrounding the subscripted text by ~ characters".

This parser implements Github's markdown; as a result, what is subscripted text in Pandoc appears as a strikethrough, which is quite confusing (for me ;)).

Describe the solution you'd like

Would there be any possibility for me (who's unfortunately not able to program it by myself) to avoid this behavior? For example, would it be possible to reserve the use of a single ~ sign for subscripts, and two ~ signs for a strikethrough?

Describe alternatives you've considered

As an alternative, would someone know of a parser for pandoc's markdown that would support highlighting?

Thank you very much for any help!

Additional context

No response