I don't think that personal commentaries are a good idea. Making the user download a module just so they can edit it seems to me a bad idea - especially as module creation functionality is already there in SWORD. It ties you down to having one module (though I believe gnomesword does allow extras - so this might not apply to it). Further, what if they want to make a dictionary, or generic book (or even a Bible)? All these aren't covered by the personal commentary.<br>
<br>In addition to this, different frontends format them differently. What would be much more sensible, in my opinion, is to allow user editable modules - perhaps there needs to be a config option for whether a module is user editable or not - and make these modules use standards compliant OSIS (or ThML or possibly TEI for dictionaries). That way all frontends should handle them properly.<br>
<br>When user editable content appears in BPBible, I suspect use of personal commentaries may be limited to import.<br><br clear="all">God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>
The grace of the Lord Jesus Christ be with your spirit.<br>Philippians 4:23 (ESV)<br><br><br>
<br><br><div class="gmail_quote">On Thu, Nov 13, 2008 at 3:36 AM, DM Smith <span dir="ltr"><<a href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.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">Karl Kleinpaste wrote:<br>
> "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> writes:<br>
><br>
>> The personal commentary driver is not handled differently than any other<br>
>> module type. In personal.conf, if you have SourceType=OSIS then the<br>
>> engine will recognize <reference> tags. If SourceType=ThML then<br>
>> <scripRef>. Hope this makes sense (and is correct).<br>
>><br>
><br>
> [charcoal@www mods.d]$ hostname<br>
> <a href="http://www.crosswire.org" target="_blank">www.crosswire.org</a><br>
> [charcoal@www mods.d]$ ls -la ~0/personal.conf<br>
> -rw-rw-r-- 1 pubmods pubmods 220 Jun 13 03:45 /space/home/ftp/pub/sword/raw/mods.d/personal.conf<br>
> [charcoal@www mods.d]$ grep Source ~0/personal.conf<br>
> [charcoal@www mods.d]$<br>
<br>
</div>When the SourceType is unspecified, it is Plaintext.<br>
<br>
Both ThML and OSIS filters can handle Plaintext modules, but they differ<br>
in the handling of whitespace from the Plaintext filters. I don't know<br>
what would happen if it were changed to SourceType=OSIS, but I'd like to<br>
see that change. Maybe, the front-ends can give the user a choice of<br>
whether to have a plain or rich text personal commentary and the<br>
front-end would record the results in the conf's SourceType field.<br>
<br>
In looking at how BibleTime, GnomeSword and BibleCS create personal<br>
commentaries, I found that they did not create portable ones. I forget<br>
the details, as I looked a long time ago.<br>
<br>
I was hoping when writing BibleDesktop's code for the personal<br>
commentary to code to a portable standard. Maybe we can create one going<br>
forward?<br>
<br>
In Him,<br>
<font color="#888888"> DM<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
<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>