✨ feat(markdown): add standardize function for Telegram MarkdownV2

[sudoskys]

No description provided.

[sudoskys]

@Ste1io
An Invite has been sent.

You can test the new changes.
After initial testing it works fine on my pc

[Ste1io]

@Ste1io An Invite has been sent.

You can test the new changes. After initial testing it works fine on my pc

Looks good to me. Good idea with using two functions. 👍 I rebased and added the bold/italics fix, see #71

[sudoskys]

@Ste1io

telebot.apihelper.ApiTelegramException: A request to the Telegram API was unsuccessful. Error code: 400. Description: Bad Request: can't parse entities: Can't find end of Bold entity at byte offset 3676

Something seems to have gone wrong, let me check...

[sudoskys]

Sample:

*bold _italic bold ~italic bold strikethrough ||italic bold strikethrough spoiler||~ __underline italic bold___ bold*

After standardize

*bold _italic bold ~italic bold strikethrough ||italic bold strikethrough spoiler||~ _underline italic bold__ bold*

__underline italic bold___ -> _underline italic bold__

refused by Telegram server

[Ste1io]

telebot.apihelper.ApiTelegramException: A request to the Telegram API was unsuccessful. Error code: 400. Description: Bad Request: can't parse entities: Can't find end of Bold entity at byte offset 3676

Ah yes, that was a pre-existing bug, but hadn't surfaced prior, due to the fact that the md string variable was never being processed or sent to telegram; only printed to console (preprocessed). I encountered it when I first cloned the project and ran the test after noticing that the string was not actually being parsed and adding it myself; it is related to the bug mentioned in my comment in #68 regarding nested tokens:

Finally, the documented behavior of closing multiple nested entities is not being handled when parsing the syntax tree (eg, using the empty bold entity to separate the closing underline from the closing italic entities: __**_*).

I'll take a look at it today; I have a PR I'm about to push anyway fixing the ||spoiler|| rendering (which was inadvertantly removed from markdown rendering during the refactor), and the __underline__ rendering which was still using the previous token character check for markdown resulting in italics formatting in the new telegram rendering class.

I have created a separate issue for this (#72) as the fix may be a little more involved than I had hoped due to the telegram parsing grammar rules. Either they didn't put a lot of thought into their markdown v3 format spec when they wrote it, or there's a very good reason markdown hasn't pursued adding it to theirs. Or both. 😅