<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 20/12/2012, at 7:06 AM, Manfred Bergmann <<a href="mailto:manfred.bergmann@me.com">manfred.bergmann@me.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">a) what are the XHtml filters. What are they for? Do they do anything different than the HtmlHref filters?</div></blockquote><br></div><div>Don't think anyone answered this question?</div><div><br></div><div>Right now they're almost exactly the same. The idea is that these can be hacked to do things more properly rather than the horrid html that is produced by the htmlhref filters... Almost like a fresh start, altho not much has been changed so far.</div><div><br></div><div>Ideally they should produce loads of html code with classes for all the display markup (such as <a href="blah" class="strongs">), rather than using loads of markup elements (such as <small><em class="strongs"><a href="blah" class="strongs">) which is what we currently do...</div><div>Why bother with all those markup elements AND using classes, when using appropriate classes would make the use of the markup irrelevant? :/</div><div><br></div><div>Compare my hacked version of osishtmlhref.ccp:67 at <a href="https://bitbucket.org/niccarter/pocketsword/src/74e571ae219c821e1aaf9764d8c43ae7b52ffb9f/externals/sword/src/modules/filters/osishtmlhref.cpp?at=default#cl-67">https://bitbucket.org/niccarter/pocketsword/src/74e571ae219c821e1aaf9764d8c43ae7b52ffb9f/externals/sword/src/modules/filters/osishtmlhref.cpp?at=default#cl-67</a></div><div><br></div><div>to the equivalent line in osisxhtml.cpp:79</div><div><br></div><div>But I am hoping that the xhtml filters will be properly updated and work will be done to validate the xhtml output. ;)</div><div>I would have tried this long ago, but I gather there is too much attachment with the filters for any one front-end to attempt to change them? hence my fork of the htmlhref filters for use in PS. :)</div><br></body></html>