[sword-devel] Personal commentary -- internal scripture xrefs

Ben Morgan benpmorgan at gmail.com
Wed Nov 12 15:55:47 MST 2008

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.

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.

When user editable content appears in BPBible, I suspect use of personal
commentaries may be limited to import.

God Bless,
The grace of the Lord Jesus Christ be with your spirit.
Philippians 4:23 (ESV)

On Thu, Nov 13, 2008 at 3:36 AM, DM Smith <dmsmith555 at yahoo.com> wrote:

> Karl Kleinpaste wrote:
> > "Troy A. Griffitts" <scribe at crosswire.org> writes:
> >
> >> The personal commentary driver is not handled differently than any other
> >> module type.  In personal.conf, if you have SourceType=OSIS then the
> >> engine will recognize <reference> tags.  If SourceType=ThML then
> >> <scripRef>.  Hope this makes sense (and is correct).
> >>
> >
> > [charcoal at www mods.d]$ hostname
> > www.crosswire.org
> > [charcoal at www mods.d]$ ls -la ~0/personal.conf
> > -rw-rw-r-- 1 pubmods pubmods 220 Jun 13 03:45
> /space/home/ftp/pub/sword/raw/mods.d/personal.conf
> > [charcoal at www mods.d]$ grep Source ~0/personal.conf
> > [charcoal at www mods.d]$
> When the SourceType is unspecified, it is Plaintext.
> Both ThML and OSIS filters can handle Plaintext modules, but they differ
> in the handling of whitespace from the Plaintext filters. I don't know
> what would happen if it were changed to SourceType=OSIS, but I'd like to
> see that change. Maybe, the front-ends can give the user a choice of
> whether to have a plain or rich text personal commentary and the
> front-end would record the results in the conf's SourceType field.
> In looking at how BibleTime, GnomeSword and BibleCS create personal
> commentaries, I found that they did not create portable ones. I forget
> the details, as I looked a long time ago.
> I was hoping when writing BibleDesktop's code for the personal
> commentary to code to a portable standard. Maybe we can create one going
> forward?
> In Him,
>     DM
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.crosswire.org/pipermail/sword-devel/attachments/20081113/d4c7d61c/attachment.html 

More information about the sword-devel mailing list