Arya. H

Please can you show the full tag text in this view, and can you also explain better what the difference is because I think only a Persian speaker will be able to tell from this one screenshot alone.

By tag text... I mean this:

If I press Ctrl+Alt+D I can toggle through the tag displays:

Obviously we're interested in the first one so we know what the CF tags are actually doing.

This issue happens with every tag. I also checked my previous documents, which were displayed correctly before the update. The same issue applies to them now

Here you can see an example of separated characters:

Persian sentence (before the update)

"سلام. اسم من آریا است"

Persian sentence (after the update)

"س‌ل‌ام. ا‌س‌م م‌ن آ‌ر‌ی‌ا اس‌ت"

Arya. H

Thanks for the additional detail.  Given these are only formatting tags can you ignore them altogether and simply don't insert them?  They are not required to be able to save the target document.

Out of interest, have you compared what happens in Microsoft Word if you do this?

1. don't use the tags in Trados Studio
2. save the target translation DOCX
3. apply the formatting in Microsoft Word

Can you also provide a small source file, and a TM, so I can test this in 2021 and also in an older version seeing as you said this only occurs since upgrading to 2021.  Which version did you have before?  You can send the files to pfilkin@sdl.com

Please check your inbox.

I also tried your second suggestion. The tags won't cause any font issues when they're applied in Microsoft Word

I accidently found a temporary solution, but this issue requires an immediate update.

Arya. H

Thank you for this update.  You won't get an immediate update I'm afraid... that would only happen with a critical issue which this is not.  Once the support team have looked at it they will clarify for development and the work to resolve this will be planned for a future update.  We'll update the posts with the bug number when we get it so it's easier to refer to the work planned.

Thanks for the reply.
I wish the team would have considered this as a critical issue. The text becomes completely unreadable when tags are applied.

Arya. H

I understand where you're coming from.  But the teams need to have a mechanism for categorising and prioritising work, so this is what they use in support:

I'm not sure yet how they will see this one, but I think it should be a "P2 - High" because it's debatable whether or not the workaround you have provided is acceptable or not.  Given the importance we place around checking for additional spaces in the QA tools I think being forced to add one where there should not be one is unacceptable.  But from a technical perspective I can't be sure what the view will be until the issue is investigated.

Anyway, I hope that gives you some insight into the process the teams will go through as they have more than a few bugs to prioritise, and we'll update this post, and the other one once we have the bug number to track.

https://community.sdl.com/product-groups/translationproductivity/f/studio/34461/sdl-trados-studio-2021-does-not-recognize-arabic-characters-after-update

Thank you for the detailed response.
For now, we keep adding additional spaces until it gets fixed.

Arya. H said:

Please check your inbox.

Thank you for sending me the files.

Update:
Alternatively, users can add any English character after the opening tag and remove it in the final word document using Find and replace.

Update:
Alternatively, users can add any English character after the opening tag and remove it in the final word document using Find and replace.