<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 13, 2008, at 7:35 PM, Chris Little wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">arl Kleinpaste wrote:<br><blockquote type="cite">(As it happens, GnomeSword understands<span class="Apple-converted-space"> </span><a href="sword://">sword://</a><span class="Apple-converted-space"> </span>and bible://<br></blockquote><blockquote type="cite">equivalently, but I suspect we should do away with the latter.)<br></blockquote><br>I had thought that BibleCS handled bible:// too, but when I checked<span class="Apple-converted-space"> </span><br>earlier, it didn't.<br><br>I'm open to adding bible://. It's certainly an easy addition. But I<span class="Apple-converted-space"> </span><br>don't know whether we would gain anything from it.<br></span></blockquote><br></div><div>If the protocol is a general lookup mechanism, then bible:// would be misleading.</div><div>e.g. bible://StrongsHebrew/H3068</div><div><br></div><div><br></div><br></body></html>