XLF translated files error message
Hi team, I am trying to upload xlf-files, translated by ChatGPT. I have made about 20 attempts with all kinds of different configurations (with html and without, with lessons and without, with a different file name and with an identical file name, before and after having the file checked with an xml checker), but I keep getting the same error message: Check formatting or re-export translation. I get this error message when ChatGPT translates only a single sentence in the file. I even get this error message when ChatGPT gives me back the exact same xlf file, without any changes, just saved again. The only time I don't get this error message, is when I upload the identical file that I downloaded. Obviously, I am following the instructions, so I've made a duplicate of the course, downloaded the xlf file from there, and am uploading in the same location. Clearly, I am missing some sort of information here that's crucial to this process. Please assist as this is getting highly frustrating. Thanks, ChantalLanguages missing for Label Translations
Hello, I am new to Articulate/Rise, learning my way through. I need to translate courses into various languages. I have been using the XLIF and Smartcat successfully. I went to select the respective language for the label translations, and the first two were successful. When I went to do this on a third course, the languages available were cut down to 4. I lost all of the extra languages and dialects to choose from. Now it just says 'coming soon' for the extra languages. Is there a reason for this? Anyone else experiencing this? Thanks! JimUpdates to existing course in many languages, translations via Word import
Hi all, do you have any suggestions for the best approach in this situation? We have an existing course with several languages within the course, and people choose their language via branching within the course. (best approach given our LMS system) Every year the content of this course gets reviewed and updates are made. The source language is English and the updates are done in this source language by a native speaker. This review is not done directly in Articulate (reviewer no access), so the file gets exported to Word and the changes are done in that file, so the updated version can be imported again. When corrections are needed to text size, extra text boxes etc., those are taken care of manually after translation. So far so good, to update just the English version, the process is fine. Now the question is: these changes (language and lay out) need to be implemented in the other languages too. What would be the most efficient, least manual approach? To take into account: we take care of the translations internally. People who translate have no access to Articulate and do not use special translation software or XLIFF files. They look at the changes in the English text to know what needs to be changed in the local language. At this moment, to do so, we provide a translation export of the original version with the required updates marked with track changes in the translation column. Thanks a lot for sharing your experience and knowledge on this topic!
