<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Agreed. Because a frontend doesn't do something with the entry attributes created by the filter, or that a chosen render filter doesn't do anything with the morpheme seg, certainly doesn't mean the WLC module is defective. Frontends are not always the target of the engine. Research can be done with the engine directly. Render filters are always growing to do more with the markup sent through them.<br><br><div class="gmail_quote">On December 30, 2017 6:31:47 AM MST, DM Smith <dmsmith@crosswire.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The module matches what the filter expects.<div><br></div><div>The filter does something.</div><div><br></div><div>Third possibility: front end doesn’t handle the attribute.</div><div><br></div><div><div>— DM Smith<div><br></div></div><div><br>On Dec 30, 2017, at 3:54 AM, David Haslam <<a href="mailto:dfhdfh@protonmail.com">dfhdfh@protonmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div>My concern is that we have a listed filter that either seems to <u>do nothing</u></div><div>or that the module[s] where it's specified <u>do not match</u> what the filter expects.</div></div></blockquote></div></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>