STEP just uses 2 colours to show different parts, alternating between the two. We're also in the process of creating a new dataset to be able to identify and define each part of each Hebrew word as it's used in the text. So the user can hover over part of a word and get the specific meaning for that segment.
On 31 March 2014 12:29, David Haslam <[email protected]> wrote: > It may well indicate that, Chris, though of course, not all words are long > enough to be segmented. > > I'm most interested to learn what should change visually when the filter is > toggled. > > Should the segments of such words be made more apparent by displaying a gap > between segments > or even a delimiter between them? Or is it up to the front-end developer to > decide how? > > How does STEP allocate the colours to the segments? Is it by segment order > within each such word? > > And, referring to my first post, should there be a diatheke option provided > for this filter? > cf. Diatheke can be regarded as a front-end, even though it's a command > line > tool. > > Best regards, > > David > > > > > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/OSISMorphSegmentation-tp4653792p4653828.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: [email protected] > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page >
_______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
