search

telegramdesktop / tdesktop

Telegram Desktop messaging app
https://desktop.telegram.org/
Other
25.17k stars 5k forks source link

Arabic language missing from language selector #25736

Open mhsabbagh opened 1 year ago

mhsabbagh commented 1 year ago

Steps to reproduce

  1. Open settings.
  2. Choose language.
  3. You will see that Arabic language is not available.

Expected behaviour

Arabic language should have been available at the language list. This is not a feature request but rather a bug because Arabic is already supported on the mobile/web apps (Screenshot attached), and it is translated completely for desktop at: https://translations.telegram.org/ar/tdesktop

So using it is just something missing that needs to be added and not a complete feature. Perhaps devs just forgot to include it in the list?

photo_2023-01-15_11-55-33

Actual behaviour

Arabic language is not available to be chosen in the language selector, preventing Arabic users from displaying Telegram in their language.

Operating system

Ubuntu 22.04, GNOME 42.5

Version of Telegram Desktop

4.5.3

Installation source

Snap

Logs

No response

amr3k commented 1 year ago

Why can't Telegram desktop show Arabic in the list !!

github-actions[bot] commented 10 months ago

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

me00001 commented 10 months ago

A comment to keep it open

john-preston commented 10 months ago

Well, the languages are marked separately for different apps as being "ready" for a widespread usage (not testing). I guess Arabic isn't considered ready for TDesktop (and I'm not sure it will be, because TDesktop isn't RTL-friendly in UI 😞, although I don't know if it's a strict requirement for an RTL language to be marked as "ready").

github-actions[bot] commented 4 months ago

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

mhsabbagh commented 4 months ago

The issue is still there.