A SDL Trados Studio 2017 query: We notice in our XML parsing that a non breaking space is removed during the parsing. We are using filters originally configured for SDL 2014 and we never had a removal there of the non breaking space.
So a combination of 'C2 A0 20' (non breaking space + regular space) is parsed as '20' removing the 'C2 A0' from the string.
Q1 > is this expected?
Q2 > would there be a setting to configure in the XML filter we are using?
Thanks for any hint.
From what I know you need to write the parser rules new. I have had a similar problem, where an extra cr/lf has been added to XML after producing target. After having recreated the parser rules from scratch in a new template in Studio 2017 the problem is gone.
There is for sure a recommendation to create all new project templates in Studio 2017 instead of importing the old ones, as this causes problems. The simplest explanation can be, that the file types has been changed significantly.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
From what I know you need to write the parser rules new. I have had a similar problem, where an extra cr/lf has been added to XML after producing target. After having recreated the parser rules from scratch in a new template in Studio 2017 the problem is gone.
There is for sure a recommendation to create all new project templates in Studio 2017 instead of importing the old ones, as this causes problems. The simplest explanation can be, that the file types has been changed significantly.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Translate
