Hi Jeff Carota ,

Assuming you're using the latest Studio version, try re-exporting your Frame Maker file to XLIFF 2.0. There might have been an issue during the initial export process that caused the error.

If the error persists, you might need to manually edit the XLIFF file. The error message suggests that there's a segment in the file that the software is trying to interpret as a tag pair, which is causing the issue. You'll need to locate this segment in the XLIFF file and correct it.

Please note that manually editing XLIFF files should be done with caution, as it can potentially lead to data loss if not done correctly. Always make a backup of your file before making any changes.

I hope this helps!

Regards,

Oana

I do not see a prompt in FM for xliff 2.0.  I did get more infomation with the segment but do not know how to decipher where it is in the file...can you assist with what segment this pertains to?

I do not see a prompt in FM for xliff 2.0.  I did get more infomation with the segment but do not know how to decipher where it is in the file...can you assist with what segment this pertains to?

 Jeff Carota 

Jeff Carota said:

I do not see a prompt in FM for xliff 2.0. 

That's a bit confusing as you said this:

Jeff Carota said:

This is for a Frame Maker Structured file that was exported to XLIFF 2.0.

However... I don't believe Framemaker does offer an export to XLIFF at all.  So if the source file you have is an XLIFF 2.0 it may be worth running it through a validation tool first to check if it's indeed valid.  Trados Studio is quite strict about these things so that would be my starting point.

It's also worth checking the error message is this can also be helpful:

1. click on "Knowledge Base" as this uses the error details with the message to search the KB and sometimes finds the right article to help
2. click on the small disk symbol.  This allows you to save the full error details to your desktop and then you can attach them to your post.  These often contain details that can be helpful too.

Jeff Carota said:

I did get more infomation with the segment but do not know how to decipher where it is in the file...can you assist with what segment this pertains to?

This will most likely be in the SDLXLIFF, so try searching for that trans-unit id in a decent text editor.  It might be helpful... it might not!

Thank you Paul, I have extracted the error message but cannot decipher it correctly.  Can you assist in letting me know more about this issue with the below log report?

 Jeff Carota 

The error log provided from Trados Studio suggests that there's an attempt to treat a segment object as a tag pair object, which is incompatible.

This error surfaces during the parsing process of your XLIFF file, as indicated by the source `Sdl.FileTypeSupport.Filters.Xliff` and the stack trace pointing towards operations involving tag pairs and parsing XML. The operations involved suggest that the error occurred while the system was trying to end a tag pair during the processing of an XLIFF document, but encountered a segment object instead of the expected tag pair object.

Given the context, the most likely source of the problem, as I suggested before, is the structure of the XLIFF file being processed, where there might be discrepancies or unexpected formats that the Trados Studio XLIFF parser is not handling correctly. This could be due to custom tags, incorrect nesting of elements, or other anomalies in the XLIFF structure that do not align with what the parser expects. To resolve this issue you probably need to go back to your client and ask then to check that the file is valid xliff.

But if you want to try and fix it yourself check the XLIFF file for any irregularities in the tag structure, especially around the areas where segments and tag pairs are defined. Look for incorrect nesting or usage of tags that might not be standard.

You could also use an XLIFF validator tool to ensure that the file conforms to the XLIFF schema. This can help identify structural issues that might not be immediately obvious.

However, keep in mind that if you fix it yourself the target file might not be compatible with whatever system they used to create the xliff in the first place. So my recommendation would be you validate the error to make sure that this the problem as it’s always possible Trados Studio is the culprit here. Then go back to your customer and explain the problem.