Skip to main content
This topic has been closed for replies.

2 replies

Participating Frequently
October 30, 2012

I just had this similar experience with Captivate 6. Any solution made for this?

Participant
November 27, 2012

I localize my Adobe Captivate projects in up to 9 languages (including Korean and Chinese) and have found the imports to be VERY sensitive to any changes in the Word doc, such as reformatting the table containing the text, or changing anything about the English source text. I typically highlight the cells where I need the translators to enter the localized text and make it very clear to them that they should not touch anything else in the document.

I've also encountered problems importing the closed caption text if I delete the English audio files between the time I export the captions and then try to reimport the translated versions. Closed captions are somehow linked to or associated with the audio files and won't import as expected if there is no longer an audio file attached to the slide.

Has anyone experienced problems exporting caption files? I have a project now that exports the text captions for the first 19 or 20 slides and that's all--the rest of the text captions and all of the closed captions are omitted. Anyone have any ideas what might be causing this?

Inspiring
November 27, 2012

I don't localize my Captivate projects, but I have at times had problems with 'round-tripping' the captions to Word and back to Captivate, where the changes made in Word were not updated in Captivate. I haven't experienced this problem with version 6 so far, but it happened fairly often with Captivate 5 and 5.5. I don't know what was causing this irregularity. Sometimes saving the Captivate project, reopening it, and re-importing the Word changes fixed the problem and sometimes not.

Participant
August 8, 2012

This procedure did not work in Captivate 6.

The objects exported and the import of translated text stated it was successful, but the text did not translate.

Any suggestions?

Sankaram
Adobe Employee
Adobe Employee
October 30, 2012

Hi All,

     May I know What you guys are trying? I presume that you are exporting the XML and updating the strings with different locale and re-importing the XML doesn't reflect the updated strings in Captivate project. If that is the case, verify your exported XML for the validity, as it might contain invalid characters.

Do the following for successful locale import:

1) Export the project as XML.

2) Open the XML in chrome browser --> which shows line containing invalid character.

3) Open the XML in XML editor (You can use Notepad ++)

4) Go to that line and you can see invalid character.

5) Delete the invalid character.

6) Repeat steps 2 to 5 till you can see valid XML in chrome.

7) Change the locale strings.

8) Import the XML.

You should be able to view the locale changes.

Let me know if that works.

Thanks,

Sankaram.

Inspiring
November 5, 2012

I had the same problem. I edited the XML in Edit Pad Pro. When I took your suggestion and opened the XML in Chrome, Chrome said that there was an error. But the error wasn't highlighted and I couldn't find the error. Therefore, I couldn't fix the error.

Is there a simpler, more accurate way to import and export XML from Captivate 6, and to edit it without errors? Do you recommend a specific editor - maybe there is one that is better to use than Edit pad Pro?