NLG GmbH

NLG GmbH said:

Initially I tried to process it with Studio's embedded file types, I had no luck as I received the error message below.

This is a bug in Studio.  If you rename the file *.xlf instead of *.xliff then it will work:

But even with this you still can't process the embedded content... another bug.  The latter has already been fixed ready for CU5 and Patrik Mazanek can review the problem with recognition of *.xliff in case it's not already known.

So, you do still need to use a custom XML for the time being... probably better anyway as the embedded content processor for XML is a lot more versatile than it is for XLIFF.  This works fine:

The RTL attribute is probably correct and is there because the target language is RTL.  Why would you want to change it?

Hello Paul Filkin

Thanks for having a look on this.

I've tried what you suggested below; neither in Studio 2019 CU8 nor in Studio 2017 CU18 I can make it work.

Paul Filkin said:

If you rename the file *.xlf instead of *.xliff then it will work:

You mean Studio 2021, aren't you?

Paul Filkin said:

The latter has already been fixed ready for CU5

The customer got back to us complaining why this attribute is there, as it caused troubles while importing the translated file back in Wordpress.

Paul Filkin said:

Why would you want to change it?

Anyway, if this is how Studio works, we can do nothing about it.

NLG GmbH said:

Anyway, if this is how Studio works, we can do nothing about it.

Correct.  Although you could log it in the ideas site so the filetype manager can consider making the addition of the RTL attribute optional.  OR you convince Wordpress to accept valid html.

NLG GmbH said:

Anyway, if this is how Studio works, we can do nothing about it.

Correct.  Although you could log it in the ideas site so the filetype manager can consider making the addition of the RTL attribute optional.  OR you convince Wordpress to accept valid html.