[PR #534] [CLOSED] Telegram Gateway: Enabled MarkdownV2 parse mode and formatted the text #562

Closed
opened 2026-02-26 06:31:25 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/nextcloud/twofactor_gateway/pull/534
Author: @nudred
Created: 9/12/2022
Status: Closed

Base: masterHead: main


📝 Commits (1)

  • 6a409db Telegram Gateway Enable MarkdownV2 Parse Mode and Format Text

📊 Changes

64 files changed (+64 additions, -64 deletions)

View changed files

📝 l10n/af.json (+1 -1)
📝 l10n/ar.json (+1 -1)
📝 l10n/ast.json (+1 -1)
📝 l10n/bg.json (+1 -1)
📝 l10n/ca.json (+1 -1)
📝 l10n/cs.json (+1 -1)
📝 l10n/da.json (+1 -1)
📝 l10n/de.json (+1 -1)
📝 l10n/de_DE.json (+1 -1)
📝 l10n/el.json (+1 -1)
📝 l10n/en_GB.json (+1 -1)
📝 l10n/es.json (+1 -1)
📝 l10n/es_419.json (+1 -1)
📝 l10n/es_AR.json (+1 -1)
📝 l10n/es_CL.json (+1 -1)
📝 l10n/es_CO.json (+1 -1)
📝 l10n/es_CR.json (+1 -1)
📝 l10n/es_DO.json (+1 -1)
📝 l10n/es_EC.json (+1 -1)
📝 l10n/es_GT.json (+1 -1)

...and 44 more files

📄 Description

I made the changes as you requested

Now the messages in the Telegram will be formatted

However, I agree with you. You need to change the PHP code so that this formatting does not apply to other Gasteways

I would help change PHP, but I'm a Average Python Enjoyer 😄


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/nextcloud/twofactor_gateway/pull/534 **Author:** [@nudred](https://github.com/nudred) **Created:** 9/12/2022 **Status:** ❌ Closed **Base:** `master` ← **Head:** `main` --- ### 📝 Commits (1) - [`6a409db`](https://github.com/nextcloud/twofactor_gateway/commit/6a409db8a833a7b13b5c3d1c1fe0d6adfe5f42ad) Telegram Gateway Enable MarkdownV2 Parse Mode and Format Text ### 📊 Changes **64 files changed** (+64 additions, -64 deletions) <details> <summary>View changed files</summary> 📝 `l10n/af.json` (+1 -1) 📝 `l10n/ar.json` (+1 -1) 📝 `l10n/ast.json` (+1 -1) 📝 `l10n/bg.json` (+1 -1) 📝 `l10n/ca.json` (+1 -1) 📝 `l10n/cs.json` (+1 -1) 📝 `l10n/da.json` (+1 -1) 📝 `l10n/de.json` (+1 -1) 📝 `l10n/de_DE.json` (+1 -1) 📝 `l10n/el.json` (+1 -1) 📝 `l10n/en_GB.json` (+1 -1) 📝 `l10n/es.json` (+1 -1) 📝 `l10n/es_419.json` (+1 -1) 📝 `l10n/es_AR.json` (+1 -1) 📝 `l10n/es_CL.json` (+1 -1) 📝 `l10n/es_CO.json` (+1 -1) 📝 `l10n/es_CR.json` (+1 -1) 📝 `l10n/es_DO.json` (+1 -1) 📝 `l10n/es_EC.json` (+1 -1) 📝 `l10n/es_GT.json` (+1 -1) _...and 44 more files_ </details> ### 📄 Description I made the changes as you requested Now the messages in the Telegram will be formatted However, I agree with you. You need to change the PHP code so that this formatting does not apply to other Gasteways I would help change PHP, but I'm a Average Python Enjoyer 😄 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 06:31:25 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/twofactor_gateway-nextcloud#562
No description provided.