Add support for converting from/to Telegram MarkdownV2 #617

Closed
opened 2026-01-29 14:41:15 +00:00 by claunia · 2 comments
Owner

Originally created by @Laiteux on GitHub (Aug 5, 2023).

(Idea)

https://core.telegram.org/bots/api#markdownv2-style

Originally created by @Laiteux on GitHub (Aug 5, 2023). (Idea) https://core.telegram.org/bots/api#markdownv2-style
claunia added the enhancement label 2026-01-29 14:41:15 +00:00
Author
Owner

@xoofx commented on GitHub (Aug 7, 2023):

I will decline. This is out of scope and can be developed outside of this repo (with maybe some markdig extensions) but it is also unclear if MarkdownV2 is actually a CommonMark compliant parser.

@xoofx commented on GitHub (Aug 7, 2023): I will decline. This is out of scope and can be developed outside of this repo (with maybe some markdig extensions) but it is also unclear if MarkdownV2 is actually a CommonMark compliant parser.
Author
Owner

@MihaZupan commented on GitHub (Aug 7, 2023):

This feels like something that could be exposed as part of https://github.com/TelegramBots/Telegram.Bot.
I'm pretty sure implementations of the "API representation => Markdown" conversion already exist. Feel free to ask in the telegram group of that project.

@MihaZupan commented on GitHub (Aug 7, 2023): This feels like something that could be exposed as part of https://github.com/TelegramBots/Telegram.Bot. I'm pretty sure implementations of the "API representation => Markdown" conversion already exist. Feel free to ask in the telegram group of that project.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/markdig#617