6 Replies
Paul Knights

Thanks Crystal.

While your at it perhaps you can also ask them why we cannot use 'web fonts' like we normally do for html5 development if that's the case. I get an awful lot of queries from backend IT guys about the fonts being turned into vectors/png's etc ... if its html5 text then it should be held in the .html files etc??

Clients could then edit the text themselves to a small degree.

Crystal Horn

Hi again, Paul.  I am able to provide context around the way the slide output works in terms of copying text.

We currently have both Flash and HTML5 output available as publishing options. Ideally, we want users who access either output to have a consistent experience with slide content. Because Flash output must render text differently than HTML5, we opted to disable the copy functionality in HTML5 to preserve consistency.

Other considerations we’ve taken include intellectual property concerns and trigger functionality. Intellectual property has especially been important to our users, and we’d have to ultimately be aware of the impact on course authors if we made text (and other course elements) available from the output.

I can also appreciate the fact that you’d like to make minor modifications as easy as possible for your clients post publish. We are really shy about ever recommending changes to the published output, and we just can’t support it. The best practice will always be to make edits in the authoring environment and republish the course.

I know it’s a functionality that you’d prefer, so I’ll submit a feature request on your behalf. Here’s how we handle feature ideas from you.

Thanks again for asking and sharing your thoughts!