I exported the content to xliff and translated it into French. The structure of the translated xliff and encoding all match the original English. But when the French xliff is imported back into the Story file, some of the French characters are appearing as their numeric code values instead of accented characters. For example:
Définition appears as Définition
This is only occurring in certain areas of Storyline. They are all appearing correctly in the slides, in the text boxes.
Where they are not correct are in the hover boxes (when in Story View and you hover over a slide or scene), layer names, triggers (name of the slide or layer), slide names (under the slide).
Changing the font does nothing. Already using a Unicode font throughout.
So why does the text on the slides appear correct but not in other areas of Storyline?
Hi, Christine -- So sorry to hear of your troubles! Have you had an opportunity to review this information on when XLIFF Translation Doesn't Work? Hope that helps and please let us know if you need further assistance. :)
Yes, I've seen that post and all of the states are set to "translated" as translations are definitely importing.
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com ---------------------------------------------------------------------------------------
Hi, Christine -- Thank you for your response and for verifying that you have read the article I shared previously.
Can you also please confirm that you are not working on a network drive? As stated here, working anywhere other than on your local C: drive is not recommended as you could run into unexplained behavior or file corruption. If you continue to have difficulties, you may want to try importing the file into a new file, or run through the steps to repair Storyline.
I have the same problem. After the xliff import the umlauts are not correct. Please take a look at the attachment. What can I do to solve that?
I already had submitted a support case ( # 00834526). For a global playing company it is essentially to work with the xliff-Format. I also wonder why the original text is tagged as"en". We are working with a German storyline version and in the player setting German is also adjusted, so if the translation agency would import the xliff. The German text is marked as "en" and no automatic translation could work. :/
There are many other posts regarding that issue, here are only a couple of them:
Currently it seems that there is no professional translation possible. The first entry, which I had found, regarding to this issue is over 3 years old! This is not a acceptable time frame for a main feature of a professional software I think. If that is right, it could be so serious that also other global companies would no longer use Storyline for their content productions, which I find a pity.
Hi, Evelyn -- Thanks for reaching out and I took a look at the case that you are currently working on with Ryan, one of our Support Engineers.
It appears that when he asked if you have tried changing the font of the player to Arial Unicode MS per this article, you shared, "I've tried that. Both, before Export and also after Import. It isn't only after publishing. It is also viewable in Storyline. The Font "Arial Unicode MS" is installed in Windows. I've checked this in the systemcontrol". Unfortunately, I do not have additional technical insights to offer at this time, so I will be sure to continue to monitor the progress being made on your case so that I am able to share updates here for others who may be following along.
I have exactly the same issues as Evelyn and totally agree that this is unacceptable for a main feature of a global software. You seem to be supporting Word doc but totally ignoring xliffs. My client is now supporting translation via xliff and we would really appreciate some support here to get this working as it should.
It's been two months since your reply to Evelyn and still there is nothing to report, even though this issue was raised 3 years ago.
I have been singing the praises of Storyline since inception and am really disappointed with the lack of support for this particular issue. Can you restore my faith in your product?
7 Replies
Hi, Christine -- So sorry to hear of your troubles! Have you had an opportunity to review this information on when XLIFF Translation Doesn't Work? Hope that helps and please let us know if you need further assistance. :)
Yes, I've seen that post and all of the states are set to "translated" as translations are definitely importing.
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
Hi, Christine -- Thank you for your response and for verifying that you have read the article I shared previously.
Can you also please confirm that you are not working on a network drive? As stated here, working anywhere other than on your local C: drive is not recommended as you could run into unexplained behavior or file corruption. If you continue to have difficulties, you may want to try importing the file into a new file, or run through the steps to repair Storyline.
Hello Christie
I have the same problem. After the xliff import the umlauts are not correct. Please take a look at the attachment. What can I do to solve that?
I already had submitted a support case ( # 00834526). For a global playing company it is essentially to work with the xliff-Format. I also wonder why the original text is tagged as"en". We are working with a German storyline version and in the player setting German is also adjusted, so if the translation agency would import the xliff. The German text is marked as "en" and no automatic translation could work. :/
There are many other posts regarding that issue, here are only a couple of them:
Currently it seems that there is no professional translation possible. The first entry, which I had found, regarding to this issue is over 3 years old! This is not a acceptable time frame for a main feature of a professional software I think. If that is right, it could be so serious that also other global companies would no longer use Storyline for their content productions, which I find a pity.
Hi, Evelyn -- Thanks for reaching out and I took a look at the case that you are currently working on with Ryan, one of our Support Engineers.
It appears that when he asked if you have tried changing the font of the player to Arial Unicode MS per this article, you shared, "I've tried that. Both, before Export and also after Import. It isn't only after publishing. It is also viewable in Storyline. The Font "Arial Unicode MS" is installed in Windows. I've checked this in the systemcontrol". Unfortunately, I do not have additional technical insights to offer at this time, so I will be sure to continue to monitor the progress being made on your case so that I am able to share updates here for others who may be following along.
Hi Christie
I have exactly the same issues as Evelyn and totally agree that this is unacceptable for a main feature of a global software. You seem to be supporting Word doc but totally ignoring xliffs. My client is now supporting translation via xliff and we would really appreciate some support here to get this working as it should.
It's been two months since your reply to Evelyn and still there is nothing to report, even though this issue was raised 3 years ago.
I have been singing the praises of Storyline since inception and am really disappointed with the lack of support for this particular issue. Can you restore my faith in your product?
Hi Tex!
Would you be able to share your project file with our support team as well as this is still an active issue with our QA Team.
This discussion is closed. You can start a new discussion or contact Articulate Support.