-Celso
Hi celso scott
Yes, thank you for persevering with these tests. I played around with this today and can obviously reproduce this, although without your help I would not have been able to identify the likely problems. I copied Kevin Flanagan as he may be interested to take a look at this problem too.
Paul Filkin | RWS Group
________________________
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 celso scott
Yes, thank you for persevering with these tests. I played around with this today and can obviously reproduce this, although without your help I would not have been able to identify the likely problems. I copied Kevin Flanagan as he may be interested to take a look at this problem too.
Paul Filkin | RWS Group
________________________
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
Yes, thank you for being so responsive. I think it should be a really easy fix, it is just in regard to how the platform reads the Unicode for this one punctuation character. I was almost wondering if there was a fix from a preference or option within SDL Trados, but I was unable to find a setting that would change how the platform reads Unicode characters when performing fuzzy matching and concordance searches, so I suspect it is something that needs to be fixed in the code.
I suspect there just hasn't been a lot of Tibetan language translators using SDL yet to notice the problem.
My trial has actually ended now, and I don't want to purchase the platform without knowing this is functioning, but I will stay in touch in the forum here and if this can be corrected. I will do another trial on a different computer to verify this and send word out to my translators group forum and update my review.
If there is any way I can help, such as explaining Tibetan language structure or further test examples just let me know.
Hmmm, lately I've been trying and reviewing some other CAT platforms, I noticed on CafeTran I had this exact same problem with the Tibetan tsek punctuation and CafeTran was getting no fuzzy match leverage, however when I brought it up in their forum, they pointed out a configuration setting in the platforms preferences that was labeled, "Additional space characters" after adding the Unicode for the Tibetan tsek punctuation, the fuzzy matches worked splendidly.
I'm wondering, there isn't some SDL Trados configuration that can do this? I feel like if there was it would be easy for me to miss while I was testing the platform, but it is a very simple coding correction right? It just needs to recognize for Tibetan that (U+0F0B) = (U+0020). This configuration on CafeTran showed me that this was all that was needed.
Please do let me know if there is any update on this, as I would like to give SDL another go since it so far is the only CAT platform I've found that has a good workaround for annotating translations from the editor, thus it is a great platform for academic/scholastic translation.
Hello celso scott and Paul,
I wonder whether this is a related issue and could be addressed at the same time:
Daniel
Hi Daniel,
Yes, that does seem to be a similar problem, although I am not at all familiar with Persian languages. I think the simplest solution for many similar cases would be to have a preference or configuration that allows for particular Unicode characters to be read as spaces. I'm sure it would be a useful fix for many issues situated in other language combinations as well. As I mentioned this is a feature in the CafeTran platform that resolved the problem for Tibetan.