New Arabic translation of 3D Slicer

Hello, I’ve finished translating the project from English to Arabic language, the 3D Slicer…now what’s next, how are you going to pay for me??

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.

How have you translated it? Using fully automatic translator? Have you reviewed the translations?

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?

Some modules, especially CLI modules of low-level processing algorithms contain information that is only understandable by domain experts. How have you translated such strings?

Have you checked the “Arabic (Saudi Arabia)” translation that our collaborators in Senegal has been working on? Have you found it useful? How does it compare to your translation?

We are grateful for your work and we’ll pay you the same amount that you’ve paid for the development of Slicer. Thank you!

3 Likes

@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.

Fortunately, it is easy to fix this. If you open this URL then you will get a list of all strings where placeholders got removed so you can quickly go through them and fix them. Thank you!

1 Like

Hello sir
I’ve just reviewed the translation, and did what you told me about, i’ve corrected them, i think now all the strings have been translated and its 100% for all of them…
Is that correct??

Correct, you have completed the translation for both Slicer core (Slicer and CTK components). There are a handful of strings with failing checks in each component that you might want to check.

ow have you translated it? Using fully automatic translator? Have you reviewed the translations?

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?

Some modules, especially CLI modules of low-level processing algorithms contain information that is only understandable by domain experts. How have you translated such strings?

Have you checked the “Arabic (Saudi Arabia)” translation that our collaborators in Senegal has been working on? Have you found it useful? How does it compare to your translation?

Good afternoon sir…
Now i think I’ve completed all of the strings, right? It was a completely new experience for me …
Anything left?? And what’s the next step?

Hello sir
Did you read my last message???

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).

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?

Some modules, especially CLI modules of low-level processing algorithms contain information that is only understandable by domain experts. How have you translated such strings?

Have you checked the “Arabic (Saudi Arabia)” translation that our collaborators in Senegal has been working on? Have you found it useful? How does it compare to your translation?

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 woul like to add something, im a native Arabic Speaker, and i have a bachelor degree in English language

1 Like

??? Any answer??,
Have you read my messages?

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.

@rbumm Thanks for the information, I would be ld be interested interested to see hear more about things that you can do.

Machine translation has definitely plays an important role. @Shadin_Omari seems to have used Google Translate, while the CZI Africa team is using Weblate’s built-in machine translation suggestions (from Microsoft, Google, and a few other engines) as a starting point for all translations.

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.

@Shadin_Omari I appreciate your continued interest in the project and can understand that you are anxiously waiting for my answers. However, the tone of some of your messages (e.g., ??? Any answer??) is not compatible with the friendly conversations that we are trying to have on this forum. You can certainly ask again if you don’t get a timely answer, but try to appear less demanding (drop the multiple question marks, etc.) and also describe what you did in the meantime on your side or any other potentially relevant details.

I’m not sure about next steps with the two Arabic translations. One translation would be much easier to maintain, but if they serve different purpose then we might keep both. Do you have any suggestions?

Sir, please accept my apologies in case you thought my tone wasn’t compatible with the friendly conversations that we are trying to have on this forum… ( i had to translate the word " compatible " on google translation to make sure of right meaning) thats why i used google translation to do this project, to choose the exact correct meaning of the words, I didn’t use it randomly and just copied and pasted the translation, plus I appreciate your continued efforts to master your work and make sure you use the right words.
Sir, i usually work as a translator, i mean in daily life, i translate and proofread books for universities, also master’s and doctoral theses, and i use Google translate as an assistan, since English is my second language, to choose the most accurate words.
I mean in case you liked my translation, i will be honored to translate more projects with you …

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.

Hiw do you think the two Arabic translations of Slicer could be merged?

@lassoan you can go https://www.quivr.app, create a login, and subscribe to the 3D Slicer public brain. It contains the slicer.pdf, the redthedocs.pdf, and the publication numbers.

1 Like

Good Evening @lassoan
Sorry for being late…

What do you mean in consolidating the two Arabic translations? If you mean something technical, then i would like to apologize since im not an expert in computer science…

Still you didn’t find out what the next step will be, so you will not pay for me??

Dear @Shadin_Omari - we appreciate your interest and efforts. It’s important to be clear that Slicer is a free software project supported by people to want to make it available globally. As far as I know nobody offered to pay for translations so you should not expect payment.

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.

2 Likes

@Shadin_Omari thank you for sending that screenshot. I’m sorry if it was misinterpreted, but I interpret @lassoan as being sarcastic in that post. Nobody pays to use Slicer, so we are not offering payment for translations either.