Forum Discussion

ShMac's avatar
ShMac
Community Member
3 months ago

Localization File Issue

I’m hoping someone can help me troubleshoot an issue I ran into with the localization tool.  

Last week, I used the localization feature to translate one of my courses into French. While working on the version saved to my desktop, I was able to switch back and forth between the English and French versions without any trouble.

I published the course to Review 360 on Wednesday for feedback from my boss, and I didn’t return to update the file again until this morning. Now, the option to switch to the French version has completely disappeared. I’ve checked my desktop and our shared folders, but I can’t locate the French version anywhere.

I’ve attached a screenshot of what I’m currently seeing in Storyline in case it helps diagnose the issue.

If anyone has experienced this before or has ideas on how to recover the translated version, I’d really appreciate your help!

4 Replies

  • StevenBenassi's avatar
    StevenBenassi
    Staff
    3 months ago

    Hi ShMac​! 

    Sorry to hear you're having trouble with your localized .story file!

    I see that your support case has been escalated to my colleague, Ian. It looks like he just replied to your e-mail sharing insight and next steps.

    You're in great hands troubleshooting with Ian, and we can continue the conversation through your case!

    • SudeepaGanguly's avatar
      SudeepaGanguly
      Community Member
      20 days ago

      StevenBenassi​ Same thing happened to me, I did my 5 language translations, last time I updated few translations, saved it, and closed Storyline. next time, I opened the file and I see all my localization has just dissapeared. I am stressed as validation has started, and how to import it, I have no idea.

      • StevenBenassi's avatar
        StevenBenassi
        Staff
        14 days ago

        Hi SudeepaGanguly​ & WeraLeber​,

        I'm so sorry to hear that the localization workflow has disappeared from Storyline!

        That shouldn't be happening, and I'm unable to replicate the same behavior when testing on my end. Also, I can confirm that both of your Articulate IDs are tied to localization-enabled subscriptions. First, please confirm that you are working with locally-stored .story files as authoring directly from a network drive can introduce unexpected behavior like this.

        If you're already working locally, please try repairing your Storyline installation. If that doesn't do the trick, we're happy to investigate further. It would be helpful to see copies of your affected .story files. Do you mind uploading those items here in the discussion or through a support case?