WorldServer and Trados Studio - Maximum Length check of CDATA content processed by an HTML processor in Custom XML file type does not work

I have applied the correct Length restriction settings to my Custom XML file type configuration as explained in this article. I am using a Custom XML file type with embedded content processor (HTML 5) enabled. The processor handles the CDATA content of my XML file.

However, the Maximum Length restriction check is not applied to my file in Studio. The segments are not marked accordingly as it should be expected. Why is this happening?

The Studio engineering team proposed this workaround:

You can set an XML validation which would validate the file when pressing F8 in Studio. Such validation will be a simple schema defining the max size of the parent element of the content you extracted for embedded content processing.

However, this has not been tested as the creation of DTD schema is beyond support scope.

The other workaround is to add a QA Profile to the Project Type used to create projects with these files and a file type filter in WorldServer (or if you work in Studio only, add it to the project settings). The QA Profile configured in Studio should include a Length Verification set to Check if target segments are longer than the character count. Here you can set the desired value. By running the Verification (F8), all target segments will be checked for their length.

Embedded content which is handled via external processors relies on the external processor functionality. If such processor doesn't support length limitation, it will not work. This applies to any content handled by processors, HTML or Plain text.

These articles are relevant:

Worldserver - How to configure an XML File Type to add Length Restriction limits?
WorldServer - How to set the maximum character length of target segments for translation in Trados Studio
How to add a Studio QA Checker Profile to a Project Type in WorldServer