Thank you for your contribution! We have noticed the new translation and just asked our Arabic-speaking colleagues to check it out. It is good that you showed up here because we do not get any contact information via Weblate.
While we were translating to other languages, we have run into many difficult questions about what is the best way to translate certain terms and often found that we need to improve the original English source text instead of doing a literal translation. Have you run into similar issues?
@Shadin_Omari We have noticed that you have translated Python string placeholders (that are replaced by actual values or text at runtime) to Arabic. For example: Checking what was translated to فحص (ماذا ), while the correct translation is (what) فحص. If placeholders are not found in the translated text then the Python script execution stops and the software does not work correctly. For example, currently you cannot load a DICOM file if your Arabic translation is used.
For me, as a maintainer of 3D Slicer, it would be important to know how your Arabic translation compares to the other Arabic translation. Keeping two separate translations would increase the maintenance efforts and in the long term it would result in lower quality translations. Please answer the following questions so that I can have a better idea of what the translation file contains and whether it should be consolidated with the other translation (and if yes, how).
Well, i found some of the english terms need to be improved so i dont have to translate them literally, and about the Arabic (Saudi Arabia), i didnt read all of files, i just had a quick look, and founf it useful that helped me to translate some strings, also i used the gogle translation and asked a friend for help in some other strings that is only understandable by domain experts, but still i cant compare the Arabic (Saudi Arabia) to mine .
I think the way to go is using AI for that.
I just created my second medical brain in quivr and can now chat with it in any language, e.g Chinese or Russian or Arabic (peace), on the webpage.
Ask English question on my German contents, and translate.
It has a growing Slicer brain, too.
However, machine translations are still much, much lower quality than human translations. The choice of words is often suboptimal, but this is not the biggest problem. The most serious issue is that often we realize while we are translating that the original text, or even the software appearance or behavior needs to be changed if we want to have a good translation that users can understand.
Before translating more projects, it would be nice to somehow consolidate the two Arabic translations of Slicer. That would allow you to work together with the other translators. It would also reduce the work to n the future, as if we have two separate translations then after each change in the Slicer user interface the new/changed words would need to be translated twice.
What we would like is to have one Arabic translation of the highest possible quality so that everyone can benefit and work together to improve it. That would mean reviewing the two and suggesting changes to the other so that we have the best of both.
Generally, it is really challenging to use coding technique with the translation tools like Google Translator for automation of language translation from complex languages like Arabia to English. The reasons may include:
Machine translations are useful for getting a general idea about what text written in a foreign language means. However, "general idea" isn't always exactly accurate; the translator literally translates (word for word) the text which often results in grammatically incorrect, if not completely incoherent, text...
Thank you Irray, but this way seems not helpful. I need to translate thousands of values, this will cost me a lot of times!!! and it is easy for me to review the translational instead of translate all the values.
Having a big issue with copying/pasting Arabic text into AI. For some reason when I copy the translation, it reverses when it is pasted into an AI text box. I am using Google Translate to get the Arabic translations (as FPO) and when I paste the copy into a text box the Arabic copy is reversed. I've been trying to contact some translators for assistance on true translation, but fear I will have the same issue with the text reversing.
I've tried to use another language's translated text that reads right to left, and it works perfectly.
I don't understand why it's happening with Arabic.
Thank you in advance for any help!
The issue you are facing might be due to the directionality settings in Adobe Illustrator. Arabic is a right-to-left language, and sometimes, when you paste Arabic text into a text box, the directionality settings in Illustrator may not automatically recognize it, leading to the text appearing reversed.
Also, you must install the MENA version of Illustrator (Middle East and North African languages) as suggested by @Zaid Al Hilali in this community post ( -discussions/problem-with-arabic-english-version-of-illust...) and then change the text direction as suggested in this HelpX article ( -hebrew.html).
I want to add Arabic translation to my mobile application I know how to add in the web. Unfortunately not found straight forward steps to translate my mobile app in Arabic. I followed the below document but as a fresh developer, it is very confusing for me.
If incase you want to manage the Json preparation with easy way then you can install thus web components & start adding string in it, it will help you to export Json which you can use in Mobile app as a resource for Multilingual plugin.
Note: You can add multiple languages as per your requirement. All the Locales that you added this web tool will help you to manage the translations for the mobile Multilingual Utility. Once Added any particular Locales from Dropdown you will see it on the dashboard List :
you will see that the records & translation that you added for the particular Locales are ready & prepared as per Mobile Multilingual Plugin. Whatever string has translation added will be present in JSON :
Else if incase you want to refer them as from Entity then You'll need to add one more attribute i.e translation id property in your entities so you'll be able to indicate what's the id of the translation you want to display.
you can refer to the below sample.
I referenced the static entity & had the translation for the same..
If your static entity is going to be used on all the screens then better you create a local entity & in the onAppReady event under the Logic section, you can similarly prepare list & store in local.. the way I did on Screen.
For text widget , I applied data-trans attribute and key for french language. It is able to convert to french language as JSON prepared. But how we can add attribute for portugese languages or if multiple langugaes?
I see that it is not a direct translation from what I read, those are names and some would give you the wrong translation using any translation software. For instance: ??? ?????? should be translated as "Jabal El-Najma" and not the "mountain of the star" literrally.
I am sorry if this was a repeated topic but I did not have time to check. Anyways, my name is Khalid Zayed. I am a medical doctor, a hospital manager and a university researcher in Cairo, Egypt. I have been working on application of EMR systems in healthcare in my country and doing a lot of research on the subject trying many other healthcare management systems but finally I chose OpenMRS to work with in my hospital and faculty. However, without an Arabic UI, it is not practical to use. Certain functions and fields must be translated to Arabic. I am not sure if OpenMRS supports RTL languages, but I when I tried to input some fields in Arabic, it worked. So, only functions need to be translated. I am not really good with programming or coding but if I get some help from professionals here, I can translate all required words to sound Arabic if there is a table or a list of concepts and functions. The medical staff can use English but other members of healthcare can use only Arabic. So, not all need to be translated and since I know exactly what needs to be translated, I maybe of help.The Middle East is a region which can benefit from this project and I think it has a big feasibility potential if Arabic is added to OpenMRS. The only reason I cannot work with it in my hospital is lack of Arabic interface.Thanks for your help
@dkayiwaThank you Daniel. However, I am still lost. I was wondering if there is some kind of a list, table or glossary for all the words or concepts in the OpenMRS that I can just make it into a table and translate it because I am not an expert with the kind of files or modules that can change the language. I just expected that within a program, there must be such a list that can be converted into a file to change the language interface. Or am I wrong? Thanks for your help
03c5feb9e7