Forum Discussion

lorraineS's avatar
lorraineS
Community Member
1 day ago

How to get Wordcount in a Storyline localized file?

Is there any way to generate a wordcount, notes and/or CCs, plush text on screen for a Storyline 360 file that has been localized? I need this to give to my proofreaders. 
Because I've used Storyline's localization feature, I no longer am able to export to XLIFF/Word. I can publish a "print" document, but that brings in slides as images and so the text on screen doesn't get counted.  

Any ideas?

Thanks,

  Lori

localization
storyline 360

3 Replies

  • muhammadammar23's avatar
    muhammadammar23
    Community Member
    17 hours ago

    Unfortunately, Storyline 360's localization workflow has a limitation: once a course is converted to a localized version, the Export to Word/XLIFF options are no longer available for that localized file.

    A few possible workarounds:

    • Generate a translation package before localization and keep it as a reference for word counts.
    • Use Publish → Word (Print) and extract the text from the resulting document, though as you've noticed, on-screen text embedded in screenshots won't be counted automatically.
    • If you still have access to the source project and translated XLIFF files, use a CAT tool or word-count utility on the translated XLIFF.
    • For proofreading, some teams publish the localized course to Review 360 and have proofreaders review the content directly in context.

    At the moment, there isn't a built-in way to generate a complete word count (including on-screen text, notes, and closed captions) from a localized Storyline file. It may be worth submitting this as a feature request, as it's a common need for localization and QA workflows.

    • lorraineS's avatar
      lorraineS
      Community Member
      2 hours ago

      Our team does have proofreaders use the review360 links. However, I believe the wordcount is needed to provide the cost/fee offered to the proofreaders (contractors). They are asking for the wordcount in the target language. So even going back to a pre-localized version and generating xliff won't help because it's not in the target language. Thanks for the ideas though.