ow to make it work, but I do think it is
there and functioning.
Peter
Sent from my mobile. Please forgive shortness, typos and weird
autocorrects.
Original Message
Subject: Re: [sword-devel] Versification Mapping
From: Jamie
To: 'SWORD Developers' Collaboration
>
>
>
>
>
> Blessings.
>
>
>
> *From: *Troy A. Griffitts
> *Sent: *10 мая 2020 г. 20:53
> *To: *SWORD Developers' Collaboration Forum
> *Subject: *Re: [sword-devel] Versification Mapping (SWORD + JSword)
>
>
>
> Applied. Thank you Костя!
>
<mailto:scr...@crosswire.org>
> *Sent: *10 мая 2020 г. 20:53
> *To: *SWORD Developers' Collaboration Forum
> <mailto:sword-devel@crosswire.org>
> *Subject: *Re: [sword-devel] Versification Mapping (SWORD + JSword)
>
>
>
> Applied. Thank you Костя!
>
&g
bout text to use for NRSVA (NRSV too) Blessings From: Troy A. GriffittsSent: 6 мая 2020 г. 22:28To: sword-devel@crosswire.org; Костя МаслюкSubject: Re: [sword-devel] Versification Mapping (SWORD + JSword) Dear John, Jamie, and Костя,First, I want to say that DM Smith has also a versification mappi
but I do not sure about text to use
> for NRSVA (NRSV too)
>
>
>
>
>
> Blessings
>
>
>
> *From: *Troy A. Griffitts <mailto:scr...@crosswire.org>
> *Sent: *6 мая 2020 г. 22:28
> *To: *sword-devel@crosswire.org <mailto:sword-devel@crosswire.org&
me the texts best to compare, for base v11n I use KJVA, but I do not sure about text to use for NRSVA (NRSV too) Blessings From: Troy A. GriffittsSent: 6 мая 2020 г. 22:28To: sword-devel@crosswire.org; Костя МаслюкSubject: Re: [sword-devel] Versification Mapping (SWORD + JSword) Dear John, Jamie
On Sat, May 9, 2020 at 9:45 AM Tobias Klein wrote:
> @all: Who would be interested in this in general? We could start with tags
> / topical verse lists.
>
I would.
For my tastes and potential use cases something that split the difference
between a complete live persistence and a static import/e
for a while now included in
the library. I am not sure how to make it work, but I do think it
is there and functioning.
Peter
Sent from my mobile. Please forgive shortness, typos and weird
autocorrects.
Original Message
Subject: Re: [sword-devel] Versification Mapping
From: J
=> Psalms 44:21-Psalms 44:22 (FreGeneve1669)
>>
>> Hope this helps,
>> Troy
>>
>>
>>
>>
>>
>> On 5/6/20 7:07 AM, ref...@gmx.net wrote:
>>> I think transparent mapping has been for a while now included in the
>>> library. I a
been for a while now included in the
>> library. I am not sure how to make it work, but I do think it is there and
>> functioning.
>>
>> Peter
>>
>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>>
>>
>>
Hi Tobias,
Remember that any libraries for STEP Bible would likely be oriented towards
JSword rather than SWORD per se.
David
Sent from ProtonMail Mobile
On Wed, May 6, 2020 at 17:04, Tobias Klein wrote:
> Hi Jamie,
>
> Thanks. I had a look at the data, that’s quite complex! Even a bit
> in
Dear John, Jamie, and Костя,
First, I want to say that DM Smith has also a versification mapping
implementation in JSword, which was, and likely still is a foundational
part of STEP. I don't know if STEP uses JSword's versification mapping
facility or if it implements its own. There were collabo
Well, sure, instead of the module's name, more precisely you'd need to
know the versification reference system name (the KJV module happens to
use KJV versification system, so in this case it is the same), then you
can simply use VerseKey:
VerseKey key;
key.setVersificationSystem("KJV");
key.setTe
If a ThML or OSIS genbook references a specific version (KJV Psalm 23:6),
but the installed versions don't include KJV, and the user wants to see it
in russynodal, would this functionality help? That is, does this table rely
on the installed modules? or is it built in a way that references for some
: Re: [sword-devel] Versification MappingFrom: Tobias Klein To: sword-devel@crosswire.orgCC:
Ok, thanks.
I think before other options I'll look into the built-in SWORD
versification functions. But anyway, thanks for sharing this
resource!
T
.info]
*Sent:* 06 May 2020 17:05
*To:* SWORD Developers' Collaboration Forum
*Subject:* Re: [sword-devel] Versification Mapping
Hi Jamie,
Thanks. I had a look at the data, that’s quite complex! Even a bit
intimidating ...
I suppose STEPBible has some library functions that parse this data?
Can
Greetings,
I have done quite a bit of content development for Logos, including Bibles that had versifications that did not fit any existing
schemes in Logos.
Logos uses "verse maps", which are xml files that specify the mapping of every verse in a particular versification to every verse in
ng.
>
> Peter
>
> Sent from my mobile. Please forgive shortness, typos and weird
> autocorrects.
>
>
> Original Message
> Subject: Re: [sword-devel] Versification Mapping
> From: Jamie
> To: 'SWORD Developers' Collaboration Forum'
be happy
to try to explain it – let me know.
Jamie
From: Tobias Klein [mailto:cont...@tklein.info]
Sent: 06 May 2020 17:05
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Versification Mapping
Hi Jamie,
Thanks. I had a look at the data, that’s quite co
Hi Jamie,
Thanks. I had a look at the data, that’s quite complex! Even a bit intimidating
...
I suppose STEPBible has some library functions that parse this data?
Can you point me to any APIs?
Best regards,
Tobias
> Am 06.05.2020 um 15:04 schrieb Jamie :
>
> Hi Tobias,
>
> Not sure that th
I think transparent mapping has been for a while now included in the library. I am not sure how to make it work, but I do think it is there and functioning. PeterSent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: Re: [sword-devel
Hi Tobias,
Not sure that this exactly answers your question, but just in case it’s
relevant, Tyndale House have various public domain information available,
including material on alternative versification schemes. The reversification
material gives details of how to map LXX, MT and Vulgate
There’s also the need for v11n mapping to the KJV.
In Him,
DM
> On Sep 29, 2018, at 1:09 PM, Andrew T. wrote:
>
> Is this just a matter of creating the canon_xxx.h files or is there more to
> it? I've been playing around with alternate versifications (creating
> canon_xxx.h files and
Is this just a matter of creating the canon_xxx.h files or is there more to
it? I've been playing around with alternate versifications (creating
canon_xxx.h files and them modifying versificationmgr.cpp to support). But
I'm not a professional programmer even if I dabble ..
On Wed, Apr 4, 2018 at
Resubmitted during the last hour with minor update to wycliffe.conf
Though earlier I'd forgotten to include this line
GlobalOptionFilter=OSISHeadings
it has no real bearing on the other problem I just reported in a new thread.
Best regards,
David
--
View this message in context:
http://swo
Module submitted to the "modules team" along with validated OSIS XML file and
covering email.
Best regards,
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Versification-for-the-Complete-Wycliffe-Bible-tp4657012p4657030.html
Sent from the SWORD Dev mailing list ar
Now fixed the matter of the *Prayer of Manasseh* that had been
inappropriately assigned in Wikisource as 2 Chronicles 37.
The fix was done after the work was converted to OSIS XML, just as I did
earlier for the *Letter of Jeremiah*.
btw. The side-effect of the misplaced title for Ezra has gone,
After fixing several further versification issues on Wikisource (mainly
misplaced chapter headings),
I've reached the stage where osis2mod gives only SEVEN appending advisories.
* Deut.27.27
* 2Chr.37.1 (/Prayer of Manasseh/)
* The title in Ezra (this is merely an unexpected consequence of the
ex
I have reached the stage where I can compare the new Wycliffe module *v2.0*
with the old Wycliffe module *v1.0* which was for the *Pentateuch and
Gospels* only.
This has brought to light the fact that v1.0 contains 299 in-line notes in
the form: *[Note: . ]*.
These are *not* included in the W
The long prayer is actually known as "[This preyere of Manasses is not in
Ebrue]"
See *page 475* in
http://quod.lib.umich.edu/c/cme/AFZ9170.0001.001/1:18.37?rgn=div2;view=fulltext
It's part of the prologue to the book of Ezra (I Esdras) in Wycliffe's
Bible.
It's not adequately marked up on
Just corrected the versification on Wikisource for
https://en.wikisource.org/wiki/Bible_(Wycliffe)/3_Esdras
See https://en.wikisource.org/wiki/Talk:Bible_(Wycliffe)/3_Esdras
"This is the 9 chapter book of Greek Ezra in the LXX, called 2 Esdras in
Russian Bibles, and called 3 Esdras in the Vulgate
The prayer mentioned in my earlier reply is counted as *2 Chronicles
36:24-27* in this site:
http://www.bible.pearmobile.com/chapters.php?id=10403&pid=16&tid=1&bid=76
Viz. (below my sign off)
That site omits the Deuterocanonical books, though.
David
---
24 Lord God Almyyti of our fadris,
Progressing with the module build.
After I generated the OSIS file, I manually replaced *EpJer.1* with *Bar.6*
and joined the two books together by removing the and in between *Bar.5* and *Bar.6*
Now I've come across something new that I'd not read of before.
A long single verse prayer as *2Ch
This is why I encountered such a problem.
The av11n for *Vulg* uses the /standard/ *osisID* names for *Esther* and
*Daniel* rather than the more specific names for *Greek Esther* and *Greek
Daniel*.
The Python script *wycliffe.py* uses the latter, along with the
corresponding USFM names.
Strictly
Afterthought:
I will upload my copy of *wycliffe.py* to GitHub at some stage, so that
anyone can clone it and adapt it for other Bibles on Wikisource.
It captures the text from the *Special* download pages and converts each of
them to USFM.
Acknowledgements to Chris Little (more than three years
On 2015-08-24, 20:16 GMT, Greg Hellings wrote:
> Outside of that, I can't see what you've changed in the script because
> you managed to change just about every single line in your zeal to
> achieve PEP-8 compliance so I can't begin to comment on whether the
> problems are with my original logic or
So what that's telling you is that your module has a strict subset of
all of those versioning schemes. "Your file has no extra references"
means that there are no attributes named "osisID" that exist in your
module that do not exist in the specified versification system. That
it reports such for AL
On 2015-08-24, 18:21 GMT, Greg Hellings wrote:
> Specifically:
> http://crosswire.org/svn/sword-tools/trunk/versification/av11n.py
I have found it and start to work on it (it didn’t work out of
the box). My current branch (with PEP8ification, and changes
I found needed) is at the git repo
http
Specifically: http://crosswire.org/svn/sword-tools/trunk/versification/av11n.py
--Greg
On Mon, Aug 24, 2015 at 9:05 AM, Peter von Kaehne wrote:
> Sword-tools repo
>
> Sent from my phone. Apologies for brevity and typos.On 24 Aug 2015 1:52 pm,
> Matěj Cepl wrote:
>>
>> On 2015-08-23, 21:04 GMT,
Sword-tools repo
Sent from my phone. Apologies for brevity and typos.On 24 Aug 2015 1:52 pm,
Matěj Cepl wrote:
>
> On 2015-08-23, 21:04 GMT, Greg Hellings wrote:
> > I had submitted a Python script somewhere that simply walks through every
>
> Could you elaborate a little bit on that “somewhere”
On 2015-08-23, 21:04 GMT, Greg Hellings wrote:
> I had submitted a Python script somewhere that simply walks through every
Could you elaborate a little bit on that “somewhere” part,
please?
:)
Matěj
--
http://www.ceplovi.cz/matej/, Jabber: mc...@ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB
I had submitted a Python script somewhere that simply walks through every
versification in the Sword library and reports the number of extra/missing
verses in a given OSIS file relative to each versification with a
per-Testament breakdown. For instance it might give output similar to the
following:
Title: signature
On 08/23/2015 08:27 AM, Matěj Cepl
wrote:
On 2015-08-23, 09:29 GMT, Peter von Kaehne wrote:
Interesting and quite probably useful would be to know if any
'colonial' translations would benefit from any of these three
v11ns. I do thi
On 04/30/2012 06:47 AM, Chris Little wrote:
> Sounds French. We don't really have enough information to produce this v11n
> system yet.
The most important piece of information to know is that unless you build some
flexibility into the system and refrain from ever hard coding the number of
verse
On Mon, Apr 30, 2012 at 12:40 PM, Brian J Dumont
wrote:
> On 04/30/2012 12:37 PM, Greg Hellings wrote:
>>
>> On Mon, Apr 30, 2012 at 11:10 AM, David Haslam
>> wrote:
>>>
>>> Didn't Greg Hellings write a Perl script to check which of our defined
>>> v11ns
>>> would be the most suitable for a new m
On 04/30/2012 12:47 PM, Chris Little wrote:
On 04/30/2012 07:44 AM, Brian J Dumont wrote:
Hi all,
I'm working with a Bible translator who has recently completed a Bible
translation into the Tandroy language. I'm almost done converting his
basic source into osis, and will soon be working on gett
On 04/30/2012 12:37 PM, Greg Hellings wrote:
On Mon, Apr 30, 2012 at 11:10 AM, David Haslam wrote:
Didn't Greg Hellings write a Perl script to check which of our defined v11ns
would be the most suitable for a new module?
Python. How dare you suggest I would sully myself with Perl?! :P
http://
On 04/30/2012 07:44 AM, Brian J Dumont wrote:
Hi all,
I'm working with a Bible translator who has recently completed a Bible
translation into the Tandroy language. I'm almost done converting his
basic source into osis, and will soon be working on getting it into SWORD.
The versification looks s
On Mon, Apr 30, 2012 at 11:10 AM, David Haslam wrote:
> Didn't Greg Hellings write a Perl script to check which of our defined v11ns
> would be the most suitable for a new module?
Python. How dare you suggest I would sully myself with Perl?! :P
http://www.crosswire.org/svn/sword-tools/trunk/vers
On 04/30/2012 12:10 PM, David Haslam wrote:
PS. Isn't the OT of the KJV based on the MT? If so, what's the real problem?
I had thought so as well; but compare KJV to JPS. There are a number of
OT chapters where the JPS has many more verses (for example, Lev 5, Num 17)
--
---
Didn't Greg Hellings write a Perl script to check which of our defined v11ns
would be the most suitable for a new module?
David
PS. Isn't the OT of the KJV based on the MT? If so, what's the real problem?
PS2. During module build, please be careful. Unless the Zcomp problem has
been solved alrea
Best to check which would be missing least. And then cram a few verses
together, unless we can expect a whole lot of other texts in a similar
versification.
Peter
Original-Nachricht
> Datum: Mon, 30 Apr 2012 10:44:13 -0400
> Von: Brian J Dumont
> An: SWORD Developers\' Collabo
Dne 14.7.2011 16:50, Greg Hellings napsal(a):
They live within the SWORD source. If you have the swig executable
you can enable bindings. I prefer to do it with CMake like follows:
You seem to be using Fedora as well. Do you think it would be possible
to add Python bindings to the sword Rawhi
They live within the SWORD source. If you have the swig executable
you can enable bindings. I prefer to do it with CMake like follows:
mkdir build && cd build
cmake -DSWORD_BINDINGS=Python ..
make -j5 && sudo make install
pushd bindings/swig/python
python setup.py build
sudo python setup.py inst
Dne 14.7.2011 02:11, Greg Hellings napsal(a):
I accept your challenge. For those of you with the ability to build
and install the Python bindings, you will find an (our first, in fact)
example Python script named av11n.py. It does as you suggest for an
Stupid question ... where does these bind
Like (as in facebook).
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Versification-comparison-script-was-Re-osis2mod-unhappy-with-New-Testament-osisIDs-tp3666383p3666735.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
The Jerusalem Bible should be fairly straightforward, from your
description. We just need to pick a versification and use it,
preferrably the one that looks like their favored versification. All
v11ns should be encoded in the OSIS doc, but the JB v11n should precede
others. If "2:7, 1:3" indica
On 11/09/10 20:15, Greg Hellings wrote:
> No one has given me a solid answer as to how that would be encoded.
That sounds not very encouraging.
Peter
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/swor
Peter,
I have brought this up before, relating it to the Jerusalem Bible,
which does something similar. Instead of using A, B, C, etc, they
simply will number a verse as "2:7, 1:3" to reflect both popular types
of versification or they will go "1:1, 1:2, 1:2a, 1:2b, 1:2c, 1:3,
1:4" to indicate ad
On Sun, Nov 8, 2009 at 13:50, Chris Burrell wrote:
>Does anyone have any views as to the best way of storing the verse/passage
>reference?
Test out each approach using different versions/editions of
GreekEsther. It probably will provide you with every "worst case
scenario" you can imagine, an
As for spelling, and as a fascinating learning experience, pick up your
printed KJV Bible and examine the spelling of the word "ankle[s]" in Ezekiel
47:3 and Acts 3:7.
Some editions have "ancle", others have "ankle".
Ostensibly both streams are based on the Authorised Version of 1769. So
Peter'
Mike Hart wrote:
> I'm working on several bibles to get them into Sword Format
> (ultimately into public domain, or as close to PD as possible), and
> I've got a few unresolved issues.
>
> Can someone point me to the how-to that covers these topics?
Please have a look at our wiki, which now is f
Mike Hart wrote:
I'm working on several bibles to get them into Sword Format (ultimately into
public domain, or as close to PD as possible), and I've got a few unresolved
issues.
Can someone point me to the how-to that covers these topics?
Issue number 1 - Versification standards
One Bi
Troy.
Attached is a diff for versemgr.
I'm getting some compile errors. TreeKey seems to be abstract.
Can you tell me which implementation it can be casted to or used
instead?
Also I didn't know how to extract osis ref and book apprev from treekey.
Hope you can help.
Manfred
versemgr.di
Sounds good.
No comments at this time.
I hope to get this registration going soon.
Scanning the whole genbook takes some time so I was thinking if we
could we make the versification registration "on the fly" in that on
the beginning only books are known. When someone wants chapters for a
boo
Once the code is done to register a versification system with a TreeKey,
I was thinking of having SWMgr, when it loads a GenBook with
KeyType=VerseKey register it with VerseMgr as a versification scheme
called the same as the module name. This will get things working for
individual modules.
Troy.
Alright, understood.
Another question:
The only call to registerVersificationSystem() is done now in the
SystemVerseMgr getter.
But here only for 'normal' versification system.
In which way do we need to differentiate between the old and the new
and call the TreeKey registerVersification
Dear Manfred,
Yes, you are exactly correct. First level would get all books, second
level would get all chapters, and third level would get all verses.
These are the things that are pulled from the static array in canon.h
-Troy.
Manfred Bergmann wrote:
> Am 29.10.2008 um 14:23 schrie
Am 29.10.2008 um 14:23 schrieb Troy A. Griffitts:
> If you'd like to help with the unfinished part, have a look at:
>
> http://crosswire.org/svn/sword/trunk/src/mgr/versemgr.cpp
>
> and search for: TreeKey
>
> See the overloaded registerVersificationSystem implementation above
> which implements
Thank you for your answer.
I took the verse parsing and list code from verserangeparse.cpp which
is in MacSword then:
sword::VerseKeyvk;
sword::ListKey listkey = vk.ParseVerseList(cref, vk, true);
listkey.Persist(true);
swModule->setKey(listkey);
// iterate through
Well, it might be, but parts are also not yet done.
If you use a standard VerseKey instance to iterate a chapter, then the
problem could be on your end, eg.
VerseKey vk;
vk.Persist(true);
module.setKey(vk);
for (int i = 0; i < 13 && !vk.Error(); i++) {
output += module.RenderText();
Huray.
First genbook with alternate versification.
It turned out that the xml2gbs converter doesn't like single quotes
for strings (attributes).
A problem though. Gen 32:33 should show something in the gerneuegb
module but it doesn't.
http://idisk.mac.com/manfred.bergmann-Public/shot_sword_gb.
Chris, do you know where I can get the OSIS source of which the KJVgb
and/or GerLut1545lhgb have been created from?
Text can be rendered for these two modules but not for my created one.
I guess there are some differences in the OSIS which I need to check.
Manfred
Am 28.10.2008 um 08:52 schri
Hi Chris.
Am 28.10.2008 um 08:52 schrieb Chris Little:
> I would first check the source file to make sure that the character
> following 32:33 is a space (plain 0x20 space). Other characters can at
> times confuse the import tools. Aside from that, I can't imagine why
> osis2mod is reversifying 3
Manfred,
I would first check the source file to make sure that the character
following 32:33 is a space (plain 0x20 space). Other characters can at
times confuse the import tools. Aside from that, I can't imagine why
osis2mod is reversifying 32:33 as 32:0, since it should really go to
32:32. A
Hi.
It's me again. :)
I've tried the svn HEAD for creating this german bible module GerNeUe
from OSIS.
The verses mentioned below are not shifted anymore.
But i.e. verse 32:33 which is in the source is re-versified as 32:0:
"re-versified Genesis 32:33 as Genesis 32:0"
What dies this mean.
Thanks Jens.
Well, I guess I'll wait with creating this module until the alternate
versification schema osis2mod is finished.
Manfred
Am 06.10.2008 um 15:42 schrieb Jens_G:
>
> Here is the Answere.
>
> My List of difference between german and english Versnumbering.
>
> http://www.grabner-on
Here is the Answere.
My List of difference between german and english Versnumbering.
http://www.grabner-online.de/download/deutsch_englisch.zip
Jens Grabner
Manfred Bergmann wrote:
>
> Hi.
>
> I know there has a lot of discussion about versification schemes.
> Now that I'm working on a Sw
Am 02.10.2008 um 08:18 schrieb Greg Hellings:
> For now, converting into a General Book is likely to be your best
> bet, and the eventual osis2mod will be able to create modules which
> are recognized as Bibles to the frontends, but which use the General
> Book driver. For now, I don't thi
Can you just use the data already there in apocrypha.h? That uses the NRSVA
mostly.
God Bless,
Ben
---
The Lord is not slow to fulfill his promise as some count slowness,
but is patient toward you, not wishing
lt;[EMAIL PROTECTED]>
> An: SWORD Developers\' Collaboration Forum
> Betreff: Re: [sword-devel] versification and fooling osis2mod
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/lis
Dear Daniel,
Troy has reworked the whole versification business in libsword. There are now
two different ways for divergent canons and versifications:
1) it is possible to have several statically defined canons and versifications
2) via GenBook it is possible to introduce new dynamically define
Greg,
Thanks for that explanation. I did notice the Psalm 9-10 issue in this
module as well. I will try out creating a genbook and see how that
goes. I can see how the technical side of things would be very
complicated. I was going to try to create a Bible module without the
deuterocanonical b
Daniel
On Thu, Oct 2, 2008 at 12:54 AM, Daniel Owens <[EMAIL PROTECTED]> wrote:
> I am working on a module for a Catholic translation that has
> deuterocanonical books as well as additional verses in Daniel 3 (vv.
> 24-90--in the LXX, though Crosswire LXX modules drop the extra text). If
> anyon
Hey all,
My apologies for being out of the loop for a week or so. Hope to
recover soon from the past weekend and get back into things. It was
great seeing Daniel again and meeting Karl in person for the first time.
Thanks, Karl, for the debrief to sword-devel.
Just a quick note on this reo
Martin Gruner wrote:
>> No timeline. As far as I know, no one has stepped up and volunteered to
>> make the remaining changes.
>>
>> Perhaps when Troy comes back from BibleTech he can outline an
>> engineering task list.
>>
>
> That would be cool. Maybe I can take an isolated task.
>
> Wiki is
Correct me if I'm wrong, but wasn't the idea to create a virtual class
based off of Versekey that would look like a verse key to the various
front ends (aside from Bible Desktop and the Firefox extension that's
being developed right now) so nobody had to change their code?
Also, with regard to
I found it! A little while back, somebody posted this reference.
_http://www.ccel.org/refsys/refsys.html_
(http://www.ccel.org/refsys/refsys.html)
Harry Plantinga has made a great start on various v11n schemes.
Peace,
David
**Start the year off right. Easy ways to stay
On Jan 28, 2008, at 9:48 AM, Martin Gruner wrote:
>>> For bibles? Does that mean they will be stored as Genbooks in
>>> future, at
>>> least if a non-KJV versification scheme is used?
>>
>> That is what I understand.
>
> I am not sure I like this. Isn't VerseKey etc. prepared to work with
> d
On Jan 28, 2008, at 8:56 AM, DM Smith wrote:
> Chris mentioned that the tool to create one exist already: osis2gbs.
> Perhaps they can be created and put into beta. I would think that
> having
> one or more in beta would spur development.
I posted an example to beta: DRCgb. I was a little off o
> > For bibles? Does that mean they will be stored as Genbooks in future, at
> > least if a non-KJV versification scheme is used?
>
> That is what I understand.
I am not sure I like this. Isn't VerseKey etc. prepared to work with dynamic
versification, only canon.h fixed the index values to save
-
From: DJ Ortley [mailto:[EMAIL PROTECTED]
Sent: Monday, January 28, 2008 11:37 AM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Versification
At this point I'd like to step up and point out that I've off and on
talked about being interested in adding
At this point I'd like to step up and point out that I've off and on
talked about being interested in adding support to the
detuerocanon/apocrypha, which in my mind would then springboard to
handling dynamic versification. I've not personally done anything as
I'm as busy as anybody else, on to
Frontend developers and end users are of course interested in having
good support for navigating in a Bible so that giving a reference as
input would give the expected output. It may be impossible to map
references inside works so that the result would always be correct but I
think that it might be
Martin Gruner wrote:
> Hi DM,
>
>
>> As Chris mentioned, canon.h will not be changed. The idea is to create
>> a GenBook with a standard way of naming the keys, in the form
>> OSISBookAbbr/ChapterNum/VerseNum. Replacing the / with . would result
>> in an OSIS id.
>>
>
> For bibles? Does tha
Hi DM,
> As Chris mentioned, canon.h will not be changed. The idea is to create
> a GenBook with a standard way of naming the keys, in the form
> OSISBookAbbr/ChapterNum/VerseNum. Replacing the / with . would result
> in an OSIS id.
For bibles? Does that mean they will be stored as Genbooks in fu
>
> BTW how many variants are there?
>
> There is obviously teh RC and Greek Orthodox way of including the
> apogrypohae into their canon with a whole range of resulting chnages.
> But any other important schemes?
>
>
There are some very heavily-used Bibles that have *extremely* different
numbe
On Jan 28, 2008, at 6:36 AM, peter wrote:
> Barry Drake wrote:
>> Hi Peter ...
>>
>> peter wrote:
>>> So could I - once that number mystery is understood - create a
>>> different
>>> canon.h file for e.g RC versification and recompile Sword ?
>>
>> I'm sure you could - but you'd break i
Chris Little wrote:
> Significantly, using TreeKeys means you don't have to know about
> versification schemes or pick one (unless you need to do mapping).
>
> New modules that use new versification schemes don't require more coding
> in the API, they're inherent to the module itself.
ok, th
peter wrote:
> Being no coder, I can not see how completely new way of encoding Bibles
> should be the right way forward - particularly as it would result in
>
> a) a possibly long period of breakage/poor implementation on various
> GUIs (+ some GUIs which are perfectly fine now will never get i
1 - 100 of 116 matches
Mail list logo
