Arabic and Persian localizations are unusable

[skycommand]

Describe the bug

Hello. Today, I accidentally activated the Arabic localization on FxSound, only to discover that it is entirely broken and illegible. I browsed other localizations and discovered that the Persian localization is also broken.

To Reproduce

Steps to reproduce the behavior:

1. Install FxSound 1.1.28.0
2. Open FxSound
3. Click the Hamburger menu (☰)
4. Click the arrow button next to English (＞). The UI will switch to Arabic.
5. Inspect the results
6. Continue pressing the arrow button (＞) several times to change the UI to Persian.
7. Inspect the results

Expected behavior

Following the above steps, the user expects a UI in legible Arabic at step 5 and legible Persian at step 7.

Actual behavior

Instead of legible Arabic at step 5, the user is presented with chaos. The Persian UI from step 7 is equally chaotic.

Arabic screenshot (click to expand)

Persian screenshot (click to expand)

Let's inspect this chaos a more closely and decode it together. (If you don't understand Arabic, don't worry because neither do I. I can't order a glass of orange juice in Arabic, but I have worked on multilingual projects before.)

1. If you look at the place that the word "English" once stood, you can discern the following letters: ي‌ب‌ر‌ع. This is not even a word; it's a jumble of letters.
2. Arabic is a right-to-left language, but the right-to-left reading of these letters brings no words to mind. Let's read those from left to right, and rewrite them from right to left. The result is ع‌ر‌ب‌ي.
3. We still don't have a word, but to an Arabic person, it is immediately obvious that those are the letters of a genuine word, in correct order, but wrong casing. (English has two letter cases: Uppercase and lowercase. Arabic has four: Initial, medial, final, and standalone.) If write those letters in correct cases, we get: عربي.
4. Google Translate confirms that عربي is indeed the Arabic word for "Arab" and "Arabic."
5. You can repeat the above steps for every other text field or label in the app. All of them are equally broken.

So, what does all the above mean? It means that the app's translators have done a good job, but the app's UI framework cannot render their work properly.

Recommendation

I recommend dropping Arabic and Persian localizations altogether. If nobody has noticed this bug so far, it's because nobody is using those localizations. In fact, if the word Wikipedia is to be believed, your website has been denying service to the only countries that speak Persian, i.e., Iran and Afghanistan.

System information

• Windows version: 10 v22H2 (10.0.19045.0)
• Audio device: Several, not applicable
• FxSound version: 1.1.28.0

[bvijay74]

Is the localization broken only for the language name listed in the selection box, or do you find that the localization for Arabic and Persian broken and unreadable everywhere in the UI?

[skycommand]

Everywhere