Here is how I would do it/it should be done:<br><br>For internal links in OSIS:<br>In:<br><reference osisRef="module:encoded_key">Text</reference><br>Out (For osishtmlhref):<br><a href="passagestudy.jsp?action=moduleRef&value=encoded_key&module=module">Text</a><br>
<br>Vary the passagestudy string according to taste - especially moduleRef<br>If module == "self", use the current module.<br><br>If a link starts with Bible: or has no : in it, the existing reference code should be used.<br>
<br>I see no reason to give an option for sword:// style of URLs - if anyone wants them, they should write their own filters - there is no easy way to allow user customization of them. The way above is consistent with the similar functionality in the filters.<br>
<br clear="all">God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>Multitudes, multitudes,<br> in the valley of decision!<br>For the day of the LORD is near<br>
in the valley of decision.<br><br>Giôên 3:14 (ESV)<br><br>
<br><br><div class="gmail_quote">On Thu, Nov 27, 2008 at 3:16 AM, Matthew Talbert <span dir="ltr"><<a href="mailto:ransom1982@gmail.com">ransom1982@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Nov 26, 2008 at 5:11 AM, Eeli Kaikkonen<br>
<<a href="mailto:eekaikko@mail.student.oulu.fi">eekaikko@mail.student.oulu.fi</a>> wrote:<br>
> Quoting Greg Hellings <<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a>>:<br>
><br>
><br>
>><br>
>> Likewise. People (I think Chris is one of the leading people, but I<br>
>> might be mistaken on that) ought to stop advocating usage of OSIS<br>
>> references for the time being. They accomplish nothing, since they<br>
>> produce nonsense out the other end, being that they're not supported.<br>
>> Why BibleDesktop or BibleTime or BPBible don't support sword:// is<br>
>> probably because they're all working on other issues right now. DM<br>
>> already mentioned some things BibleDesktop is trying to figure out<br>
>> first, the BibleTime guys are actively working on achieving<br>
>> independence of the KDE libraries, Ben just explained why he can't get<br>
>> support into the current version of BPBible.<br>
><br>
> Actually BibleTime uses sword:// internally but the rest of the link<br>
> specification may be a bit different from other implementations. I<br>
> have thought about changing it if necessary. This whole issue is<br>
> important enough to be resolved as soon as possible. Linking inside<br>
> and between modules should be self-evident feature in Bible software.<br>
<br>
</div>Greg Helling is working on the filters. His proposal is to use<br>
sword://module/OSISref links for internal links because that appears<br>
to be the easiest way to implement. There would be an option when you<br>
create the renderer to get links in either passagestudy.jsp style or<br>
sword:// style. So a reference would like like sword://ESV/Gen.1.1 for<br>
instance.<br>
<br>
Comments?<br>
<div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br>