• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 3126 views
  • Users 0 members are here
Options
Related

xlf/xlz, encoding

Valérie Gravel

Hello, 

One of my client exports files from Xyleme (Learning Content Management System) and gives me .xlf file ou .xlz.
I was able to process both file type in Studio 2015.

The first one required to open it in notepad, edit the langage pair and tags.

The second one worked fine.

 

However, the client says he has a problem with importing back the file into Xyleme because the encoding from the original file is utf-8 and that since it has been process in Studio, the encoding chaged to ANSI.

I found nothing about Studio changing the encoding in files, do you have any details about that? 

Could you provide a workaround for that type of file, maybe i am doing something wrong.

 

Thank you very much!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello Valérie,

    There are indeed cases with some file types when Trados Studio is not sure about the input file encoding and will try to heuristically deduce it. I don't know if it will work in your case, but check if the xlf/xlz files have the encoding attribute on the namespace declaration.

    Do your files have this snippet of code as the first line?

    <?xml version="1.0" encoding="UTF-8"?>

    If they have only <?xml version="1.0"?>, please add the encoding atttribute as seen above. I think this will solve your issue if the file encoding indeed has been changed and is not an error on your or your client's part.

     

    Regards,

    Raul
Reply
  • 0

    Hello Valérie,

    There are indeed cases with some file types when Trados Studio is not sure about the input file encoding and will try to heuristically deduce it. I don't know if it will work in your case, but check if the xlf/xlz files have the encoding attribute on the namespace declaration.

    Do your files have this snippet of code as the first line?

    <?xml version="1.0" encoding="UTF-8"?>

    If they have only <?xml version="1.0"?>, please add the encoding atttribute as seen above. I think this will solve your issue if the file encoding indeed has been changed and is not an error on your or your client's part.

     

    Regards,

    Raul
Children
No Data