Closed Captioning misreading of apostrophes

[jonathans18491493]

We are rolling out Closed Captioning using Adobe 2019. However, when apostrophes and ampersands are used, the Closed Captioning converts these characters into an "a" with an accent mark over it. Our possessives and contractions now look like they are misspelled. Does anyone know how to get around this?

[Paul Wilson CTDP]

Presumably, you copied and pasted this text from a word processor or a set of presentation slides. If you copied content that included hidden formatting from the original files this can sometimes happen. I use an application called PureText (Windows) that allows me to remove all text formatting from an application like the aforementioned. 

[jonathans18491493]

Thanks Paul. I shared your response with the designer that is handling this Captivate project and he reported that the text was cleaned and entered directly. Also, it looks fine on his machine, but then the problem comes up once shared via a URL from a server.

[RodWard · Accepted solution]

Ask the designer if he first published out to HTML5 and then viewed it from a localhost server on his machine or just previewed from within Captivate (which would likely have shown him an SWF output preview).

The issue is likely that the punctuation marks in your HTML5 output are being interpreted as code in the HTML5 output when it is played from a web server.  To avoid the issue you would need to remove the offending punctuation marks or escape them or replace them with specific letter combinations that will be interpreted by the web browsers and rendered as the punctuation you want.

Watch Your Punctuation Online

[jonathans18491493]

Thanks Rod.

Looks like the issue was HTML5 misreading the apostrophe as code.

Since we use an LMS and the issue goes away in SCORM, we can live with the HTML5 misreading as we use that for internal review only.