On Thu, Aug 26, 2010 at 12:19 AM, Chris Little <chris...@crosswire.org> wrote: > No, there is nothing specifically image-oriented about the <figure> element. > That Sword filters always interpret it as an image is irrelevant to my > point. > > Moving forward, we can mandate that (for Sword) non-image data embedded with > <figure> be tagged with an attribute (e.g. type="x-audio") or we can add the > tag ourselves in the importer by reading filename extensions. Then the > OSISHTMLHREF filter can watch for type="x-audio" and generate <audio> or > whatever (depending on whether we're targeting HTML5 or something else).
As an interesting footnote to this, I stumbled across this article today while looking at the HTML5 audio/video spec: http://sharovatov.wordpress.com/2009/06/05/html5-video-tag-and-internet-explorer/ Seems that using images to display video has a precedent much older than us (though now abandoned). --Greg _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
