[sword-devel] One of those weird ideas....

[Troy A. Griffitts]

Peter,

It would certainly be possible with the current engine software.  It would
be dependent on the frontend to handle the new data in a module.

We just need to decide the best way to include information about audio and
what it means.  We've heard some good suggestions.

If audio is present, we'll need a Feature=Audio in the .conf
and then a normal way.  For images we use <img
src="relative/path/to/resourced"/>. For audio we could use <seg
type="x-audio">relative/path/to/resource</seg>

A simple filter to pull these into an entry attribute for frontends to
easily grab would be straight-forward.  Likely under:
["Audio"]["001"]["src"] = relative/path/to/resource

Are we all in agreement that the usage we are talking about is an audio
resource which is EQUIVOLENT to the body of the entry?

We could conceivably talk about somethink IN the body like:

"To hear this greek word pronounced, <seg type="x-audio"
subtype="x-inline">relative/path/to/resource</seg>"

Thoughts?

  -Troy.



peter <refdoc at gmx.net> wrote: 
>So back then to the sound files - would this be a possibility?
>
>_______________________________________________
>sword-devel mailing list: sword-devel at crosswire.org
>http://www.crosswire.org/mailman/listinfo/sword-devel
>Instructions to unsubscribe/change your settings at above page
>
>