I work for a translation agency preparing Rise files for translation. When the courses are to be translated into several languages, we need to make a duplicate of the course and extract the xlfs for translation for every target language, which is very time consuming. I would like to know if there is a way to export the content just once and then import the content for every language without overwriting them each time.
I'm sorry to hear you're finding the current translation process time-consuming. Unfortunately, right now that's the only option. However, I've passed on your feedback to our developers. We'll let you know if that changes in the future!
Thanks for your reply. Indeed the workflow is not very efficient and there should be a way to export the content just once for translation into several languages and them re-importing the translated content into the different language versions...
I'm bombing into this conversation, because I see you are a translation expert. We currently translate into 10 corporate languages. Other than being a long process, did you experience any issues with the export/import function to generate files for any language?
No other issues in general (that I can think of now) other than having to create a duplicate per language and extract the content 10 times in your case to make sure each later import will work with the corresponding duplicate... :-/
On the other hand, if any of your 10 languages is RTL (Ar, He...) then you will have issues to show the content correctly. There is another thread about this ;-)
I too work for a company that translates most courses into approximately 8 languages. The process for translation, especially of text to speech, is very time consuming and cumbersome. Maybe I am missing a feature? The export and import of the word file works well, with the exception of the mentioned text to speech. Any plans on an update? We actually have a platform that handles this for courses we create in our LMS. If your team is interested we could arrange a call or meeting to understand how the feature works for us.
Thanks for chiming in and offering your feedback. Please take a moment to submit a feature request here with more details about exactly what you’d like to see. Thanks :)
I really like to avoid altering the topic too much in a thread but sometimes posting on older threads doesn't get much attention, so with that 'mea culpa', here goes (but yes it's on translation!)
Allison/Nicole, is there a resource (release notes doc or something) itemizing what's in/not in the translation export file (we're still on SL2 but hoping 360 in a couple months) and the general logic to the order of the rows? For example, I thought layer names were in the export but not seeing them so suppose not.
We're also looking for tips to more easily find specific items. For example, the Identifier tag includes '.note' for content on a notes tab - simple enough.
Not to worry - we're here to help no matter the topic! 😉
Within a Storyline export for translation, you'll see the logic as follows in our XLIFF and Word exports:
Scene name as it appears in story view
Slide content
Slide name as it appears in story view
Slide notes
Layer content
and at the end of the file:
Project title
Titles of player resources
Glossary terms and definitions
Scene and slide titles as they appear in the player menu
As for Identifiers, we use:
- Title for the project title and player resources - Term for glossary term - Definition for glossary definition - Name for all scene and slide names - Note for slide notes
9 Replies
Hi Elisa,
I'm sorry to hear you're finding the current translation process time-consuming. Unfortunately, right now that's the only option. However, I've passed on your feedback to our developers. We'll let you know if that changes in the future!
Hi Allison,
Thanks for your reply. Indeed the workflow is not very efficient and there should be a way to export the content just once for translation into several languages and them re-importing the translated content into the different language versions...
Please keep me updated.
Thanks and kind regards,
Elisa
I totally get it! I'll keep you updated.
Hi Elisa,
I'm bombing into this conversation, because I see you are a translation expert. We currently translate into 10 corporate languages. Other than being a long process, did you experience any issues with the export/import function to generate files for any language?
Kind regards,
Hi Antoinette,
No other issues in general (that I can think of now) other than having to create a duplicate per language and extract the content 10 times in your case to make sure each later import will work with the corresponding duplicate... :-/
On the other hand, if any of your 10 languages is RTL (Ar, He...) then you will have issues to show the content correctly. There is another thread about this ;-)
Kind regards,
Elisa
I too work for a company that translates most courses into approximately 8 languages. The process for translation, especially of text to speech, is very time consuming and cumbersome. Maybe I am missing a feature? The export and import of the word file works well, with the exception of the mentioned text to speech. Any plans on an update? We actually have a platform that handles this for courses we create in our LMS. If your team is interested we could arrange a call or meeting to understand how the feature works for us.
Hi Hillary,
Thanks for chiming in and offering your feedback. Please take a moment to submit a feature request here with more details about exactly what you’d like to see. Thanks :)
I really like to avoid altering the topic too much in a thread but sometimes posting on older threads doesn't get much attention, so with that 'mea culpa', here goes (but yes it's on translation!)
Allison/Nicole, is there a resource (release notes doc or something) itemizing what's in/not in the translation export file (we're still on SL2 but hoping 360 in a couple months) and the general logic to the order of the rows? For example, I thought layer names were in the export but not seeing them so suppose not.
We're also looking for tips to more easily find specific items. For example, the Identifier tag includes '.note' for content on a notes tab - simple enough.
Hi Chris,
Not to worry - we're here to help no matter the topic! 😉
Within a Storyline export for translation, you'll see the logic as follows in our XLIFF and Word exports:
Scene name as it appears in story view
Slide content
Slide name as it appears in story view
Slide notes
Layer content
and at the end of the file:
As for Identifiers, we use:
-
Title
for the project title and player resources-
Term
for glossary term-
Definition
for glossary definition-
Name
for all scene and slide names-
Note
for slide notesThis discussion is closed. You can start a new discussion or contact Articulate Support.