[sword-devel] Observations on the SahidicBible module

[David Haslam]

In my other thread, Troy kindly wrote,

So, as a side note to this thread,

The Sahidic Bible is maintained at coptot.manuscriptroom.com:

http://coptot.manuscriptroom.com/transcribing?docID=1620025&userName=PUBLISHED

and we regularly export from there and import into swordweb, which is used
for their browser plugin (first link on Christian Askeland's wonder resource
list for Coptic):

https://sites.google.com/site/askelandchristian/copticlinks

We don't index the text.  They typically search with regex (and yes, they
know about the {byte_count} anomaly with our regex search).

-Troy

---------------------------------

FYI. I am now in email contact with Dr Askeland, so I hope we can make
progress towards a properly updated module. 

The one in the CrossWire repo was last updated in 2012, and judging by the
anomalies in the conf file was originally put together somewhat of in a
hurry.

Although I have submitted an updated conf file to the modules team,
something more substantial is required.

One thing I didn't change in the .conf file was this line:

SourceType=OSIS

I expressed my doubts in my cover email, but now I have conclusive evidence
that the module was made using *imp2vs*.

There are two verses where the IMP format reference was not processed for
whatever cause.

$$$Jer.44.6
$$$Acts.7.60

That being the case, and there being no XML fragments in the module text,
that line should be

SourceType=PlainText

Providing we can obtain the most recent source text that now contains input
from further contributors, it should be feasible to build a new module.

btw. Our other four Coptic modules have "Cop" as a module name prefix. This
one doesn't.

Would it be sensible to rename the module as [CopSahidicBible] when it's
rebuilt, and include the line

Obsoletes=SahidicBible


Best regards,

David





--
View this message in context: http://sword-dev.350566.n4.nabble.com/Observations-on-the-SahidicBible-module-tp4657132.html
Sent from the SWORD Dev mailing list archive at Nabble.com.