Forum Discussion
Translation of Rise Course
Hi Irina!
Thanks for working with Renson and Vic in your case. Vic recently sent you an update, and I'll share it here for anyone else using Trados 2017 or Trados 2019.
Our team ran further tests using Trados 2017 and Trados 2019, and we confirmed that the option Do not store segmentation information in the translated file is available in both versions of Trados Studio.
To summarize, if you're having trouble translating a Rise XLIFF file in Trados Studio, enable the option Do not store segmentation information in the translated file in both areas of Trados Studio. Here's how:
- File > Options > XLIFF > Settings > Do not store segmentation information in the translated file
- Project Settings > File Types > XLIFF > Settings > Do not store segmentation information in the translated file
Doing this will ensure the <seg-source> tags are not included in the file, and you can import it into your Rise 360 course without any issues.
If you need a hand with either of those steps, our Support Team is here to help.
Hi Alyssa,
I realise that this is an old thread, but we are experiencing the same problem at the moment and trying to understand the implications. We are working with an external translation company that is using Trados (not sure what version), and the XLIFF file that they have sent us displays empty text blocks after import. The code does include <seg-source> tags, can I assume from the above that these are not compatible with Rise360? The follow-up question is if we remove them, will this affect the formatting or display of HTML content such as tables etc?
Cathy Evans
- EricSantos8 months agoStaff
Hello Cathy,
Sorry for the trouble with the translation. We'd like to take a closer look at the XLIFF file to make a better recommendation. Would you be willing to share it privately in a support case? We'll reach out soon after we hear from you!