Forum Discussion
Translation import from Word loses formatting
I see that this is a very old conversation and was hoping there was a fix or workaround for this issue. We normally just muscle through, as I am sure many others do, but still see this come up regularly. With larger projects it can add hours to formatting efforts after import, and could to errors that could potentially get passed on to a client.
I have noted this with both Word and xliff export/import, using the latest version/updates.
Thanks,
Matthew
- JoseTansengco2 years agoStaff
Hello Matthew,
If you're using Storyline 360's Enhanced Word Translation, you should see the formatting of your text get preserved after importing a translation file.
When importing your translation file, can I ask if you have this option enabled for your Storyline 360 installation?
If this option is already enabled, try doing a repair of your Storyline 360 installation to see if this helps. This procedure will also bring you to the latest available version of Storyline 360.
If the issue persists, open a case with our support team here for further assistance!
- MatthewDollinge2 years agoCommunity Member
Good morning Joe,
I am seeing this with an xliff export/import.
Before and after import example images attached.
Thank you,
Matthew
- StevenBenassi2 years agoStaff
Hi Matthew!
Thanks for clarifying and sharing what you're seeing on your end!
It looks like the issue revolves around missing paragraph spacing after importing back a translated XLIFF file. I'd be happy to offer some extra insight!
Testing this out on my end, exporting an XLIFF file, the formatting remained the same after importing it back to my Storyline 360 project. Everything was working as intended! I've attached some examples of my results for your reference as well.
When exporting from Storyline, I used XLIFF version 1.2. May I ask which version you used when you encountered this issue?
It's possible the issue is specific to the file itself. Would you be willing to share it here in the discussion or privately through a support case? It would be helpful to take a closer look, as well as test it out on our end to see if we can reproduce the behavior. We'll delete it from our system once troubleshooting is complete!
Related Content
- 11 months ago
- 1 year ago