<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">See below:<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 20, 2017, at 2:27 PM, David Haslam <<a href="mailto:dfhmch@googlemail.com" class="">dfhmch@googlemail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">The idea was prompted by my correspondence with Terence Noble in Vancouver. <br class="">He's the editor of the modern spellings Wycliffe 2012 Bible.<br class="">These have been published as Kindle e-Books.<br class="">I had been working with his agreement towards making a SWORD module,<br class="">but I got stuck over some technical matters, and the work got shelved due to<br class="">my ill-health.<br class=""><br class="">He included bracketed text and parenthesised text to indicate which parts of<br class="">the Bible were from the earlier edition and which from the later edition.<br class="">I'd need to refresh my brain for the exact details.<br class=""><br class="">As I recall, there are many verses that would read perfectly OK with both<br class="">variants hidden.<br class="">So the idea would be that for general reading without the clutter, you might<br class="">wish to hide both such variants.<br class=""><br class="">Moreover, I don't see this kind of thing as a completely unexpected<br class="">situation.<br class=""><br class="">One can have a Bible translation that includes additional words from more<br class="">than one source, but which doesn't require to replace any existing word or<br class="">words.<br class=""></div></div></blockquote><div><br class=""></div>That was my example of text found in one but not the other. While it is true regarding an isolated verse, it won’t be true for all.</div><div><br class=""></div><div>When marking variants it is important to mark what is being replaced in the base text as the first variant. And the replacement as a second variant. Even when the variant is empty. They need to form parallel arrays.</div><div><br class=""></div><div>E.g.</div><div>Suppose the words A C E G H I J in the original text. And A B D E F G J K L M in the variant text.</div><div>You might have</div><div><span style="font-family: 'Courier New';" class=""><A> <v1: v2:B> <v1:C v2:D> <E> <v1: v2:F> <G> <v1:"H I” v2:> J <v1: v2:”K L M”></span></div><div><span style="font-family: 'Courier New';" class=""><br class=""></span></div><div><span style="font-family: 'Courier New';" class="">Which might be rendered in an interlinear fashion:</span></div><div><span style="font-family: 'Courier New';" class="">A --- *C* +E+ --- G +H I+ J -----</span></div><div><font face="Courier New" class=""> +B+ *D* --- +F+ ----- K L M</font></div><div><br class=""></div><div>Turning off all variants shouldn’t show</div><div><font face="Courier New" class="">A C E G H I J</font></div><div><br class=""></div><div>Lets suppose it is a text that has some alternate spellings. The front end should be able to show the alternate spelling under the word or phrase. In this case it is important to mark what is being replaced as well as the alternate.</div><div><font face="Courier New" class="">A B B' C D E E' FG F’ G'</font></div><div>Where FG is a single compound word and F’ G’ is broken into two words.</div><div><font face="Courier New" class="">A B C D E FG</font></div><div><font face="Courier New" class=""> B' E' F' G’</font></div><div><font face="Courier New" class=""><br class=""></font></div><div>Turning off all variants shouldn’t show:</div><div><font face="Courier New" class="">A B C D E FG</font></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">IMHO, our attachment of functionality based to the meaning of the word<br class="">variant has been overprecise.<br class=""><br class="">Whether or not a front-end should ever display with no variants could be<br class="">something we might specify in the module .conf file.<br class=""><br class="">Basically, any text wrapped inside a seg element for this purpose is<br class="">something that can be optionally shown or hidden according to certain<br class="">criteria. There's no overarching requirement that we should never have all<br class="">such text portions hidden.<br class=""><br class="">Best regards,<br class=""><br class="">David<br class=""><br class=""><br class=""><br class=""><br class=""><br class=""><br class="">--<br class="">View this message in context: <a href="http://sword-dev.350566.n4.nabble.com/OSISVariants-SWORD-tp4656983p4656989.html" class="">http://sword-dev.350566.n4.nabble.com/OSISVariants-SWORD-tp4656983p4656989.html</a><br class="">Sent from the SWORD Dev mailing list archive at <a href="http://Nabble.com" class="">Nabble.com</a>.<br class=""><br class="">_______________________________________________<br class="">sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" class="">sword-devel@crosswire.org</a><br class=""><a href="http://www.crosswire.org/mailman/listinfo/sword-devel" class="">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="">Instructions to unsubscribe/change your settings at above page<br class=""></div></div></blockquote></div><br class=""></div></body></html>