Weird things happens when copy source to target in EN-AR language pair. need help.

My colleague is tranlste an English word file to Arabic, the trados version is 2015, when she copys source to target , weird thing happens, as the figure below

Screenshot of Trados Studio showing source text 'GMSK, 8PSK (GSM)' and 'BPSK, QPSK, 16-QAM (WCDMA)' with incorrectly placed brackets in the target text.

as you can see, the source is 
GMSK, 8PSK (GMS) 
and 
BPSK, QPSK, 16-QAM (WCDMA)

but when copied them to target, the position of the brackets changed to

(GMSK, 8PSK (GSM 
and 
(BPSK, QPSK, 16-QAM (WCDMA

but on my computer, the trados version is still 2015, when I copied the source to target, the position of the brackets are the same as source.

Screenshot of Trados Studio with source text correctly copied to target text, maintaining the original position of brackets.

I installed a new version (2019) on her computer, the same problem appears again. 

I've tried the button "Insert rigths-to-left mar",  seems no help.

Screenshot of Trados Studio interface highlighting the 'Insert right-to-left mark' button in the toolbar, with 0 Errors, 0 Warnings, and 1 Note displayed.



Generated Image Alt-Text
[edited by: Trados AI at 6:46 AM (GMT 0) on 29 Feb 2024]
emoji
Parents
  • If you want the text to look exactly like the source (i.e. to maintain the left-to-right text direction), you need to add the LRM (left-to-right) mark and not the RLM (right-to-left) mark after the closing bracket (the one that is out of place). You may also need to add another LRM character at the beginning of the sentence because due to some other technical factors that will be too long and boring to get into details about here. In fact, it's a good practice to enclose LTR phrases/sentences within an otherwise RTL sentence/paragraph between two LRM characters. For example <LRM>The text goes here<LRM>.

    That said, for RTL languages, the order of the items in the list should change to right-to-left as well, so you might want to consider this first.

    Lastly, export the document and see how it comes out because, and that's another layer of complexity, even if you get everything looking correctly inside the Editor environment some idiosyncrasies between the version of the Word (or any other) filter you use in Studio and the version of Word (and any other program) the document was created on/saved with could result in BiDi issues in the exported document. Some programs (Word, InDesign, and so on) have their own RTL quirks. For RTL languages, one must always check the translation in its native format for layout and directionality issues because more often than not there will be at least minor fixes to apply.

    emoji
Reply
  • If you want the text to look exactly like the source (i.e. to maintain the left-to-right text direction), you need to add the LRM (left-to-right) mark and not the RLM (right-to-left) mark after the closing bracket (the one that is out of place). You may also need to add another LRM character at the beginning of the sentence because due to some other technical factors that will be too long and boring to get into details about here. In fact, it's a good practice to enclose LTR phrases/sentences within an otherwise RTL sentence/paragraph between two LRM characters. For example <LRM>The text goes here<LRM>.

    That said, for RTL languages, the order of the items in the list should change to right-to-left as well, so you might want to consider this first.

    Lastly, export the document and see how it comes out because, and that's another layer of complexity, even if you get everything looking correctly inside the Editor environment some idiosyncrasies between the version of the Word (or any other) filter you use in Studio and the version of Word (and any other program) the document was created on/saved with could result in BiDi issues in the exported document. Some programs (Word, InDesign, and so on) have their own RTL quirks. For RTL languages, one must always check the translation in its native format for layout and directionality issues because more often than not there will be at least minor fixes to apply.

    emoji
Children
No Data