Katharina Schuhmann 

Katharina Schuhmann said:

I did provide a sample in the .zip folder I attached to my post.

So you did... couldn't see it for looking!

Quite an interesting file and I went around the houses before we found the problem!  I'll start with the problem... the file you are using has no XML declaration and it doesn't have a BOM (Byte Order Mark telling it the file is UTF-8).  So when you open in Studio the file is actually seen as Baltic (Windows) and the incorrect encoding is used.  The result... nothing you do will fix this problem of entities unless you fix in the file or change the encoding when you open it.

The last option is only available for single file projects and works by selecting UTF-8 when you open the file here:

You will then see this message:

Click yes and all is well :-)

We cannot change the bold I'm afraid as this is due to the text being in a CDATA section.  It's only bold in the editor.

The next way to change it, seeing as you may have many files and working with a single file project is probably not optimal, is to pre-process the file and add an xml declaration to the start:

<?xml version="1.0" encoding="UTF-8"?>

Easy enough to do and you could create a script to handle all the file in a project and then use a script to remove the declaration afterwards if you client cannot manage the files with this.

Another way is to add a BOM to your files.  This may be even more preferable since you can handle multiple files in one go with this app and the change shouldn't be an issue for your customer:

https://appstore.rws.com/Plugin/58

You can find a short video to see how this works here: https://youtu.be/mJY212049WE

In the process of all of this I also tried to use the preview to workaround the issue and can do this:

It didn't help me with the workaround until I fixed the problem with the encoding, but I quite like it so here's the stylesheet in case you find it helpful too: recordID.zip

So I think this is solved apart from the bold bit, but I'm afraid there is no way around this since you cannot use the Document Structure for your rule, nor for the preview, if you use embedded content.  But at least you seem to have a way forward.

Katharina Schuhmann 

Katharina Schuhmann said:

I did provide a sample in the .zip folder I attached to my post.

So you did... couldn't see it for looking!

Quite an interesting file and I went around the houses before we found the problem!  I'll start with the problem... the file you are using has no XML declaration and it doesn't have a BOM (Byte Order Mark telling it the file is UTF-8).  So when you open in Studio the file is actually seen as Baltic (Windows) and the incorrect encoding is used.  The result... nothing you do will fix this problem of entities unless you fix in the file or change the encoding when you open it.

The last option is only available for single file projects and works by selecting UTF-8 when you open the file here:

You will then see this message:

Click yes and all is well :-)

We cannot change the bold I'm afraid as this is due to the text being in a CDATA section.  It's only bold in the editor.

The next way to change it, seeing as you may have many files and working with a single file project is probably not optimal, is to pre-process the file and add an xml declaration to the start:

<?xml version="1.0" encoding="UTF-8"?>

Easy enough to do and you could create a script to handle all the file in a project and then use a script to remove the declaration afterwards if you client cannot manage the files with this.

Another way is to add a BOM to your files.  This may be even more preferable since you can handle multiple files in one go with this app and the change shouldn't be an issue for your customer:

https://appstore.rws.com/Plugin/58

You can find a short video to see how this works here: https://youtu.be/mJY212049WE

In the process of all of this I also tried to use the preview to workaround the issue and can do this:

It didn't help me with the workaround until I fixed the problem with the encoding, but I quite like it so here's the stylesheet in case you find it helpful too: recordID.zip

So I think this is solved apart from the bold bit, but I'm afraid there is no way around this since you cannot use the Document Structure for your rule, nor for the preview, if you use embedded content.  But at least you seem to have a way forward.

Katharina Schuhmann 

Also... we have logged a dev item to ensure the default will always be UTF-8 if we don't know!  Our reference is CRQ-33815.

 Paul 

Wow, that's quite a solution! Thank you! Thanks for the explanation, too - I always thought these files are strange, but we get so many strange files these days (remember the XLIFFs?)...

I don't know if I have time today to try out your solution and then I'm on holiday, but I will definitely look into this and try it afterwards. So thank you very much once again! I'll get back to you once I've tried everything. :)