Mark Owens 

Mark Owens said:

It does not matter if the leading space is in an attribute or in an element, the space(s) is lost.

I think is probably the wrong choice of words because the spaces are not lost, they are just not needed.  If you use View all Content with a filter you'll see this:

The spaces have been moved outside because there is normally no reason for them to be in the segment.  In fact putting them in there is more likely to lead to problems as thy would be easily missed, or even deliberately corrected.

If I translate this file, save the target, then all the spaces are retained.

If I then create a new project and use Perfect Match against the original then the spaces are similarly still there in the new target file.

So your problem is that you have an sdlxliff file where the spaces were not moved externally and now you are presumably creating projects with something different to the way the original one was created and now Perfect Match isn't perfect anymore.

I'm not sure how to work around this without seeing a simple example of exactly what you're faced with, but it would have to be a workaround to deal with files that are simply prepared in different ways as this isn't a bug.

Mark Owens 

Mark Owens said:

It does not matter if the leading space is in an attribute or in an element, the space(s) is lost.

I think is probably the wrong choice of words because the spaces are not lost, they are just not needed.  If you use View all Content with a filter you'll see this:

The spaces have been moved outside because there is normally no reason for them to be in the segment.  In fact putting them in there is more likely to lead to problems as thy would be easily missed, or even deliberately corrected.

If I translate this file, save the target, then all the spaces are retained.

If I then create a new project and use Perfect Match against the original then the spaces are similarly still there in the new target file.

So your problem is that you have an sdlxliff file where the spaces were not moved externally and now you are presumably creating projects with something different to the way the original one was created and now Perfect Match isn't perfect anymore.

I'm not sure how to work around this without seeing a simple example of exactly what you're faced with, but it would have to be a workaround to deal with files that are simply prepared in different ways as this isn't a bug.

Hi Paul, 

Well you live and learn! Sure enough, I created a Trados project with the above file and did a translate, then did a generate and the leading space is re-inserted into the output document.

Comparing the SDLXLIFF generated by Trados with the SDLXLIFF generated by Passolo, I can see that the Trados segment does not have the leading space, and the Passolo segment does have the leading space.

If I use the Passolo export as-is, then I do not get a perfect match.

if I edit the Passolo export to match the Trados SDLXLIFF file, I get a perfect match.

So I need to write something to strip out the extra leading spaces from the Passolo SDLXLIFF files before using them against a Trados project.

I will get in touch with the Passolo guys to see if they can align the SDLXLIFF export feature to write the same SDLXLIFF as Trados - these Passolo export files are supposed to be used with Trados after all.

Best Regards

Mark