Re: [sword-devel] Font size specification inside

2011-06-27 Thread Jonathan Morgan
Hi Peter, On Mon, Jun 27, 2011 at 5:36 PM, Peter von Kaehne wrote: > Just some clarification required: > > There are four places in ./filters where DivineName is somehow being > dealt with > > There is a GBF filter gbfosis.cpp - I think we can safely ignore that. > > There is the big OSIS to HTM

Re: [sword-devel] classes spans vs presentational encoding - was Re: Font size specification inside

2011-06-27 Thread Troy A. Griffitts
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 head

[sword-devel] classes spans vs presentational encoding - was Re: Font size specification inside

2011-06-27 Thread Peter von Kaehne
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

Re: [sword-devel] Font size specification inside

2011-06-27 Thread Peter von Kaehne
Just some clarification required: There are four places in ./filters where DivineName is somehow being dealt with There is a GBF filter gbfosis.cpp - I think we can safely ignore that. There is the big OSIS to HTML filter osishtmlhref.cpp - this is important There is osisplain.cpp - and I do no