Does the config key order for GlobalOptionFilters matter to JSword ?
If not, that’s another argument for fixing SWORD as Karl argues.
David
Sent from ProtonMail Mobile
On Tue, Jul 7, 2020 at 08:34, David Haslam <dfh...@protonmail.com> wrote:
> I agree with Karl, though it is noted in
> http://wiki.crosswire.org/DevTools:conf_Files#cite_note-strongs-17
>
> http://wiki.crosswire.org/DevTools:conf_Files#cite_note-15
>
> This seems to be the only config key group where the Key order is significant.
>
> Can this be solved in SWORD 1.9 ?
>
> David
>
> Sent from ProtonMail Mobile
>
> On Tue, Jul 7, 2020 at 03:02, Karl Kleinpaste <k...@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.
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
