Hi Michael,

the behaviour you describe is a defect in version 11.7.x, which is fixed in version 11.8. There is a simple workaround. This article has all the details:

https://gateway.sdl.com/apex/communityknowledge?articleName=000019653

I recommend a search in our Knowledge Database, it is very likely that you find an article for almost all issues :-)

hope this helps you!

Hello Caterina, thank you for your help. However, I am still confused. According to the screenshot, I should modify the existing XML 2: Any XML file type in Trados Studio 2022. But as you can see from my last screenshot in the original post, I do not have the ability to modify the parser rules for this file type.

I also cannot export the XML 2: Any XML file type:

If I could have exported it, maybe I could have imported it and changed the new derived file type.

Hi Caterina,

OK, thanks for that!  The workaround is a bit as I suspected but was afraid to try it off the cuff. I'll give it a go in the next few days and let you know how it goes. Thanks again!

Unfortunately, I still cannot get this to work. I've created a filetype filter for XML 2 that works perfectly in Trados Studio 2022:

(For information, I followed the information provided by Paul Filkin here:  Are there differences in XML 2 parser rules? )

When I try to follow the steps in the article you provided, I am able to import the file type (although "Copy of XML v 2.0.0.0_2" specified on the help page was simply "Copy of XML v 2.0.0.0" for me, probably doesn't matter). The file type is applied to the file during project creation in WorldServer as I would expect; however, no segments at all are displayed (0 words to translate). I do not understand why it works fine in Trados Studio 2022 but not our version of WorldServer 11.7.3. Unfortunately, very frustrated...

Hello Michael, are you sure that the "right" filter configuration has been used to segment the file in WorldServer? Please check the Task History and the "Segment Asset" step. If all is fine and the "right" filter and configuration has been applied, can you please create a Worldserver support case for this, providing source file and sdlftssettings file?

Hi Caterina, thank you for your reply. Yes, that is what I meant by this:

"The file type is applied to the file during project creation in WorldServer as I would expect; however, no segments at all are displayed (0 words to translate)."

I will have to check the status of our support agreement.

Hi Michael, I have tested the segmentation after the import and - unfortunately - I confirm that the settings are not applied and the segmentation results in 0 words. I have filed a defect with ID CRQ-33343. I hope to hear back from the Engineering Team with a solution or a workaround for versions below 11.8. As you know, the issue is fixed in version 11.8. Maybe is upgrading an option for you? Version 11.8.0 is already available, 11.8.1 will be released around mid May. Anyway, I will keep you posted. Happy Easter!

Hi Caterina,

thank you for following up! We had actually just upgraded from 11.3.5 to 11.7.3 so I'm not sure we can convince the company to upgrade again. I am still clarifying the status of our support agreement and look forward to any new information from your side. Happy Easter as well!

Dear Michael, unfortunately, the issue is not fixed for version 11.7.3, but I found an imperfect, but functioning workaround:

1- In Trados Studio, create your File Type configuration normally using File > Options > File Types > New from XML2.
2- Export your File Type configuration to a *.sdlftssettings file
3- Before importing it into WorldServer 11.7.x (which would lead to the error), open the .sdlftssettings file in *Notepad ++, and change these properties as below. Note: the values associated with SettingsGroup Id and FileTypeDefinitionId might vary, depending on what you have entered in Studio.

Find
<SettingsGroup Id="Copy of XML v 2.0.0.0_2">
and replace it with
<SettingsGroup Id="XML: Any v 1.2.0.0">

Find
<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 2.0.0.0</Setting>
and replace it with
<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 1.2.0.0</Setting>

Find
<FileTypeDefinitionId>Copy of XML v 2.0.0.0_2</FileTypeDefinitionId>
and replace it with
<FileTypeDefinitionId>XML: Any v 1.2.0.0</FileTypeDefinitionId>

Save your change and import the File Type configuration again. The import will work. However: the filter configuration will not appear under the XML 2: Any XML File type, but under the Custom XML (Legacy Embedded Content) File Type.

The filter configuration will work, meaning that XML files will be segmented fine.

I will keep you posted.

Cheers, Caterina

Hi Caterina Lazzarini , thank you very much for the follow-up. When I get some free time, I will give it a go and let you know the results.

Hi Caterina Lazzarini  I've just tested it, and you're right: it does segment. However, it didn't show up for me under "Custom XML (Legacy Embedded Content) File Type", but under "XML: Any v 1.2.0.0". In addition, all parser settings were ignored so the segments are partially broken and no document structure information is displayed.

Hi Michael, sorry, there was a typo in my previous instructions: I entered, <SettingsGroup Id="XML: Any v 1.2.0.0">

instead of 

<SettingsGroup Id="XML v 1.2.0.0">

Let me summarize the instructions:

1- In Trados Studio, create your File Type configuration normally using File > Options > File Types > New from XML2.
2- Export your File Type configuration to a *.sdlftssettings file
3- Before importing it into WorldServer 11.7.x (which would lead to the error), open the .sdlftssettings file in *Notepad ++

Find
<SettingsGroup Id="Copy of XML v 2.0.0.0_2">
and replace it with
<SettingsGroup Id="XML v 1.2.0.0">

Find
<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 2.0.0.0</Setting>
and replace it with
<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 1.2.0.0</Setting>

Note: <FileTypeDefinitionId> is optional, it does not really need to be changed.

Save your change and import the File Type configuration again. The import will work. However: the filter configuration will not appear under the XML 2: Any XML File type, but under the Custom XML (Legacy Embedded Content) File Type.

- To modify the XML2 File Type Setting file to a Custom XML (Embedded Content Processor) file type configuration, follow the same step above but use 

<SettingsGroup Id="XML v 1.3.0.0">

<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 1.3.0.0</Setting>

In my tests, the segmentation was fine after the import and exactly as in Studio. However, I have used a simple test source file and a simple configuration without embedded content processor(s) enabled.

I also would like to let you know that the issue with the 0 words after segmentation does not happen on all 11.7.x environments when applying the previous workaround to the XML 2 File Type. While I can reproduce in one of my test environments, creating an XML 2 File Type and then replacing only

<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 2.0.0.0</Setting>

with

<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML: Any v 2.0.0.0</Setting>

and importing it, in several other 11.7.x test environments, the segmentation works perfectly and matches the one in Studio. I am not sure yet what is different in your environment and in the one where I can reproduce. So far I could not find out. 

I think that it would be great if you could submit a WorldServer support case so we can work on this together, exchanging files and having a call as this thread is getting too long and possibly for Community, I am afraid.

Cheers

Hi Michael, sorry, there was a typo in my previous instructions: I entered, <SettingsGroup Id="XML: Any v 1.2.0.0">

instead of 

<SettingsGroup Id="XML v 1.2.0.0">

Let me summarize the instructions:

1- In Trados Studio, create your File Type configuration normally using File > Options > File Types > New from XML2.
2- Export your File Type configuration to a *.sdlftssettings file
3- Before importing it into WorldServer 11.7.x (which would lead to the error), open the .sdlftssettings file in *Notepad ++

Find
<SettingsGroup Id="Copy of XML v 2.0.0.0_2">
and replace it with
<SettingsGroup Id="XML v 1.2.0.0">

Find
<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 2.0.0.0</Setting>
and replace it with
<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 1.2.0.0</Setting>

Note: <FileTypeDefinitionId> is optional, it does not really need to be changed.

Save your change and import the File Type configuration again. The import will work. However: the filter configuration will not appear under the XML 2: Any XML File type, but under the Custom XML (Legacy Embedded Content) File Type.

- To modify the XML2 File Type Setting file to a Custom XML (Embedded Content Processor) file type configuration, follow the same step above but use 

<SettingsGroup Id="XML v 1.3.0.0">

<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 1.3.0.0</Setting>

In my tests, the segmentation was fine after the import and exactly as in Studio. However, I have used a simple test source file and a simple configuration without embedded content processor(s) enabled.

I also would like to let you know that the issue with the 0 words after segmentation does not happen on all 11.7.x environments when applying the previous workaround to the XML 2 File Type. While I can reproduce in one of my test environments, creating an XML 2 File Type and then replacing only

<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML v 2.0.0.0</Setting>

with

<Setting Id="FileTypeConfiguration_ComponentBuilderId">XML: Any v 2.0.0.0</Setting>

and importing it, in several other 11.7.x test environments, the segmentation works perfectly and matches the one in Studio. I am not sure yet what is different in your environment and in the one where I can reproduce. So far I could not find out. 

I think that it would be great if you could submit a WorldServer support case so we can work on this together, exchanging files and having a call as this thread is getting too long and possibly for Community, I am afraid.

Cheers

Hi Caterina,

I understand and would like to thank you for the support you have provided thus far. I hope to be able to test the new variant soon (and will post here when I have). Have a great weekend!

Hi Caterina,

was able to get to it faster than I thought. It looks like everything is working now: it's segmented correctly, etc. The only thing that doesn't seem to be working is the color coding for the document structure information. Despite what I set in Trados Studio the colors all come back from WorldServer as white. Other than that, everything looks good. Thanks again for all your help!