RocketChat / RocketChat/Rocket.Chat

Persian locale has missing Account settings translations

Open
#38,675 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

When using Persian (fa) in Account settings pages, several UI strings were still shown in English.
Also, when opening a select/multiselect with no options, it showed Empty in English.

Steps to reproduce:
  1. Set user language to Persian (fa).
  2. Open Account pages:
    • /account/profile
    • /account/preferences
    • /account/security
    • /account/tokens
    • /account/omnichannel
    • /account/accessibility-and-appearance
  3. In Preferences, open the “Don’t ask me again list” multiselect when there are no options.
  4. Observe untranslated strings and Empty label.

Video demo of the issue:

https://github.com/user-attachments/assets/4d47a920-68f6-491a-a95c-3b5a0fd21c7b

Expected behavior:

All Account settings UI strings are translated to Persian, including empty-state labels in selects/multiselects.

Actual behavior:

Some labels/descriptions were in English, and empty select state displayed Empty.

Server Setup Information:
  • Version of Rocket.Chat Server: develop (local)
  • License Type:
  • Number of Users:
  • Operating System:
  • Deployment Method:
  • Number of Running Instances:
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
Client Setup Information
  • Desktop App or Browser Version:
  • Operating System:
Additional context

Fix prepared in branch:
i18n/fa-account-translations-and-empty-select

Relevant logs:

N/A

Contributor guide

Open the 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.

Research direction

Start with the Persian locale resources used by the Account routes listed in the reproduction steps, then check the Preferences multiselect empty state. Done means the identified Account settings strings and the no-options label display in Persian rather than English; the issue notes that a fix is already prepared in branch i18n/fa-account-translations-and-empty-select.

Written by the indexing model from the issue text.

Assessment

Domain
localization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.