Storyline doesn't yet support "Thai" as a language. (It's not included among the languages in Player > Text Labels.) Will this by any chance get added in the next months to year?
Is it possible to publish a course with Thai characters nevertheless? (More specifically, I will want to import a Thai translation of an existing English course into Storyline and am not sure if the lack of Thai in the Text Labels menu will make this impossible.)
Dear all, thank you for this very useful information. I also would like to see Thai in 360 as an additional language. Thailand has a fast growing economy and is getting very important. Is there any thought on including Thai in 2019? If not, can you recommend any other text to speech engines for Thai in the meanwhile?
Folks here found that some accent symbols in their Thai text are missing. Our team is still looking into that issue, but I don't see any other reports for the boxes you see on your text. So sorry you're running into that!
A few questions to start:
Do you see those boxes during Preview, in the published output – or both?
Is this happening with all fonts, or just the Arial Unicode MS one?
With your permission, we'd like to take a look at your .story file. It'll help us get a clear picture of what's going on and we'll delete after troubleshooting. If that works for you, you can send that Storyline file to us privately in a case here. We'll give it a test in a similar environment and let you know what we find!
Hi, any update on this? Trying to publish Thai from 360. Preview is ok then once zip is created uploaded to LMS, boxes appear and character spacing is jumbled.
Thanks for letting us know what's going on. What you're seeing sounds similar to a bug we've got our eye on in Storyline 360. However, you mentioned everything looks correct when previewing in Storyline, so there may be something else going on here.
With your permission, we can take a look at your project file to investigate what's happening. We'll delete it when we're done troubleshooting. If that works for you, you can upload your file privately to our support team here. We'll give it a test and let you know what we find!
I am having the same problem with upper intonation marks - I imported the translation text in Tahoma font, as recommended by the linguist translating the text. The intonation marks show in the Storyline file, but when I preview or publish the course - the intonation marks do NOT display on the screen. The Thai reviewer indicates that the word is 'misspelled" without the intonation mark. These posts are over a year old - Have you found a solution???
This is still an open issue with our team. This conversation is attached so that we can share any updates that we have directly with you here.
Have you looked into using Arial Unicode? Our internal testing and many of the users in this conversation mention that this works better for the marks needed for the Thai translation.
Hi, any update on this issue? I am also experiencing this issue with losing the upper intonation marks upon preview/publish. I don't seem to have a problem with Arial Unicode or Tahoma, but it does not work properly with Leelawadee, which is a Thai-specific font.
I stand corrected - I have do an issue in the player when using Arial Unicode MS as the Player Font. When I open the published module in my LMS, the Resume text is not displayed properly. The first character in the "Resume" header has a box around it. I double-checked the text labels, and there is no box. The attached screenshot shows the relevant text label on the left, and the dialog box on the right. I changed the Player Font to Tahoma, and that seems to be working fine.
Yes, there is a workaround, but I have wasted an incredible amount of time tweaking, publishing, uploading, testing, over and over again, all because of a font issue that was reported at least two years ago. I really hope this gets resolved soon. I don't imagine that many non-native Thai speakers would even notice that those tiny marks are missing, and they are unknowingly publishing incorrect content. My team now has to do a full audit of our Thai course catalog to ensure that everything was published correctly.
Thank you for checking in on this bug! I'm glad you were able to find a workaround as well.
Unfortunately, I don't have an update to share. You're right; we logged this bug two years ago. We are currently looking into other factors, such as how many customers the bug affects and how seriously those customers are impacted. We also consider how difficult the bug is to fix, and if fixing it might cause other problems with the software.
Once we’ve prioritized the bug, it goes into our development team’s work queue in order of priority. If I hear of any news, I'll report back to this discussion.
Alex - I had some issues when using Arial Unicode MS as the player font. However, Tahoma seems to be working well, both for the player and for slide content.
Hello, any news on that issue? I would like to start a thai language version of a WBT, but do not know, if this will end up in trouble or if it will work meanwhile with Storyline 360.
Thanks for checking in! We haven't released a bug fix for this error with missing Thai characters in Storyline 360. In the meantime, I see there are workarounds listed in this thread. We'll keep you updated when we have more information on a fix.
This workaround (using Tahoma) was working with the Storyline update up to February.
Articulate has managed to break this workaround by releasing many updates for Storyline after that one and none of these updates has fixed this issue, BUT now it is not possible to go back to Feb version anymore. The oldest I can go back is to a March version.
How can I get hold of an update from Feb to install?
58 Replies
Hi Jeff,
We do have the same issue reported for Storyline 3 as well.
I'm adding this thread to the report as we track user impact and it will allow us to update you here as well.
This post was removed by the author
This post was removed by the author
Is there any chance that this issue will be fixed soon?
Hi there Rasmus,
I don't have an ETA for a fix just yet, but we will certainly keep you posted. Really sorry this bug is causing headaches for you!
Dear all, thank you for this very useful information. I also would like to see Thai in 360 as an additional language. Thailand has a fast growing economy and is getting very important. Is there any thought on including Thai in 2019? If not, can you recommend any other text to speech engines for Thai in the meanwhile?
Hello Matthias! Thanks for sharing your perspective. The issue with Thai tone marks in HTML5 output is still open with our team, but it sounds like you might be looking for additional Thai language support. Would you mind elaborating for us exactly what you'd like to see for Thai language here? It's the best way for us to track those requests! Here's a close look at how we manage feature requests.
Thanks!
Arial Unicode MS
Hi Jyri,
Do you need help with that font and Thai language, or suggesting that's what folks use?
If you can share any more details, happy to help.
I am using SL3 and have used the Arial Unicode MS font but there is still issue like having square around the words which Thai languages doesn't have.
Hi, Sameer. Thanks for that screenshot!
Folks here found that some accent symbols in their Thai text are missing. Our team is still looking into that issue, but I don't see any other reports for the boxes you see on your text. So sorry you're running into that!
A few questions to start:
Arial Unicode MS is the only font I found where the tone marks are in the place.
Is there some other fonts that works with Thai?
Thanks, Jyri. That's similar to what our team has found, and I'll let them know you reported similar. We'll keep you posted on this issue here!
Hi, any update on this? Trying to publish Thai from 360. Preview is ok then once zip is created uploaded to LMS, boxes appear and character spacing is jumbled.
Hi Damien!
Thanks for letting us know what's going on. What you're seeing sounds similar to a bug we've got our eye on in Storyline 360. However, you mentioned everything looks correct when previewing in Storyline, so there may be something else going on here.
With your permission, we can take a look at your project file to investigate what's happening. We'll delete it when we're done troubleshooting. If that works for you, you can upload your file privately to our support team here. We'll give it a test and let you know what we find!
I am having the same problem with upper intonation marks - I imported the translation text in Tahoma font, as recommended by the linguist translating the text. The intonation marks show in the Storyline file, but when I preview or publish the course - the intonation marks do NOT display on the screen. The Thai reviewer indicates that the word is 'misspelled" without the intonation mark. These posts are over a year old - Have you found a solution???
Hi Amy,
This is still an open issue with our team. This conversation is attached so that we can share any updates that we have directly with you here.
Have you looked into using Arial Unicode? Our internal testing and many of the users in this conversation mention that this works better for the marks needed for the Thai translation.
Hi, any update on this issue? I am also experiencing this issue with losing the upper intonation marks upon preview/publish. I don't seem to have a problem with Arial Unicode or Tahoma, but it does not work properly with Leelawadee, which is a Thai-specific font.
I stand corrected - I have do an issue in the player when using Arial Unicode MS as the Player Font. When I open the published module in my LMS, the Resume text is not displayed properly. The first character in the "Resume" header has a box around it. I double-checked the text labels, and there is no box. The attached screenshot shows the relevant text label on the left, and the dialog box on the right. I changed the Player Font to Tahoma, and that seems to be working fine.
Yes, there is a workaround, but I have wasted an incredible amount of time tweaking, publishing, uploading, testing, over and over again, all because of a font issue that was reported at least two years ago. I really hope this gets resolved soon. I don't imagine that many non-native Thai speakers would even notice that those tiny marks are missing, and they are unknowingly publishing incorrect content. My team now has to do a full audit of our Thai course catalog to ensure that everything was published correctly.
Hi Katy!
Thank you for checking in on this bug! I'm glad you were able to find a workaround as well.
Unfortunately, I don't have an update to share. You're right; we logged this bug two years ago. We are currently looking into other factors, such as how many customers the bug affects and how seriously those customers are impacted. We also consider how difficult the bug is to fix, and if fixing it might cause other problems with the software.
Once we’ve prioritized the bug, it goes into our development team’s work queue in order of priority. If I hear of any news, I'll report back to this discussion.
Hi all,
Is using Arial Unicode MS the best solution for this issue as of now?
I have a client who was experiencing the same issue with Thai vowels overlapping, and I am looking the most feasible option.
Alex - I had some issues when using Arial Unicode MS as the player font. However, Tahoma seems to be working well, both for the player and for slide content.
Hello,
any news on that issue? I would like to start a thai language version of a WBT, but do not know, if this will end up in trouble or if it will work meanwhile with Storyline 360.
Hi Selin!
Thanks for checking in! We haven't released a bug fix for this error with missing Thai characters in Storyline 360. In the meantime, I see there are workarounds listed in this thread. We'll keep you updated when we have more information on a fix.
This workaround (using Tahoma) was working with the Storyline update up to February.
Articulate has managed to break this workaround by releasing many updates for Storyline after that one and none of these updates has fixed this issue, BUT now it is not possible to go back to Feb version anymore. The oldest I can go back is to a March version.
How can I get hold of an update from Feb to install?
Thank you!