David McDermit 

This KB offers another reason:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0039731

So open the sdlxliff in a text editor and look for these sort of characters within the translatable text... should be easy to spot with a regex search.

Paul  It sounds like this article is stating the Translator themselves might have put this coding by mistake.

I will check.  Just got another PPT file with this issue.

In my case there was not translation beyond what google mt did.

David McDermit 

Yes, it does read like that.  But what it's really saying is that the characters were introduced during the translation process.  So an MT engine is an example of where this could happen, but there are probably other ways they could get there including a bug in Studio and even manually by a translator... copy/pasting chars that look ok but are converted under the hood to an entity like this.

So I think focus on seeing if there are characters in there like that.  How they got there is another question!

Paul 

Checked the PPT file and those characters are not present, and not able to check the MT technically.  It seems that the sdlxliff file it automatically creates is fine.  The target file I created is the one that is not opening, but for that file I am unable to save a sdlxliff file to see it.

David McDermit 

David McDermit said:

Checked the PPT file and those characters are not present

No surprise there!

David McDermit said:

It seems that the sdlxliff file it automatically creates is fine.

But have you looked at the content in a text editor? This is the file you need to check, not the PPT.  Open the SDLXLIFF in a text editor and search for these chars using a regex.  So use an editor like notepad++ that supports regex search and look for something like this:

&#[^;]+;

That will find any of these strings in your SDLXLIFF.

David McDermit said:

but for that file I am unable to save a sdlxliff file to see it.

You don't need to save it, it's already there.  Just open up the location where the project is stored and copy the sdxliff from your target language folder to some other ocation of your choosing.  Then work on that one with your text editor..

Paul 

I actually used Notepad to look over the code first.  I did open the PPT sdlxliff in Notepad++ and it looks like it is only showing one slide.   Very new to Notepad++.

As for the other file that did MT.  Yes, the file created from the project I am to find.   This is what makes the MT odd.  That file you are talking about (adlxliff and Word file) work just fine.  The file that is the problem is the one I worked on in Trados and saved a Target file.  All I did in that file was copy target (chinese characters) over to blank Source side.  That Save As Target file (one I am unable to create sdlxliff file) is the one with this error.  How can the automatically created file work fine but not the other one.

David McDermit 

Can you share the sdlxliff with me?

Paul can I email it to you?

David McDermit 

Sure… pfilkin @ SDL dotcom 

Paul 

Can tell have too much on my plate.  I totally forgot about this one point.    I take the sdlxliff file from the translator and bring it into Trados myself and Save a New Target and it worked.