Title: [Bug] RTL Punctuation Issue in System Dialogs & Card Numbers

Open
  • Is something wrong?
#405 13 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@an1ndra is already working on this.

Since Nov 6, 2026.

  • #428 by @an1ndra — open
  • #432 by @an1ndra — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

Research direction

The issue does not name files or tests. Start by locating the Compose UI for the Card Number label and the cited system dialogs, then inspect their behavior in RTL mode. Done means the card number stays on one line and punctuation appears in the correct sentence position in those dialogs.

Written by the indexing model from the issue text.

Description

rtl

Hi an1ndra,

I hope you are doing well.

First, I want to say that because your application is truly great and highly functional, my friend considers it the number one app on GitHub! I, as a user, wish for this app to be the best on GitHub without the slightest weakness.

I just wanted to leave a quick note here. I'm really looking forward to the next version.

Also, just a gentle reminder: whenever you decide to make changes to the UI in the future, please keep two small things in mind:

  1. The "Card Number" issue (it would be great if it could stay on one line without breaking).
  2. The punctuation marks (? and .) in some system dialogs (like the "Set as default SMS app" or "Back up without a PIN" windows) are still pushed to the beginning of the sentence in RTL mode.

But no pressure at all! Thanks again for all your efforts.🌹

Image Image Image Image
Dominant language
Kotlin
Stars
44
Forks
5
Avg merge
14h 15m
Merged PRs (30d)
69

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from an1ndra/Messages

All issues in an1ndra/Messages

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.