<<< text/html; charset="utf-8": Unrecognized >>>
___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
I suspect an error in Dom’s conf maker script accounts for the filter’s
presence in CPDV.
Those seg elements shown in bold are unrelated to morph segmentation.
Not every seg element has that function!
I was once told that one JSword based app (STEP Bible?) supports morpheme
segmentation and do
David Haslam wrote:
Might Xiphos be enhanced to implement this in future?
I currently see 3 modules that claim this:
cpdv.conf:GlobalOptionFilter=OSISMorphSegmentation
hinerv.conf:GlobalOptionFilter=OSISMorphSegmentation
turntb.conf:GlobalOptionFilter=OSISMorphSegmentation
All Xiphos can do i
From the source documentation: This filters toggles splitting of morphemes (for
morpheme segmented Hebrew in the WLC).
So this seems to be a module specific filter.
The filter,
https://crosswire.org/sword/apiref/osismorphsegmentation_8cpp_source.html,
It governs how segmented text is handled (
Does any SWORD front-end app include support for this ?
GlobalOptionFilter=OSISMorphSegmentation
Might Xiphos be enhanced to implement this in future?
The SWORD engine knows about it, yet AFAICT, it effects no change in displayed
text.
What it ought to do was once suggested by someone at STEP
I have a question about pointer lifetime and management when interacting
with libsword: who owns the lifetime and delete management of pointers
coming out of the SWMgr and SWModule calls? For instance: if I create an
SWMgr object and fetch a SWModule* from its get module methods, who owns
deletion
