Hi,
I have a problem with Persian numbers.
In Trados (also with last update 14.1.10010.18573) the numbers are displayed correctly (۲۷-۲) but when saving the Word file the position of the numbers is converted (۲-۲۷).
The numbers are displayed correctly when I open the .docx file with Wordpad!
Thank you in advance for a reply.
Hi,
I enclose the file with some examples.
I enclose the file with some examples.
It would be helpful if you provide the SDLXLIFF and not just word files. It's quite difficult for me to enter the correct hindi number and even harder for me to understand whether the results are the right way around or not. I think a good place to start checking would be related to the correct placement of BiDi markers in the file, but I'm not really sure.
So you will really need to spell this out to me step by step, what you have done, what you expect to see etc. etc. Show the BiDi controls in any screenshots explaining where you placed them etc.
Then I'll be happy to get this investigated properly with the appropriate teams.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Hi Paul,
Thank you for your kind answer.
In attachment I send a pdf file with the details and SDLXLIFF file.
Thank you, this is helpful. A quick question, am I right in thinking that Hindi numbers are written left to right as well?
This being so I'm wondering if having to insert the LRM is the normal process here. I wonder if Shai Nave might also be able to chip in as he's an expert in the use of BiDi in CAT tools.
I'd like to make sure I have the correct understanding of this before discussing with support.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Thank you Paul,
Yes, I confirm that both the Persian and Arabic languages follow the logic of mathematics, so they are written from left to right.
I also opened another topic about the lack of automatic conversion of Persian numbers (standard keyboard available in windows 10) in Trados. Maybe it would be better to cover the whole argument in this topic.
Hi Paul,
Do you have any news about this question of mine?
thank you
Apologies for not getting back to you sooner.
Do you have any news about this question of mine?
In your PDF you said this which seems to be the knub of your problem:
I think this is simply how you must work with these chars. When you type there is no recognition of the Persian language going on so Studio doesn't know when you type a number that should go left to right, and when you type other characters that go right to left. So you have to add in a LRM as you are.
But the problem is that in a 50-page manual that most are numbers, inserting LRM mark after each number is very demanding work. It would be better that the same display in Trados, we find also in Word format.
I don't believe there is a simple way around this. But I suggest you raise it as an idea and perhaps once we have more integrated AI in the tools we will be able to do things like automatically:
I also opened another topic about the lack of automatic conversion of Persian numbers (standard keyboard available in windows 10) in Trados.
Also a topic for a separate idea.
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Thank you for your response.
Trados has included the Persian language in its list of languages, but despite this it ignored the minimal support for this language, such as no support for the Standard Persian keyboard, lack of support for numbers and especially Verify. Many customers who do not know the Persian language send me emails saying that they receive a lot of errors when they make Verify and I have to answer them that it is the lack of Trados support.
For example Verify reports as an error if it doesn't find capital letters at the beginning of the sentences. This option must be removed by default for Persian, Arabic and Urdu because there are no uppercase start characters in these languages, or Verify reports that there are numbers in the source but no numbers in the target language. Not to mention the fact that it does not support Persian grammar at all.
I will now try to make my requests in the "ideas" section and hope to have some answers.
I have to answer them that it is the lack of Trados support.
I'm curious... is there another CAT tool that provides you with this level of support?
Paul Filkin | RWS
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Unfortunately I haven't had the chance to work with other Cat Tools recently. I have worked with some of them, but many years ago. I am also curious to know if there are other Cat Tools that support RTL languages better.
Unfortunately I haven't had the chance to work with other Cat Tools recently. I have worked with some of them, but many years ago. I am also curious to know if there are other Cat Tools that support RTL languages better.
Translate
