Wrt modules guaranteed to work in every frontend - this is already not the case.
The Farsi modules do not work in BibleCS, which is odd as it can display the Arabic one fine - but seems to be a problem somehow inherent in Windows. WxSword does not work with any of the RtoL modules or complex script ones. etc... I think there might be a need to abandon the thought that _every_ module will work in _every frontend - if the frontend in question has limitations which are inherent to its platform, subsequent to not being thought through enough to exploit all the machine's abilities or simply designed as a simple one-language reader like LCDBible. Peter Chris Little wrote > No. What I'm saying is try it out in your renderer and find out whether > it works either out of the box or with one of the CSS workarounds. > > None of the front ends let you bring your own browser (unless you count > the web frontend). They're all controlled environments with set > renderers and set feature-sets. > > --Chris > > David (Mailing List Addy) wrote: >> So really, what you're saying is that it's probably not the way to go yet >> since we can't guarantee it would work in any given front end, unless we >> write an HTML renderer for them >> >> _______________________________________________ >> 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 _______________________________________________ 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
