Maria Luisa Barbano

While it seems to me your process through Studio worked ok, meaning import/export I understand you cant open the file in MemSource. 
This would suggest an issue on memsource side, but if you are able to share your file I can try run through some tests to see if we can help you.

Lyds 

Thank you so much for your offer Lydia! Can you pls. provide an email where I can send the file? Many thanks!

For anyone who could be following this thread.

The error from Memsource is far from helpful and despite the file in question is a mxliff, it can be opened in Studio with the relevant plugin installed.
It's at this point the "error" Studio gave was far more transparent as to what is wrong with the file

If you then open the mxliff in an editor environment like notepad++ and locate this spot I found these

From my experience, it could be anything not just < /> but nevertheless when they are removed/replaced the file then opened well in Studio and in Memsource.




Concern would be that there where more than 1 instance of these in the document and for the purpose of troubleshooting I simply removed them and left a blank space. The question now would be how best to handle these < /> as they are part of the source and clearly not parses optimally when the bilingual files are being created.

While we at RWS have an article about this for our own native files which can be found here, I am not at liberty to assume for this native file.

Maria Luisa Barbano  it a pleasure progressing to a state where the file can be opened and the translations retrieved

Lyds

For anyone who could be following this thread.

The error from Memsource is far from helpful and despite the file in question is a mxliff, it can be opened in Studio with the relevant plugin installed.
It's at this point the "error" Studio gave was far more transparent as to what is wrong with the file

If you then open the mxliff in an editor environment like notepad++ and locate this spot I found these

From my experience, it could be anything not just < /> but nevertheless when they are removed/replaced the file then opened well in Studio and in Memsource.




Concern would be that there where more than 1 instance of these in the document and for the purpose of troubleshooting I simply removed them and left a blank space. The question now would be how best to handle these < /> as they are part of the source and clearly not parses optimally when the bilingual files are being created.

While we at RWS have an article about this for our own native files which can be found here, I am not at liberty to assume for this native file.

Maria Luisa Barbano  it a pleasure progressing to a state where the file can be opened and the translations retrieved

Lyds

Thank you very much for your help Lydia!

Best, Maria Luisa