Am 26.08.10 06:19, schrieb Chris Little: > > > On 8/25/2010 5:20 AM, Karl Kleinpaste wrote: >> Chris Little<chris...@crosswire.org> writes: >>> If you mean to embed the audio in-line, I would recommend using the >>> <figure> element. There's nothing specifically image-oriented about the >>> element, aside from implications made by its name. >> >> Yes, there is: The XXXhtmlhref filters wrap the resulting HTML<img> >> element in<a href="passagestudy.jsp?action=showImage..."> for the sake >> of letting the application kick off a standard external viewer, if it >> knows how to do so. > > 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.
In the "New Oxford American Dictionary" the term "figure" can also have the meaning of audio/music where "a short succession of notes producing a single impression." > 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 This would produce an entry attribute? > 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). HTML5 would be fine. Which else standard is there that could be used instead? However, the HTML5 audio tag doesn't define attributes like for example start/stop time for playing fragments within a large audio file. How could this be handled? Manfred _______________________________________________ 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