Forum Discussion
Q&A: Nova — AI, & Credits
Thanks for laying out the real-world impact here, AngeliqueHB, I can see why this matters for the business case you're building.
I want to be upfront. There isn't a reliable way to estimate characters or cost before translating a course today. That's a known gap on our end, not something you're missing.
Two workarounds exist, though both only give you a rough floor, not an accurate number. You can export a Storyline course to Word and use Word's character count, or export the XLIFF file from a Rise course. Either way, I'd treat whatever number comes out as a baseline rather than something to build a firm budget around. The real character count tends to run higher, since formatting like bold text adds characters that a plain word count won't capture.
Only, when you have chosen the AI localization, the other export options are no longer there...
+ The AI localization translates anything and everything, including every slide title and variable. These are things I sometimes don't need to have localized. (for example in a project with no menu in the player, or when screenscraping, a slide can be just a mouse movement...)
So when translating a course, Ideally I need to be able to have a cost for what the translation will be, to see if that cost can be motivated versus the purpose of that training...
- EricSantos9 days agoStaff
Hi JurgenLepla,
Thanks for following up, and for flagging that the export options disappear once a course is localized. You’re right, and I should have been clearer about when the Word export works.
The Word export gives a rough baseline only on a regular Storyline file, so it has to be done before any languages are added, for example on a copy of your source course. Once a course has been translated with Articulate Localization, the export options aren’t available.
It sounds like you’d want to be able to leave out content you don’t need translated and see the cost up front, so you can decide whether a translation is worth it for the training. At the moment, on-slide text, slide notes and text variable values are all translated automatically, and there isn’t a way to leave items out. There also isn’t a way to see the cost before translating, and I don’t have a timeline to share. We’re continuing to track the need for a cost estimate.
Which slide elements do you most often need left untranslated, such as titles, variables or notes?
- JurgenLepla7 days agoCommunity Member
1. If I do TTS, I keep a copy of the script in a text field below the slide, to know the text that is spoken there, without having to open the audio each time. The same text goes into the narration generation, and in the captions. The same text is translated 3 times, sometimes differently, and will be consuming credits each time?
Notes are translated too, so there is no way to have any developer only comments on the slide, if you are planning to localize...
2. When using a variable, and you are using the value of that variable (%variable% = 22) These fields should not get translated.
3. It is really annoying if a change of language also changes the size of the font. There is no reason why German text should be higher than English text. Or that extra line breaks are added.
Related Content
- 2 months ago
- 10 months ago
- 17 days ago
- 2 months ago