Re: [sword-devel] Observations on the SahidicBible module

2017-05-01 Thread David Haslam
Troy wrote, "... each biblical book is in a different state of completeness and quality". One evidence of this is that these three books have text but it's completely without *w* elements yet. I Samuel II Samuel Isaiah Best regards, David -- View this message in context: http://sword-dev.35

Re: [sword-devel] Observations on the SahidicBible module

2017-05-01 Thread David Haslam
Hi Troy, I can certainly see that OSIS will be needed to make some parts of the source text more usable. There are 201 *w* elements similar to this example: ⲉⲧⲃⲉ I'm thinking that these should be converted to use the OSIS *transChange* element. ⲉⲧⲃⲉ The *reason* attribute could be discarded i

Re: [sword-devel] Observations on the SahidicBible module

2017-05-01 Thread David Haslam
Thanks Troy, I only got drawn into this through my curiosity when I came across a later post of yours in this mailing list in which you were asking about viewing the SahidicBible module in PocketSword. :) Is it likely then that the "2012-10-10" module version 1.1 in our repository is merely a sna

Re: [sword-devel] Observations on the SahidicBible module

2017-05-01 Thread Troy A. Griffitts
The text is in constant development and each biblical book is in a different state of completeness and quality. An export of the work in its most current state can always be obtained with: http://coptot.manuscriptroom.com/community/vmr/api/transcript/export/?docID=1620025&biblicalContent=Gen-Rev

[sword-devel] Observations on the SahidicBible module

2017-05-01 Thread 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 t