[sword-devel] One of those weird ideas....
refdoc at gmx.net
Tue Sep 18 15:50:51 MST 2007
Troy A. Griffitts wrote:
> 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
> 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?
That is what I meant, yes. I have for example 150 psalm readings in
Farsi and would simply set them as
> We could conceivably talk about somethink IN the body like:
> "To hear this greek word pronounced, <seg type="x-audio"
That in turn is yet another interesting way to make use of the feature.
Essentially once the feature is enabled I presume it would function
exactly the same way as the images currently - which can be delivered
with explanatory text etc. The weighting of text vs audio vs image would
be largely a matter for the module designer.
> 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
>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel