[sword-devel] API morph search (greek)

[David Haslam]

Thanks Troy,

If the order of filters has wider scope than the 3 filters already mentioned in this thread, why is only one ordering requirement noted in the wiki page for .conf files?

https://wiki.crosswire.org/DevTools:conf_Files#Elements_required_for_proper_rendering

It's not good to say so little about ordering, if what Troy just wrote is indeed the case.

Admittedly, we do say this before the table goes on to list the legacy filters:
"These filters are applied in the order that they are listed in the conf. Some filters are dependent on each other for certain features - e.g. cross-references in notes require both the OSISFootnotes and the OSISScriprefs filters enabled."

Best regards,

David

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, 7 July 2020 13:38, Troy A. Griffitts <scribe at crosswire.org> wrote:

> While I sympathize with your position, SWORD filters have always been applied in the order they are specified in the .conf file and many have order dependencies. SWORD filters are like UNIX piped commands. Order matters.
>
> Some SWORD filter authors have used inter-dependencies and we don't have a complex system of "dependsOn" properties in the filter-set so each might know of any filters which needs to run before itself, with a manager working it all out. In fact, it is conceivable that, as with UNIX pipes, different ordering might be desired for different circumstances. Filters in SWORD are simply snippets of code which conform to a SAX processing model and are dynamically configured to be executed in whatever order is specified. The way these dependencies are specified is by order in the .conf file.
>
> I really do sympathise with your position, Karl, and in practice, there is typically only a few order dependencies which exist. The alternative is to either remove these filter interdependencies altogether, or else to build the aforementioned "dependsOn" framework so a filter can specify its dependencies which need to run first, and then build the logic to organize all the specified dependencies for each specific filter pipeline and establish an order based on these, and then to change the principle that order in a .conf file is no longer a programmatic declaration of processing order.
>
> Troy
>
> On July 7, 2020 4:02:17 AM GMT+02:00, Karl Kleinpaste <karl at kleinpaste.org> wrote:
>
>> On 7/6/20 9:12 PM, Troy A. Griffitts wrote:
>>
>>> edit your morphgnt.conf file and reorder the options
>>
>> I'm here to argue that, if order of GlobalFilterOption choices matters, it's the job of the engine to enforce the correct order, internally, regardless of their textual appearance order in .conf.
>>
>> I don't think I need to provide any reasoning for this argument, because it's true by inspection: To claim otherwise is to claim that every single module creator must be aware of required ordering choices of a conceptually unordered list of features.
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20200707/80b51805/attachment.html>