Please find my file through the link below:

https://drive.google.com/file/d/1xnDxtLsRhku3GoBv-czB5zyIR9c60PZX/view?usp=sharing

Thank you! 

bcsd Taiwan 

I have the same issue as you.

I’ve quickly checked the XLIFF and I see you have changed the structure somehow, because there are plently of returns that shouldn’t be there.

For example these returns followed by spaces make me think you have changed the XLIFF outside Trados Studio:

Looking at these returns+spaces no wonder there are errors with the XLIFF you have shared. You may go back to an XLIFF copy without these returns with or without indentation spaces.

I can get those indentations using prettfy tools, such as the ones included in Notepad++. Have you use them or a similar tool? If so, please share a copy of the XLIFF not processed in this way.

Just to be clear, these returns in the header are fine:

Thank you for checking my file!

I use Visual Studio Code to check coding but didn't change anything. The origin xlf file was sent to the other translator and the link below is the file he returned for me to edit. I'm not sure if he changed anything with the file outside Trados Studio.

https://drive.google.com/file/d/1ozeikeiB15DytjAG1F1oR-ET26mTnZi2/view?usp=sharing

bcsd Taiwan 

This XLIFF has the same issue in Trados Studio: it doesn’t allow to create the target file.

If you had opened it in Notepad++, you’d have seen the same wrong return characters (plus spaces to indent) highlighted above in red colour.

I don't know if deleting those return characters (and spaces) will fix your issue, but I’d try, but they shouldn’t be there. Trados Studio didn’t add them. There are around 6,000 returns+spaces and then the returns after header. In a decent editor such as Notepad++ shouldn’t take long to delete them and then try if target creation works.

Because I'm not familiar with coding stuffs, am I correct that you suggest I can try deleting the spaces and "LF" using Notepad++?

bcsd Taiwan 

bcsd Taiwan said:

m I correct that you suggest I can try deleting the spaces and "LF" using Notepad++?

Yes, LF plus spaces for indenting. This is the search regex pattern that you can used:

\n  +

Then, you will need to remove the returns outside the header.

If it doesn’t work, or alternatively, you can pre-translate the original document with the TM.

I see now that the original document is an XLF file, so the issue with the returns can be there as well, so if I were you, I’d check first this original XLF file (Can you create the target from the original XLF? Does the XLF have returns as well?), because maybe the solution is asking a nice XLF to your client.

bcsd Taiwan 

bcsd Taiwan said:

m I correct that you suggest I can try deleting the spaces and "LF" using Notepad++?

Yes, LF plus spaces for indenting. This is the search regex pattern that you can used:

\n  +

Then, you will need to remove the returns outside the header.

If it doesn’t work, or alternatively, you can pre-translate the original document with the TM.

I see now that the original document is an XLF file, so the issue with the returns can be there as well, so if I were you, I’d check first this original XLF file (Can you create the target from the original XLF? Does the XLF have returns as well?), because maybe the solution is asking a nice XLF to your client.

Thank you for the instruction! However, after deleting the spaces, I still got the same Error msg.

Could you check my file below and see if I done it correctly?

https://drive.google.com/file/d/1fp82N6SO3sIMIBHS5dCCUF1pRT_Bqecg/view?usp=sharing

And the link below are the original files received from my client:

https://drive.google.com/drive/folders/1nwGwSCZfejFGT9c5PuXlsmvbM_TvFyiD?usp=sharing

Hi bcsd Taiwan 

I’ve created a new project with the original XLF file. I didn’t translate anything, just generated the target and I got this error:

So my bet is that there is something wrong with the oiginal XLF file. Sorry, I don’t know what can be wrong… I’d talk to your client and ask for a direct XLF file (you can see indentations as well in this XLF).

I see. Thank you very much though for the testing and suggestions!