Receiving the following message in my translation : state="translated

Question

Hi, I have started using SDL Trados 2019 since March this year and everything was going smoothly. However, after receiving a notification requesting me to update my Trados to the recent one, I started experiencing difficulties as my translated XLIFF files are now having the following sentence "state=translated which has nothing to do with my translation. I spent the whole shift yesterday trying to fix it, and I was not successful. Can anybody assist please. This is how it appears

RAIL_CALLING_ORDER_LINES RAIL_CALLING_ORDER_LINES

No help is available for this page. Aucune aide n'est disponible pour cette page

Paul · Answer

Kasongo Bajika 
 Why is this a problem? The state attribute is normally expected in XLIFF files. You can change the translated attribute-value to be something else, but there is no way to avoid writing something in there.

Paul · Answer

Kasongo Bajika 
 Two things... 
 Kasongo Bajika said: I am busy translating a big document in HTML language. 
 Then why is XLIFF even an issue here? You can translate the HTML directly. 
 Kasongo Bajika said: the client is complaining that the document cannot be downloaded as he is receiving errors message. 
 Can you share the error message? If the state is really causing this error then your client is the one at fault here for not supporting XLIFF correctly. 
 http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#state

Daniel Hug · Answer

Kasongo Bajika 
 Are you returning the generated target file or the XLIFF file to your customer? It almost sounds like you are sending the XLIFF file back. 
 If you finalize a project, Studio will generate a target file in the original file format. That would be HTML in your case. In the same folder will be the bilingual translation file (SDLXLIFF). 
 
 The target file (ICML in the above screenshot, HTML in your case) is what you send back to your customer. 
 Daniel

Daniel Hug · Answer

Kasongo Bajika I don't know which program your client used to convert the HTML to XLIFF, but it's unusual that he should not be able to import your XLIFF. As Paul said, it's correct. If deleting the state attribute solves your problem, you could do a "replace all" and replace with in Notepad++, which is free software. All these batch operations carry a certain risk, so make a backup copy before you start. The whole thing is a bit surprising - that your client's software can't read a nomal XLIFF file. But a similar issue was dicussed here, it seems: https://community.sdl.com/product-groups/translationproductivity/f/studio/5779/tu-contains-target-state-translated-in-xlf-file Daniel

Trados Studio > 6. AutoHotKey

Receiving the following message in my translation : state="translated