As DM has suggested, I am all in favor of copying the current osis to
htmlhref filter (or actually copying and merging in the changes from
webif filter) to osisxhtml and slowing changing markup to use classed
spans and providing a SWBuf OSISXHTML::getHeader(); method which would
supply a basic header to prepend to a display object when rendering.
Obviously a frontend could supply their own or use this as a base but
override whatever they wanted. Initially it would return a string like:
"
.divineName {
font-variant: small-caps
}
...
"
Thoughts?
Troy
On 27/06/11 10:35, Peter von Kaehne wrote:
> On 25/06/11 21:47, ref...@gmx.net wrote:
>> As Jonathan has explained, this is about ..
>
> Sorry got confused here, reading emails on a phone. Now back on computer.
>
> Anyway, the serious question is : as we have already discussed a bunch
> of times, there is a serious case for classed spans for a lot of things
> we do currently by presentational layout.
>
> Is there any remaining obstacle to it?
>
> I.e. is there any frontend reliant on osishtmlhref.cpp which can not
> apply a (more or less) simple stylesheet onto the html produced by the
> filter?
>
> Otherwise - what stops us?
>
>
> Peter
>
>
> _______________________________________________
> 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
_______________________________________________
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
