dfhdfh at protonmail.com
Sat Dec 30 10:08:51 MST 2017
There are at least two separate reasons why the WLC module is "defective".
They are unrelated to this thread. My use of the adjective was an "aside".
Both issues were reported ages ago in the CrossWire tracker for MOD.
Neither issue has been addressed. Just about par for the course.
i.e. We have a tracker system that might as well be a black hole.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
> -------- Original Message --------
> Subject: Re: [sword-devel] OSISMorphSegmentation
> Local Time: 30 December 2017 4:44 PM
> UTC Time: 30 December 2017 16:44
> From: scribe at crosswire.org
> To: SWORD Developers' Collaboration Forum <sword-devel at crosswire.org>
> 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.
> On December 30, 2017 6:31:47 AM MST, DM Smith <dmsmith at crosswire.org> wrote:
>> The module matches what the filter expects.
>> The filter does something.
>> Third possibility: front end doesn’t handle the attribute.
>> — DM Smith
>> On Dec 30, 2017, at 3:54 AM, David Haslam <dfhdfh at protonmail.com> wrote:
>>> My concern is that we have a listed filter that either seems to do nothing
>>> or that the module[s] where it's specified do not match what the filter expects.
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel