Tamil and Teluga Storyline 2 courses
May 10, 2016
We are using Storyline 2 to create courses for Tamil and Teluga and getting corruption issues in the player.
To translate the content for the players we have extracted the player content to XML, had it translated and are importing the translated XML file back in to the course. We have changed the fonts as required for the languages but are still experiencing issues with corrupt characters. I have seen in posts that there may be issues with 'stacked characters' in Presenter could this be the same issue?
Has anyone successfully translated either of these to Indian dialects?
5 Replies
Hi Kimberly,
I'm not familiar with these specific dialects, but if you're having difficulty and have already checked the initial items of ensuring you're working on a local drive with your .story file and your imported files, that they adhere to the naming conventions here, and that you're using the latest update of Storyline 2 Update 8 - I'd want to have you work directly with our Support Engineers and share the problematic files.
Hi Ashley,
I just wanted to check back in and share the information we have relating to the initial issues with Tamil and Teluga languages.
To prevent font corruption in projects with languages that are not recognized by
Articulate Storyline 2, publish in Storyline 2 - update 8 or above.
and
Choose Publish > Publishing for HTML5 and mobile devices > Include HTML5 output
This has resolved our issue and we have published the translated file for Tamil and Teluga.
Kind regards,
Kim
Thanks Kim for that update and sharing it here with the ELH community! So it seems that Update 8 and later allowed for the use of these languages that previously didn't work as expected in earlier versions?
Yes, we were able to create the content as expected using update 8 and later as well as publishing Publish > Publishing for HTML5 and mobile devices > Include HTML5 output
Great - just an FYI Kimberly that responding via email includes your signature here so you're welcome to edit the post to remove that information if you'd like.
This discussion is closed. You can start a new discussion or contact Articulate Support.