Forum Discussion

LilyKreiting007's avatar
LilyKreiting007
Community Member
1 month ago
Solved

Error translating a Rise course

I'm trying to translate a Rise course from English to French. I've followed all the steps outlined in Rise. I've exported to an XLIFF file, I've run it through the company's machine translation engin...
rise 360
  • LucianaPiazza's avatar
    LucianaPiazza
    1 month ago

    Hello LilyKreiting007​, 

    I see that you've opened a case and are working with our colleague, Genelyn. You're in excellent hands! We'll continue the conversation over in your case, so everything is in one spot! 

    Have a great start to 2026! 

MicahBHardt's avatar
MicahBHardt
Community Member
2 days ago

Hiya! 

My team and I are experiencing a similar issue to this, with the same error -- we reviewed the XLIFF files that our translation program is spitting out and it doesn't seem to match the example photo that was included. . .  We are seeing <source> and <target> tags, but they are different. . . ours lists it as <target state = "final"> 

Are we able to share what the final resolution to this is/was so we can keep troubleshooting? 

  • StevenBenassi's avatar
    StevenBenassi
    Staff
    1 day ago

    Hi MicahBHardt​,

    Sorry to hear you're also experiencing errors when translating a Rise course using XLIFF.

    After checking LilyKreiting007​'s support case, I can confirm that we have this behavior logged as a bug in Rise 360. This bug causes:

    • Importing an XLIFF file fails, and produces a "500 internal server error" in the console.

     

    Also, we've determined that this bug is content-specific and occurs when the amount of Lesson content reaches a large volume. We've also observed other common themes, such as:

    • A Custom Block is always present in the course.
    • The bug does not occur if "Include HTML formatting" is unchecked when exporting the original XLIFF file.

     

    Please let me know if these examples apply to your affected Rise course. I'm happy to include your voice in the bug report that's being tracked.

    Looking forward to hearing from you!