# Arabic Text Issues

**URL:** <https://quelea.discourse.group/t/arabic-text-issues/880>\
**Category:** Uncategorized\
**Created:** [July 27, 2022, 3:29am UTC](https://quelea.discourse.group/t/arabic-text-issues/880 "2022-07-27T03:29:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![member238](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@member238](https://quelea.discourse.group/u/member238)\
**Post date:** [July 27, 2022, 3:29am UTC](https://quelea.discourse.group/t/arabic-text-issues/880/1 "2022-07-27T03:29:25Z")

</div>

Hi! Trying to help a friend who leads worship with some Arab speakers. He’s trying to add Arabic as a translation and is running into some issues. Seems in part to be due to the default font Noro Sans, which doesn’t seem to render Arabic properly. When he doesn’t use the translation functionality, and switches to Arial in the theme settings, both languages project correctly. However, on the preview screen and live preview screen on the computer, it comes out all scrambled. This isn’t a game stopper, but they would love to maybe get the translation functionality working, if possible. However, they are running into a couple of problems.

Firstly, the font used for translation also seems to be Noro Sans, and we’re can’t figure out any way to change that. Is there a way to do that?

Secondly, the chords get scrambled when we put them adjacent to the Arabic. Is there a way to enable right-to-left functionality?

Also, is it possible at all to change the font used for the two preview screens on the computer?

Thank you so much for any help you can give us!

Quelea 2022.0 is running on a Macbook running OSX 10.15.7

---

<div class="post-metadata">

**Author:** ![steph](https://avatars.discourse-cdn.com/v4/letter/s/22d042/32.png) [@steph](https://quelea.discourse.group/u/steph)\
**Post date:** [March 10, 2025, 9:41am UTC](https://quelea.discourse.group/t/arabic-text-issues/880/2 "2025-03-10T09:41:01Z")

</div>

any solution ?, experiencing same problem, preview and live panels show gibberish when I paste telugu

---

<div class="post-metadata">

**Author:** ![JessyJP](https://yyz2.discourse-cdn.com/free1/user_avatar/quelea.discourse.group/jessyjp/32/292_2.png) [@JessyJP](https://quelea.discourse.group/u/JessyJP)\
**Post date:** [March 10, 2025, 4:15pm UTC](https://quelea.discourse.group/t/arabic-text-issues/880/3 "2025-03-10T16:15:37Z")

</div>

First of all, you would have to start from here:

> [@Checkout this Quelea expansion pack build with Improvements and experimental features!](https://quelea.discourse.group/t/checkout-this-quelea-expansion-pack-build-with-improvements-and-experimental-features/1162/13):
>
> Well, now it’s totally next level. It can figure out if you mean to search by refererence. They are clickable an can effectively act like a navigation for the references, The search is hybrid. It can figure out if you mean to write text or a reference. With some minor exceptions in some languages, there won’t be any…

This is a fork with new and extra features and modifications. It at least up to date.  
If you are on windows, I can provide an installer. With this version you wouldn’t need to reinstall to further modify the web parts.  
In "c:\Program Files\Quelea\server" the HTML/CSS/JS can just be modded.

That said, I could probably include features like that, but testing would be up to you. If you give good feedback would be possbile. I have added some font options for the remote already. Now that you mention it, I could do the same for the web view, it’s little effort afterall.

As for macs … I don’t care about them at the moment. I have some other projects wich might need iphone and mac builds. If i get a setup i would do this one too, but it’s not a priority.  
… again, if there is a willing and able Mac used to do the builds I would include them in the releases.
