TelegramMessenger / TelegramMessenger/Telegram-iOS
Inappropriate strikethrough view in buttons
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 9k
- Forks
- 2.9k
- PR merge metrics
- No merged PRs in 30d
Description
Checklist
- I am reporting an issue in existing functionality that does not work as intended
- I've searched for existing GitHub issues
Description
I have a menu with buttons, which can be strikethrough or usual
Before update to Telegram 6.1.2, it was looked as usual -> strikethrough worked correctly,
After update -> I understood that localization of these strikethrough numbers was changed and it isn't working appropriately.
As we know, buttons are not maintaining strikethrough text directly via "<s></s>", so I've used Unicode characters to make them as they should be:
Unicode Character 'COMBINING LONG STROKE OVERLAY' (U+0336)
0 -> "\u03360\u0336";
1 -> "\u03361\u0336";
2 -> "\u03362\u0336";
3 -> "\u03363\u0336";
4 -> "\u03364\u0336";
5 -> "\u03365\u0336";
...
etc.
But now it works inappropriately, bot outputs: <LONG_DASH>0<LONG_DASH>.
Expected Behavior
Strikethrough workes correctly,
Actual Behavior
Output of strikethrough changed to: <LONG_DASH>0<LONG_DASH>.
Screenshots and Videos


Environment
Device: iPhone/iPad X
iOS version: 13.X
App version: 6.1.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. Start by reproducing the menu-button behavior on iOS 13.x with Telegram 6.1.2, using the listed Unicode combining characters, then trace the localization or text-rendering entry point. Done means strikethrough digits render correctly instead of as LONG_DASH characters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- localization, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100