Entity conversion in embedded content

Hi

I have some problems getting entity conversion in embedded content processing in SDL Trados Studio 2015 to work the way I'd like it to work...

I'd like Studio to interpret the character entities it finds (reader settings) and show that in the editor, but I'd like Studio to output the actual characters in the output (writer settings).

In some cases, Studio even double escapes things.

 

Input?

Parents
  • Hello Torben,

    Can you knock up a small test file please and attach to the post? Just a few lines to make this simple will do nicely and will make it easy to anonymise.

    Thanks

    Paul

    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 Paul

    Thank you for taking a look!

    Here is a small test file. As you can see, the client is also doing it differently, sometimes writing the actual characters, sometimes escaping things:

     

     

    Client is asking to deliver back with actual characters.

    <?xml version="1.0"?>
    <root>
      <content>
        <text>&lt;p&gt;&lt;strong&gt;If the sun is shining&lt;/strong&gt; we&amp;rsquo;d love to use R&amp;Aring;SE as &amp;nbsp;&lt;span style="line-height: 1.42857;"&gt;protection.&lt;/span&gt;&lt;/p&gt;</text>
        <text>&lt;p&gt;Tap RÅSE into a search engine and it’s quick to see that happily you love the product as much as we do. Here’s a couple of ways our product manager would love to try it out.&lt;/p&gt;</text>
      </content>
    </root>

  • Hi Torben,

    I spent a while messing with this and trying every configuration I think is possible (including the suggestion from Evzen which didn't work) but cannot achieve what you are after. I also discussed it with Patrik and he confirmed this is not going to be possible because the file is really badly authored causing a need to solve two different problems at the same time. The only option would be for us to introduce a setting for each entity and then support a different conversion behaviour for parsing and writing. This I think is starting to get too complicated when the solution is probably far easier than this.

    Just ask your client to do one thing or the other! Well... I say it's easy but it may not be!!

    Regards

    Paul

    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

Reply
  • Hi Torben,

    I spent a while messing with this and trying every configuration I think is possible (including the suggestion from Evzen which didn't work) but cannot achieve what you are after. I also discussed it with Patrik and he confirmed this is not going to be possible because the file is really badly authored causing a need to solve two different problems at the same time. The only option would be for us to introduce a setting for each entity and then support a different conversion behaviour for parsing and writing. This I think is starting to get too complicated when the solution is probably far easier than this.

    Just ask your client to do one thing or the other! Well... I say it's easy but it may not be!!

    Regards

    Paul

    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

Children
No Data