Forum Discussion
Query Regarding Localization and “Save Translation As” Option in Storyline
Hi AnuVarghese-394, we recommend using a language trigger condition to help with situations like this. This article, "Articulate Localization: Create Multi-Language Storyline 360 Projects," provides helpful information on working with that condition. I hope that helps. Please let us know if you have any questions.
Hi GingerSwart
Thank you for your input. The scenario my team is facing is a bit different, and I’m sharing the details below along with images for reference:
- The team used checkboxes/shapes to show task progress. However, after translation, the checkbox placement does not align with the translated text. It seems these alignment issues need to be addressed individually as standalone files. (Attachment: alignment issue)
- Even with full localization, the variable values and prompt text in feedback layers are not matching in some slides. If these are not fixed individually, it should impact the functionality of the project file. (Attachment: variable issue)
My question: Can the team keep the translation stack intact for future updates (text changes) while using “Save Translation As” to address the above issues without incurring additional charges?
or are we allowed to make changes to a translated text? Does editing the translated break its connection with source file?
