When I import a translated Spanish word *.doc file into Storyline, all the formatting is missing and font changing to default Arial text. Although I can follow the directions from the forums to install the missing Frutiger fonts, I want to know if this would help me getting the translated texts with same formatting such as Bold, Italics etc. as matching the source Storyline document. Everything seemed fine when I did the same with version 1 in December 2014.
Example: some words and phrases are Bold with Italics, but once the translated document is imported, the associated (translations) texts are no more Bold and Italic. I did check the doc file, the source English doc file and the translated Spanish file have same formatting i.e. plain text with no bold / italics.
Then the answer would be yes in the absence of the required Font , Articulate (assumption) would default to Arial which as a by product probably strips the Formatting. Once you have the correct fonts installed this would be avoided.
But this did not happen in the same machine while using version 1 with the same file, has something changed with respect to fonts management in translations for Storyline version 2?
That I couldn't say one of the staff should be able to let you know.
However the transcript you export from Articulate should have the source formatting, in if the Transcript document is plain text with no bold / italics then when you re-import that's exactly what you will get, the ID's as i understand it are simply relational for Location within your project. the Formatting is translated back into articulate via word.
It could be you dont have Frutiger installed in word and when you opened it there it stripped the formatting rather than articulate?
I do quite regular translations into 5 languages and haven't had the same problem you have, also is the original File you are re-importing from SL1 if so (Why I don't know) might this not be the problem in that the upgraded SL2 File is incompatible in some way?
try exporting from your upgraded file (SL2) get a transcript (exported from this file) modify a few lines and reimport (using the same fonts etc) and see if the issue replicates itself.
The test *.doc document I exported now from SL2 has no formatting in it and is all in Arial, no bold or italics. yes, that's what i am getting when I import it back after changing a few lines (using the same fonts etc). the issue replicates itself and still persists. I have Frutiger font installed in my machine and word displays the font correctly when checked.
Well I am trying to do some research here and find that when we export the source text from SL2 as XLIFF it includes the font formatting details within such as :
However I do not see this in the word doc format, so i think the formatting is stripped when we export into word doc and import using the same word doc into Storyline? Alex, you mentioned that it worked with 5 languages for you. Did you use the same word doc format for import/export?
Yes we did (the formatting information is not visible (like XLIFF above in word but may possibly be contained in a hidden container within the articulate project itself Hazarding a guess )
okay, now me and my colleague figured it out that this issue is a flaw or bug in the Articulate Storyline 2. If you are working on a project that has source files from version 1 and importing the translated document into version 2. you will see this issue of formatting loss, which I think is a major bug that was overlooked and not tested thoroughly. I hope that Articulate releases a patch soon or later.
When you export text for translation, you may find that some text formatting (bold, italics, etc.) isn't saved.
This is a known issue. It'll be fixed in the next software update for Articulate Storyline. Enable the Check for updates at startup feature to be notified when the update is available.
Ok, but why wait for another update instead of a patch or bug fixes? The next update might put users again under unnecessary pressure to upgrade previous version story files and also cause license issue.. Clever marketing tactic but this isn't user friendly. Anyways I appreciate the responsiveness and support.
11 Replies
If I have understood this correctly,
Then the answer would be yes in the absence of the required Font , Articulate (assumption) would default to Arial which as a by product probably strips the Formatting. Once you have the correct fonts installed this would be avoided.
But this did not happen in the same machine while using version 1 with the same file, has something changed with respect to fonts management in translations for Storyline version 2?
That I couldn't say one of the staff should be able to let you know.
However the transcript you export from Articulate should have the source formatting, in if the Transcript document is plain text with no bold / italics then when you re-import that's exactly what you will get, the ID's as i understand it are simply relational for Location within your project. the Formatting is translated back into articulate via word.
It could be you dont have Frutiger installed in word and when you opened it there it stripped the formatting rather than articulate?
I do quite regular translations into 5 languages and haven't had the same problem you have, also is the original File you are re-importing from SL1 if so (Why I don't know) might this not be the problem in that the upgraded SL2 File is incompatible in some way?
try exporting from your upgraded file (SL2) get a transcript (exported from this file) modify a few lines and reimport (using the same fonts etc) and see if the issue replicates itself.
Thanks for the quick response Alex :)
The test *.doc document I exported now from SL2 has no formatting in it and is all in Arial, no bold or italics. yes, that's what i am getting when I import it back after changing a few lines (using the same fonts etc). the issue replicates itself and still persists. I have Frutiger font installed in my machine and word displays the font correctly when checked.
Then i am afraid i am stumped!
Might be worth running a repair on your Articulate installation and seeing if that helps Though i am just grasping at straws ! with that suggestions.
Hopefully someone will be able to assist you soon.
Well I am trying to do some research here and find that when we export the source text from SL2 as XLIFF it includes the font formatting details within such as :
FontFamily="Frutiger LT Std 57 Cn" FontSize="32" FontIsBold="True" FontIsItalic="False" FontIsUnderline="False" FontIsStrikeout="False"
However I do not see this in the word doc format, so i think the formatting is stripped when we export into word doc and import using the same word doc into Storyline? Alex, you mentioned that it worked with 5 languages for you. Did you use the same word doc format for import/export?
Yes we did (the formatting information is not visible (like XLIFF above in word but may possibly be contained in a hidden container within the articulate project itself Hazarding a guess )
okay, now me and my colleague figured it out that this issue is a flaw or bug in the Articulate Storyline 2. If you are working on a project that has source files from version 1 and importing the translated document into version 2. you will see this issue of formatting loss, which I think is a major bug that was overlooked and not tested thoroughly. I hope that Articulate releases a patch soon or later.
Hello Shiv,
When you export text for translation, you may find that some text formatting (bold, italics, etc.) isn't saved.
This is a known issue. It'll be fixed in the next software update for Articulate Storyline. Enable the Check for updates at startup feature to be notified when the update is available.
Ok, but why wait for another update instead of a patch or bug fixes? The next update might put users again under unnecessary pressure to upgrade previous version story files and also cause license issue.. Clever marketing tactic but this isn't user friendly. Anyways I appreciate the responsiveness and support.
Thanks,
Shiv
---- E-Learning Heroes wrote ----
[https://community.articulate.com/assets/logo-blue-4c6bd6e1878d802db4a1639211552d5b.png]
Hello Shiv,
This will be in an update for bug fixes, not a new version. Hope this helps!
This discussion is closed. You can start a new discussion or contact Articulate Support.