“My .exe is different than your .exe,” said Mac to Win.

Why should a Captivate developer worry about .txt?

If you are using Closed Captioning in your modules, then you should worry about .txt.  It’s well-documented in the forums that copying and pasting from a .docx into Captivate’s Slide Notes leaves residue formatting that can make your Closed Captioning quite ugly.

So where does the Mac .txt vs. Windows .txt conflict play into this?

I asked my client to save the narration text from a .docx crosswalk  as a .txt so I could upload it quickly into Captivate’s Slide Notes. He obliged and uploaded it from his P.C. to Sharepoint.  I downloaded the .txt from the client’s Sharepoint onto my iMac and tried to open his .txt on TextEdit This is what I got:

Symbols were substituted for only some spacing, and other strange formatting appeared for contractions.  There was no way I could use this for Closed Captioning.  It looked weirder than the .docx formatting. Regardless of what I did, I could not get rid of those formatting quirks.

Read the full story by

Tags:

RELATED READS
L&D Is Stuck… And Here’s What We Need To Do About It Assets: no download option on elearning bros
We are updating our Privacy Policy, so please make sure you take a minute to review it. As of May 25, 2018 your continued use of our services will be subject to this new Privacy Policy.
Review Privacy Policy OK