Properly escape quotes with leading spaces

[Almighty-Satan]

Pull Request Etiquette

• I have checked the PRs for upcoming features/bug fixes.
• I have read the contributing guidelines.

Changes

• Internal code
• Library interface (affecting end-user code)
• Documentation
• Other: _____

Closes Issue: #2358

Description

Fixes an issue that caused quotes with leading spaces to not be escaped.

[SurfyDevelopment]

I've tested this, it seems like it escapes everything coming after the input string aswell, could you check?

[Almighty-Satan]

I've tested this, it seems like it escapes everything coming after the input string aswell, could you check?

I don't really understand what you mean by that. Could you please elaborate a bit?

[SurfyDevelopment]

Basically, what I am doing is:

Convert the markdown from Telegram for an automatic Discord message (announcement)

I am doing so by escaping the text and then convert the Telegram entities into Discord markdown.

ORIGINAL MESSAGE:

ESCAPING PRESENT DISCORD MARKDOWN ON THAT TEXT:

DEBUG ENTITIES:

Entitites get converted into discord markdown

OUTPUT STRING:

As you can see, in the output string everything was not being converted

Note:

This is how it gets sent on 5.0.0-beta2

[SurfyDevelopment]

After some more debugging I found out that the problem is that the escape actually replaces one space char instead of just adding the \ right before the quote, as shown:

ORIGINAL:

ESCAPED:

This is what ends up breaking my converter, the chars basically just don't add up.

[Almighty-Satan]

After some more debugging I found out that the problem is that the escape actually replaces one space char instead of just adding the \ right before the quote, as shown:

ORIGINAL:

ESCAPED:

This is what ends up breaking my converter, the chars basically just don't add up.

I think that should be fixed now

[SurfyDevelopment]

Tested, I can confirm it does in fact work properly now

DEBUG MESSAGE AFTER ESCAPING + CONVERSION:

[DV8FromTheWorld]

This needs tests.