I have intensely been working to learn the new Captivate 6 especially regarding the output to HTML6 since our online classroom is going mobile this year.
I have published a project and all the text has been turned to images. At first, I realized that I had not used a websafe font, so I went through and changed all the fonts to one that were websafe. They are all still turning to images. Is there a font or a method to get the html version to publish out as text so that the file size is smaller, the strain on the device is less (right now my project will not play on a mobile yet it plays in preview - I think the images are loading it down), and allows the text to be selectable as you would find in a webpage?
Thanks in advance for any help anyone can give.
Thanks Rod. I think you answered my other question here in this one, but showing me that there is a another gallery deeper in the files did the trick. I will post your answer over in my other question so if anyone does a search in the forum with a similar query they will find the answer there in that question.
Anyone still game to answer this question about fonts that will publish out to html as text instead of images?
Well, I did some testing. I couldn't find any fonts that didn't get turned in to images. I did play around with making the same project in Muse, just out of curiosity. The same project in Muse had 34 objects versus over 600 for Captivate because of the fonts getting turned to images. Another advantage that I saw in the Muse version was when on an iPad you zoomed in the fonts from the Muse version was just as crisp as they were at standard size. Bitmapped images wouldn't be able to do that.
OK, so one of my expectations, the accessible HTML text, might not have been met. I am still happy with the product, especially considering this is the first release with the HTML5 added and it is still such a new standard it isn't an easy task to get it added in there. Maybe a future feature will be that you are shown what fonts are web-safe and if you chose them you can opt for them to stay as real fonts instead of images. That way you have a smaller file size, clean text even on zoom on mobile devices, and the viewer is able to copy-paste text if you want them to.
Actually this makes me quite curious. Can someone from the HTML5 team chime in here and help us to understand why Adobe chose to go this route for the HTML5 output? On the face of it, if font characters are being converted into images for HTML5, this would seem to mean that a typical Cp6 project it likely to have hundreds (if not potentially thousands) of extra objects to be requested and downloaded from the web server. Each separate request will take extra milliseconds that could add up to a significant amount of latency for this type of output.
Surely there must have been a trade off or benefit of some kind that outweighed the possible latency?
Hmmm, it looks like there must be a way for Flash to publish with editable text since I discovered it at an artist's website at http://www.themaninthehatart.com/. I can select the text and copy it yet it is definitely Flash-based. I wonder if a widget might be possible that could turn this on in our published projects for both Flash and for HTML5?