New Localization Feature Trouble
I'm wondering if anyone else is experiencing this. We are trying out the localization feature for a course. We ran the AI, published to the review 360, and went through to make changes/validate. However, instead of all the changes we made being imported back into RISE like they are supposed to, the RISE file just perpetually says Applying Updates. None of the human changes we've made are actually being incorporated into the original file, which makes the review feature not usable as it resulted in A LOT of wasted staff time. Is this just us? Anyone else encountering this? Screen recording of the issue we're encountering here.Storyline 360 Localization - change navigation text?
Hi, We've been doing a lot of localication using the automated tool inside storyline. So far we've been using Spanish-Mexico. Our nav arrows are then labeled PREVIA and SIGUIENTE. I had to do a Spanish-Spain one today and instead of using the PREVIA and SIGUIENTE, it used ANT and SIG. I cannot edit these labels in the player editor. Is there a way to force them to still be SIGUIENTE and PREVIA even when doing Spanish-Spain? I looked in the review 360 language validation to see if I could update it there, but no luck. Where can I do this? Thx, LoriRejecting Automatic Format Change
How do I undo/reject automatic format change in Articulate Storyline? What I want the text to look like: (1) What it gets auto corrected to: ① What I have to do to make it more like what I want: ( 1 ) I need the text to look exactly like (1) with no spaces around the number and no stupid circle around the whole thing. How do I make this happen? My file will be translated into many languages, so it needs to be translation friendly.Articulate Localization: Spanish translation consistency
The Articulate Localization workflow has saved us time and simplified reviews. We’re looking for ways to maintain translation consistency across course updates. Last year, our English course was translated into Spanish (Spain) by a translation team. This year, we updated the English version and used Articulate Localization to generate a new Spanish (Spain) translation. We also used Articulate’s glossary template and added key terms from last year’s course. When comparing the Articulate translation to last year’s translated version, we noticed differences in phrasing and wording. For those managing translated courses: How do you maintain consistency with a prior translation when using Articulate Localization? How much wording variation between versions is typical? Have you found Spanish (Latin America) translations to be more consistent, or do you have tips for better aligning AI translations with an existing Spanish (Spain) translations? Thank you!Localization: tokens / translation?
I recently did a trial phase of the localization feature but didn't pay attention to how many tokens are used for each translation. Could someone share this info with me? Let's say I have an English course and want to translate it into German, French and Spanish - how many tokens would each translation cost me? And if, at a later point, I want to add an additional Japanese version? Would it only subtract tokens for this one additional language? Thank you :)Localisation an Custom Blocks
I'm at a loss. At first, I thought it was because something was wrong with the links in the translations—some texts from the custom blocks are translated, some are not. I have translated 11 languages here, and even though we have invested in localization, I have to maintain everything manually. And even if I maintain the languages manually and translate the text that was not maintained in Chinese into Chinese, it is for example also in Chinese in Polish. Has anyone else had this problem? How did you solve it?Copy of a localized (multi language) file cannot be published to a NEW review name
HELP! I created a file and localized it with English/Spanish. I published for review. It went great. Now I need to make a similar file, so I started with my existing file and made a copy of it. Made a whole bunch of changes, updated translations, etc. But when I go to publish to review 360, it wants to publish to the original review. But this is a NEW file. How do I fix this? Do I have to start over every time with a non-localized file and redo all the formatting (getting rid of scroll bars, etc) again? I should always be able to publish as a NEW review when I want to. Please advise.DeepL translations and xlf files don't work
When I export an xlf or xliff file from a Rise course and then drop it into the DeepL translator (Pro version), it displays an error message: Course Title.xlf This file couldn’t be translated due to a technical issue. (unsupported_document_version) Anybody know why this happens or knows of a workaround? Thanks.
