Sotir Rangelov

The reason for this is that this text is held in the value attribute of the input element of your CDATA.  This is non-translatable by default in the html embedded content processor.  So you would need to make that attribute translatable.  Once you do that you will have this:

However... you will also have the content from every other part of the file containing this attribute and as you can see quite a lot more segments!  So you will now not only have additional content you don't want as you can see, but also things like this:

Not exactly what you wanted!!  The problem really is Wordpress doesn't provide localization friendly XLIFF.

One possible solution is to use the new Multilingual XML filetype on the appstore.  Using this you can do the following:

1. put the source in the source and the target in the target ... so not just a monolingual XML filetype where you translate the target
2. use the embedded content processor AND use regex to remove the placeables you also find in this file

So I could achieve this for example:

Somewhat better... however I do think that the work required to prepare this particular file would be so excessive you won't like it.  This is truly one of the worst examples of XLIFF prepared for translation I have ever seen.

Sotir Rangelov

The reason for this is that this text is held in the value attribute of the input element of your CDATA.  This is non-translatable by default in the html embedded content processor.  So you would need to make that attribute translatable.  Once you do that you will have this:

However... you will also have the content from every other part of the file containing this attribute and as you can see quite a lot more segments!  So you will now not only have additional content you don't want as you can see, but also things like this:

Not exactly what you wanted!!  The problem really is Wordpress doesn't provide localization friendly XLIFF.

One possible solution is to use the new Multilingual XML filetype on the appstore.  Using this you can do the following:

1. put the source in the source and the target in the target ... so not just a monolingual XML filetype where you translate the target
2. use the embedded content processor AND use regex to remove the placeables you also find in this file

So I could achieve this for example:

Somewhat better... however I do think that the work required to prepare this particular file would be so excessive you won't like it.  This is truly one of the worst examples of XLIFF prepared for translation I have ever seen.

Thank you! I will try this new XML asap.

Meantime we will update those elements manually copy-pasting translation into client's website.