Forum Discussion
translation troubles - xliff, mxliff... and course duplication
Hello,
My question is a bit of a mixed bag, as this is my first Rise project that requires translation. Of course, it needs to be an "all out" effort with 8 languages.
- I saw too late that I would have needed to duplicate the course 8 times, and now re-upload the xliff file to the corresponding version. What???? I have no idea where that requirement is coming from, I frankly have to say it doesn't make sense to me. As I'm now sitting on ONE duplicated course (that I had intended to clone 7 more times...) - what's the next step / workaround? How can I make the xliff files match the course? I can't really go back and ask the translators to take a new xliff file and ask for a do-over.
- The second issue I'm facing is that I received (so far) mxliff files. It looks to me as if our translation management system only supports mxliff as output, not xliff. Is there any way to convert the files to xliff? mxliff contains both languages, which of course wouldn't work for the upload if Rise only expects xliff.
20 Replies
Here's a thought that might work if you haven't tried this already. Be careful, you may lose your 'original' course in the process so do this first:
1. Create another duplicate of the 'master' course you did your XLIFF export from. This will be your backup.
2. From the 'master', import your first XLIFF file.
3. Make a duplicate of the course that you imported the XLIFF into.
Repeat steps 2 through 3 with the rest of your XLIFF files. Just be sure to go back to the 'master' each time.
As for the mXLIFF format, I haven't come across that before but if you have a small snippet you can share, I would be happy to take a look to see how multiple languages are being added to the file.
Although XLIFF files are a bit overwhelming to look at, if you change the extension to .xml and drop it in your browser (Chrome, Edge, FireFox, etc.), it's much easier to see what is going on.
Hi Susanne,
To ensure the xliff files match each course version and upload successfully, you’ll need to export an xliff for each language version. You should have eight course versions, 1 for each language. You can find details here: Rise 360: Translate Your Course.
To help identify which XLIFF files go to the correct course, you can rename the title of each duplicated course to indicate its target language. So when you export an XLIFF file for each course, you'll know which file goes to which course by the name.
As for mXLIFF, I haven't personally encountered this kind of translation file. In searching, this seems to be a format specific to Memsource. Rise only accepts xliff files, so hopefully, Thor’s suggestion on converting the mxliff file type will help!
I'd be very keen for a fix to this problem too. Thor's solution is workable, but has the potential for any number of mishaps.
It makes sense that we should be able to import an xlif in to a copy of the course. Does anyone know of a way to modify the xlif to allow for this?
David, I did not go down that path - I'm not enough of a programmer :-) What I ended up doing is to import the translation into my original file, and then copy to a new course. That got rather messy, as it was hard to keep track of which of my clones was the original course, especially when I got a second / improved version of a translation and needed to reimport. I think that creating a copy for each language will take care of that. What other mishaps are you thinking of?
I ended up uploading the translation into my original course, then make a copy, then upload the next translation into the original course... which is a version control nightmare. I hope that I won't need to make any updates before the course is updated in English after 12 months. Lesson learned: next time, I will create a version for each translation, and then deal with the files separately. It's not pretty, but it's the way for now.
I don't have enough programming background to try and change the course ID in the xliff file. I don't even know which editor to use, and where to look... Following the steps that somebody posted here for the HTML edit for Arabic (right-to-left) was feasible, but I'd like to leave it at that.
This is what I ended up doing too, took a lot of concentration and a spread sheet to make sure I got it correct! I had 13 courses and 4 different languages on top of the English versions so it was a huge task. Lesson also learned.
Hi,
Did you manage to import MXLIFF file to Rise or found some alternative?
Best regards,
Sandra
I went back to the translator and got the xliff from them. All other attempts did not work out.
I did not find an alternative. The translation team sent me an xliff file, and I was able to upload that.
I am reading this thread and dreading what I have to do now to get my three courses into Spanish. Send help.
Make copies of the courses and export the xliffs from those, then reimport the translated xliffs in to your copied courses.
Makes sense. Except I got the XLIFF files delivered a few months ago. I kept them in my folders until I got the green light from my supervisor that we're ready to deploy the Spanish content. When I duplicate the original course and try to upload the XLIFF I got from the translation agency, I get the prompt that the XLIFF doesnt match the course. So I'm guessing I will have to implement the workaround shared in this thread, which will be a massive concentration challenge as you mentioned in your last post. Not looking forward to this.
Ah, okay. Good luck!
Thank you. I'll need it.
Hello Andrea,
Just thought I would jump in and offer some suggestions (hopefully they'll be helpful!)
Sounds like the XLIFF file you're trying to import is for the original course and not the duplicate you created. Since you have a duplicate, think of this now as your English course and then you can apply the XLIFF to your "original" course.
This way you will still have both courses except they've swapped places.
With this approach, there is some risk though -
- I don't know if the course is in production and what implications there might be with updating, etc.
- The other possibility is that you changed the original between the time you got the translation and to now. If it's different enough, the XLIFF import may still not work.
I actually have one more solution I can talk with you about that may make this even less daunting. Please feel free to private message me or reach out via LinkedIn if I don't respond (sometimes private messages aren't delivered.)
Hi Thor,
Thank you for reaching out. Yes, I understand the process. My first though was actually what you mentioned in your second bullet point. However, I'm 90% sure the content hasn't changed, which is why I was so confused in the beginning. Definitely what must be happening is what you mentioned in the first bullet point.
I will try your suggestion in a few minutes. I've postponed the activity out of fear of messing up (thank you, ADHD!). I'll keep y'all posted! Hopefully it works!
