Re: [sword-devel] French versification schemes

[Konstantin Maslyuk]

Yes i called it meta v11n in past.  I think it is  possible,  but with OSIS i simply do not know where exactly we have to map. 



Отправлено с Mi PhoneMartin Denham  | От: 19 июня 2017 г. 12:59 AM | Сообщение:Should we consider introducing a new, fabricated translation (IIRC this may have originally been your idea DM), containing all potential books and used for mapping between different v11n?  I was recently struggling to sort bookmarks from multiple different v11n and wrote the following at the time:1. JSword's VersificationsMapper uses KJV as the intermediate mapping so Vulgate->KJVA will not work for dc books.What about using a fabricated-v11n which contains all possible books, chapters and verses as the intermediate v11n.  Maybe this would be based on something like KJVAMartinOn 18 June 2017 at 22:40, DM Smith  wrote:Good idea. I’ll look into how we can markup an OSIS text with a mapping to the KJV. If we can do that, then the form that SWORD/JSword needs is merely a form that the two can agree upon.DM SmithOn Jun 18, 2017, at 3:45 PM, Костя Маслюк  wrote:Having one file for canon defnition and mappings is preffered in my point. Having source(reference) text in that file as well is best.So would OSIS gurus say whether it is possible to store all data required to build canon and mappings in valid OSIS document?As i realize convenience of readable formats my point is still the same. So i count on some sort of authoritative desision. 10 июня 2017 г. 5:31 PM пользователь "DM Smith"  написал:Circling back around to this.There are two parts to the problem:1) AV11N2) Mapping to KJVAV11N:In JSword, we don’t yet have a form for external AV11N. There are two parts to this: Books and Verse/Chapter counts. Books have presence and ordering. Chapters have verse counts, answering "What is the highest verse number in the chapter?” JSword and SWORD differ a bit on internal representation of chapter counts, but the biggest difference is that we have one representation for the OT and one for the NT, allowing reuse of a testament’s chapter counts. The other is a slight difference where we don’t have a separate array of the counts of chapters.In canon.h there is:struct sbook ntbooks[] = {  {"Matthew", "Matt", "Matt", 28},JSword doesn’t have the chapter count, 28, present in its book order array.The canon.h vm[] array is:int vm[] = {  // Genesis  31, 25, 24, 26, 32, 22, 24, 22, 29, 32,  32, 20, 18, 24, 21, 16, 27, 33, 38, 18,  34, 24, 20, 67, 34, 35, 46, 22, 35, 43,  55, 32, 20, 31, 29, 43, 36, 30, 23, 23,  57, 38, 34, 34, 28, 34, 31, 22, 33, 26,  // Exodus  22, 25, 22, 31, 23, 30, 25, 32, 35, 29,  10, 51, 22, 31, 27, 36, 16, 27, 25, 26,  36, 31, 33, 18, 40, 37, 21, 43, 46, 38,  18, 35, 23, 35, 35, 38, 29, 31, 43, 38,The difference for JSword is that we use a doubly nested array:    /* protected */ static final int[][] LAST_VERSE_OT =    {        // Genesis        {           31,  25,  24,  26,  32,  22,  24,  22,  29,  32,           32,  20,  18,  24,  21,  16,  27,  33,  38,  18,           34,  24,  20,  67,  34,  35,  46,  22,  35,  43,           55,  32,  20,  31,  29,  43,  36,  30,  23,  23,           57,  38,  34,  34,  28,  34,  31,  22,  33,  26,        },        // Exodus        {           22,  25,  22,  31,  23,  30,  25,  32,  35,  29,           10,  51,  22,  31,  27,  36,  16,  27,  25,  26,           36,  31,  33,  18,  40,  37,  21,  43,  46,  38,           18,  35,  23,  35,  35,  38,  29,  31,  43,  38,        },We’ve maintained the comments as the same and the number of elements on a line the same, allowing us to diff the corresponding canon.h for verification.The practical difference is that we use sizeof to get the chapter count rather than a lookup in a 2D book array.Looking at Костя’s file his representation, while easy to generate from a module’s original OSIS xml is too verbose. It has one XML element per verse. We only need chapters/book and verses/chapter. The above representations are sufficiently compact. The python script that is used to generate the canon file can be adapted to create any format we choose.The format we choose should be:easy to readeasy to parse and convert into the internal format neededcompactThe book names being standardized to OSIS is sufficient.The array of chapters having 10 per line make it easy for people to read.I’ve also spaced it so commas line up even for chapters with over 99 verses.I’d suggest JSON over XML as it can represent arrays in a more compact form.E.g. (off the top of my head, can be otherwise)KJV = [[  [ "Gen",     [      31,  25,  24,  26,  32,  22,  24,  22,  29,  32,      32,  20,  18,  24,  21,  16,  27,  33,  38,  18,      34,  24,  20,  67,  34,  35,  46,  22,  35,  43,      55,  32,  20,  31,  29,  43,  36,  30,  23,  23,      57,  38,  34,  34,  28,  34,  31,  22,  33,  26    ]  ],  [ "Exod",    [      22,  25,  22,  31,  23,  30,  25,  32,  35,  29,    

Re: [sword-devel] French versification schemes

[Martin Denham]

Should we consider introducing a new, fabricated translation (IIRC this may
have originally been your idea DM), containing all potential books and used
for mapping between different v11n?  I was recently struggling to sort
bookmarks from multiple different v11n and wrote the following at the time:

1. JSword's VersificationsMapper uses KJV as the intermediate mapping so
Vulgate->KJVA will not work for dc books.
What about using a fabricated-v11n which contains all possible books,
chapters and verses as the intermediate v11n.  Maybe this would be based on
something like KJVA

Martin

On 18 June 2017 at 22:40, DM Smith  wrote:

> Good idea. I’ll look into how we can markup an OSIS text with a mapping to
> the KJV. If we can do that, then the form that SWORD/JSword needs is merely
> a form that the two can agree upon.
>
> DM Smith
>
> On Jun 18, 2017, at 3:45 PM, Костя Маслюк  wrote:
>
> Having one file for canon defnition and mappings is preffered in my point.
> Having source(reference) text in that file as well is best.
>
> So would OSIS gurus say whether it is possible to store all data required
> to build canon and mappings in valid OSIS document?
>
> As i realize convenience of readable formats my point is still the same.
> So i count on some sort of authoritative desision.
>
>
> 10 июня 2017 г. 5:31 PM пользователь "DM Smith" 
> написал:
>
> Circling back around to this.
> There are two parts to the problem:
> 1) AV11N
> 2) Mapping to KJV
>
> AV11N:
> In JSword, we don’t yet have a form for external AV11N. There are two
> parts to this: Books and Verse/Chapter counts. Books have presence and
> ordering. Chapters have verse counts, answering "What is the highest verse
> number in the chapter?” JSword and SWORD differ a bit on internal
> representation of chapter counts, but the biggest difference is that we
> have one representation for the OT and one for the NT, allowing reuse of a
> testament’s chapter counts. The other is a slight difference where we don’t
> have a separate array of the counts of chapters.
>
> In canon.h there is:
> struct sbook ntbooks[] = {
>   {"Matthew", "Matt", "Matt", 28},
> JSword doesn’t have the chapter count, 28, present in its book order array.
>
> The canon.h vm[] array is:
> int vm[] = {
>   // Genesis
>   31, 25, 24, 26, 32, 22, 24, 22, 29, 32,
>   32, 20, 18, 24, 21, 16, 27, 33, 38, 18,
>   34, 24, 20, 67, 34, 35, 46, 22, 35, 43,
>   55, 32, 20, 31, 29, 43, 36, 30, 23, 23,
>   57, 38, 34, 34, 28, 34, 31, 22, 33, 26,
>   // Exodus
>   22, 25, 22, 31, 23, 30, 25, 32, 35, 29,
>   10, 51, 22, 31, 27, 36, 16, 27, 25, 26,
>   36, 31, 33, 18, 40, 37, 21, 43, 46, 38,
>   18, 35, 23, 35, 35, 38, 29, 31, 43, 38,
> The difference for JSword is that we use a doubly nested array:
> /* protected */ static final int[][] LAST_VERSE_OT =
> {
> // Genesis
> {
>31,  25,  24,  26,  32,  22,  24,  22,  29,  32,
>32,  20,  18,  24,  21,  16,  27,  33,  38,  18,
>34,  24,  20,  67,  34,  35,  46,  22,  35,  43,
>55,  32,  20,  31,  29,  43,  36,  30,  23,  23,
>57,  38,  34,  34,  28,  34,  31,  22,  33,  26,
> },
> // Exodus
> {
>22,  25,  22,  31,  23,  30,  25,  32,  35,  29,
>10,  51,  22,  31,  27,  36,  16,  27,  25,  26,
>36,  31,  33,  18,  40,  37,  21,  43,  46,  38,
>18,  35,  23,  35,  35,  38,  29,  31,  43,  38,
> },
>
> We’ve maintained the comments as the same and the number of elements on a
> line the same, allowing us to diff the corresponding canon.h for
> verification.
>
> The practical difference is that we use sizeof to get the chapter count
> rather than a lookup in a 2D book array.
>
> Looking at Костя’s file his representation, while easy to generate from a
> module’s original OSIS xml is too verbose. It has one XML element per
> verse. We only need chapters/book and verses/chapter. The above
> representations are sufficiently compact. The python script that is used to
> generate the canon file can be adapted to create any format we choose.
>
> The format we choose should be:
> easy to read
> easy to parse and convert into the internal format needed
> compact
>
> The book names being standardized to OSIS is sufficient.
> The array of chapters having 10 per line make it easy for people to read.
> I’ve also spaced it so commas line up even for chapters with over 99
> verses.
>
> I’d suggest JSON over XML as it can represent arrays in a more compact
> form.
>
> E.g. (off the top of my head, can be otherwise)
> KJV = [
> [
>   [ "Gen",
> [
>   31,  25,  24,  26,  32,  22,  24,  22,  29,  32,
>   32,  20,  18,  24,  21,  16,  27,  33,  38,  18,
>   34,  24,  20,  67,  34,  35,  46,  22,  35,  43,
>   55,  32,  20,  31,  29,  43,  36,  30,  23,  23,
>   57,  38,  34,  34,  28,  34,  31,  22,  33,  26
> ]
>   ],
>   

Re: [sword-devel] French versification schemes

[DM Smith]

Good idea. I’ll look into how we can markup an OSIS text with a mapping to the 
KJV. If we can do that, then the form that SWORD/JSword needs is merely a form 
that the two can agree upon.

DM Smith

> On Jun 18, 2017, at 3:45 PM, Костя Маслюк  wrote:
> 
> Having one file for canon defnition and mappings is preffered in my point. 
> Having source(reference) text in that file as well is best.
> 
> So would OSIS gurus say whether it is possible to store all data required to 
> build canon and mappings in valid OSIS document?
> 
> As i realize convenience of readable formats my point is still the same. So i 
> count on some sort of authoritative desision. 
> 
> 
> 10 июня 2017 г. 5:31 PM пользователь "DM Smith"  > написал:
> Circling back around to this.
> There are two parts to the problem:
> 1) AV11N
> 2) Mapping to KJV
> 
> AV11N:
> In JSword, we don’t yet have a form for external AV11N. There are two parts 
> to this: Books and Verse/Chapter counts. Books have presence and ordering. 
> Chapters have verse counts, answering "What is the highest verse number in 
> the chapter?” JSword and SWORD differ a bit on internal representation of 
> chapter counts, but the biggest difference is that we have one representation 
> for the OT and one for the NT, allowing reuse of a testament’s chapter 
> counts. The other is a slight difference where we don’t have a separate array 
> of the counts of chapters.
> 
> In canon.h there is:
> struct sbook ntbooks[] = {
>   {"Matthew", "Matt", "Matt", 28},
> JSword doesn’t have the chapter count, 28, present in its book order array.
> 
> The canon.h vm[] array is:
> int vm[] = {
>   // Genesis
>   31, 25, 24, 26, 32, 22, 24, 22, 29, 32,
>   32, 20, 18, 24, 21, 16, 27, 33, 38, 18,
>   34, 24, 20, 67, 34, 35, 46, 22, 35, 43,
>   55, 32, 20, 31, 29, 43, 36, 30, 23, 23,
>   57, 38, 34, 34, 28, 34, 31, 22, 33, 26,
>   // Exodus
>   22, 25, 22, 31, 23, 30, 25, 32, 35, 29,
>   10, 51, 22, 31, 27, 36, 16, 27, 25, 26,
>   36, 31, 33, 18, 40, 37, 21, 43, 46, 38,
>   18, 35, 23, 35, 35, 38, 29, 31, 43, 38,
> The difference for JSword is that we use a doubly nested array:
> /* protected */ static final int[][] LAST_VERSE_OT =
> {
> // Genesis
> {
>31,  25,  24,  26,  32,  22,  24,  22,  29,  32,
>32,  20,  18,  24,  21,  16,  27,  33,  38,  18,
>34,  24,  20,  67,  34,  35,  46,  22,  35,  43,
>55,  32,  20,  31,  29,  43,  36,  30,  23,  23,
>57,  38,  34,  34,  28,  34,  31,  22,  33,  26,
> },
> // Exodus
> {
>22,  25,  22,  31,  23,  30,  25,  32,  35,  29,
>10,  51,  22,  31,  27,  36,  16,  27,  25,  26,
>36,  31,  33,  18,  40,  37,  21,  43,  46,  38,
>18,  35,  23,  35,  35,  38,  29,  31,  43,  38,
> },
> 
> We’ve maintained the comments as the same and the number of elements on a 
> line the same, allowing us to diff the corresponding canon.h for verification.
> 
> The practical difference is that we use sizeof to get the chapter count 
> rather than a lookup in a 2D book array.
> 
> Looking at Костя’s file his representation, while easy to generate from a 
> module’s original OSIS xml is too verbose. It has one XML element per verse. 
> We only need chapters/book and verses/chapter. The above representations are 
> sufficiently compact. The python script that is used to generate the canon 
> file can be adapted to create any format we choose.
> 
> The format we choose should be:
> easy to read
> easy to parse and convert into the internal format needed
> compact
> 
> The book names being standardized to OSIS is sufficient.
> The array of chapters having 10 per line make it easy for people to read.
> I’ve also spaced it so commas line up even for chapters with over 99 verses.
> 
> I’d suggest JSON over XML as it can represent arrays in a more compact form.
> 
> E.g. (off the top of my head, can be otherwise)
> KJV = [
> [
>   [ "Gen", 
> [
>   31,  25,  24,  26,  32,  22,  24,  22,  29,  32,
>   32,  20,  18,  24,  21,  16,  27,  33,  38,  18,
>   34,  24,  20,  67,  34,  35,  46,  22,  35,  43,
>   55,  32,  20,  31,  29,  43,  36,  30,  23,  23,
>   57,  38,  34,  34,  28,  34,  31,  22,  33,  26
> ]
>   ],
>   [ "Exod",
> [
>   22,  25,  22,  31,  23,  30,  25,  32,  35,  29,
>   10,  51,  22,  31,  27,  36,  16,  27,  25,  26,
>   36,  31,  33,  18,  40,  37,  21,  43,  46,  38,
>   18,  35,  23,  35,  35,  38,  29,  31,  43,  38
> ]
>   ],
> ... rest of OT ...
> ],
> [
> ... NT spec ...
> ]
> ]
> 
> Of course we could come up with a proprietary format. E.g.
> KJV 29 27
> Gen 50
>   31  25  24  26  32  22  24  22  29  32
>   32  20  18  24  21  16  27  33  38  18
>   34  24  20  67  34  35  46  22  35  43
>   55  32  20  31  29  43  36  30  23  23
>   57  38  34  34  28  34  31  22 

Re: [sword-devel] French versification schemes

[Костя Маслюк]

Having one file for canon defnition and mappings is preffered in my point.
Having source(reference) text in that file as well is best.

So would OSIS gurus say whether it is possible to store all data required
to build canon and mappings in valid OSIS document?

As i realize convenience of readable formats my point is still the same. So
i count on some sort of authoritative desision.


10 июня 2017 г. 5:31 PM пользователь "DM Smith" 
написал:

Circling back around to this.
There are two parts to the problem:
1) AV11N
2) Mapping to KJV

AV11N:
In JSword, we don’t yet have a form for external AV11N. There are two parts
to this: Books and Verse/Chapter counts. Books have presence and ordering.
Chapters have verse counts, answering "What is the highest verse number in
the chapter?” JSword and SWORD differ a bit on internal representation of
chapter counts, but the biggest difference is that we have one
representation for the OT and one for the NT, allowing reuse of a
testament’s chapter counts. The other is a slight difference where we don’t
have a separate array of the counts of chapters.

In canon.h there is:
struct sbook ntbooks[] = {
  {"Matthew", "Matt", "Matt", 28},
JSword doesn’t have the chapter count, 28, present in its book order array.

The canon.h vm[] array is:
int vm[] = {
  // Genesis
  31, 25, 24, 26, 32, 22, 24, 22, 29, 32,
  32, 20, 18, 24, 21, 16, 27, 33, 38, 18,
  34, 24, 20, 67, 34, 35, 46, 22, 35, 43,
  55, 32, 20, 31, 29, 43, 36, 30, 23, 23,
  57, 38, 34, 34, 28, 34, 31, 22, 33, 26,
  // Exodus
  22, 25, 22, 31, 23, 30, 25, 32, 35, 29,
  10, 51, 22, 31, 27, 36, 16, 27, 25, 26,
  36, 31, 33, 18, 40, 37, 21, 43, 46, 38,
  18, 35, 23, 35, 35, 38, 29, 31, 43, 38,
The difference for JSword is that we use a doubly nested array:
/* protected */ static final int[][] LAST_VERSE_OT =
{
// Genesis
{
   31,  25,  24,  26,  32,  22,  24,  22,  29,  32,
   32,  20,  18,  24,  21,  16,  27,  33,  38,  18,
   34,  24,  20,  67,  34,  35,  46,  22,  35,  43,
   55,  32,  20,  31,  29,  43,  36,  30,  23,  23,
   57,  38,  34,  34,  28,  34,  31,  22,  33,  26,
},
// Exodus
{
   22,  25,  22,  31,  23,  30,  25,  32,  35,  29,
   10,  51,  22,  31,  27,  36,  16,  27,  25,  26,
   36,  31,  33,  18,  40,  37,  21,  43,  46,  38,
   18,  35,  23,  35,  35,  38,  29,  31,  43,  38,
},

We’ve maintained the comments as the same and the number of elements on a
line the same, allowing us to diff the corresponding canon.h for
verification.

The practical difference is that we use sizeof to get the chapter count
rather than a lookup in a 2D book array.

Looking at Костя’s file his representation, while easy to generate from a
module’s original OSIS xml is too verbose. It has one XML element per
verse. We only need chapters/book and verses/chapter. The above
representations are sufficiently compact. The python script that is used to
generate the canon file can be adapted to create any format we choose.

The format we choose should be:
easy to read
easy to parse and convert into the internal format needed
compact

The book names being standardized to OSIS is sufficient.
The array of chapters having 10 per line make it easy for people to read.
I’ve also spaced it so commas line up even for chapters with over 99 verses.

I’d suggest JSON over XML as it can represent arrays in a more compact form.

E.g. (off the top of my head, can be otherwise)
KJV = [
[
  [ "Gen",
[
  31,  25,  24,  26,  32,  22,  24,  22,  29,  32,
  32,  20,  18,  24,  21,  16,  27,  33,  38,  18,
  34,  24,  20,  67,  34,  35,  46,  22,  35,  43,
  55,  32,  20,  31,  29,  43,  36,  30,  23,  23,
  57,  38,  34,  34,  28,  34,  31,  22,  33,  26
]
  ],
  [ "Exod",
[
  22,  25,  22,  31,  23,  30,  25,  32,  35,  29,
  10,  51,  22,  31,  27,  36,  16,  27,  25,  26,
  36,  31,  33,  18,  40,  37,  21,  43,  46,  38,
  18,  35,  23,  35,  35,  38,  29,  31,  43,  38
]
  ],
... rest of OT ...
],
[
... NT spec ...
]
]

Of course we could come up with a proprietary format. E.g.
KJV 29 27
Gen 50
  31  25  24  26  32  22  24  22  29  32
  32  20  18  24  21  16  27  33  38  18
  34  24  20  67  34  35  46  22  35  43
  55  32  20  31  29  43  36  30  23  23
  57  38  34  34  28  34  31  22  33  26
Exod 40
  22  25  22  31  23  30  25  32  35  29
  10  51  22  31  27  36  16  27  25  26
  36  31  33  18  40  37  21  43  46  38
  18  35  23  35  35  38  29  31  43  38

I favor a standard format over proprietary. For JSword, if standard, we'd
use a 3rd-party parser. But writing a parser is fairly trivial.

Response on standardizing mapping file next.

In Him,
DM

On Oct 2, 2016, at 6:13 AM, Troy A. Griffitts  wrote:

Thanks for bringing this up Dominique. Костя, what do we need to move
forward into this next release?

I also, with 

Re: [sword-devel] French versification schemes

[DM Smith]

Circling back around to this.
There are two parts to the problem:
1) AV11N
2) Mapping to KJV

AV11N:
In JSword, we don’t yet have a form for external AV11N. There are two parts to 
this: Books and Verse/Chapter counts. Books have presence and ordering. 
Chapters have verse counts, answering "What is the highest verse number in the 
chapter?” JSword and SWORD differ a bit on internal representation of chapter 
counts, but the biggest difference is that we have one representation for the 
OT and one for the NT, allowing reuse of a testament’s chapter counts. The 
other is a slight difference where we don’t have a separate array of the counts 
of chapters.

In canon.h there is:
struct sbook ntbooks[] = {
  {"Matthew", "Matt", "Matt", 28},
JSword doesn’t have the chapter count, 28, present in its book order array.

The canon.h vm[] array is:
int vm[] = {
  // Genesis
  31, 25, 24, 26, 32, 22, 24, 22, 29, 32,
  32, 20, 18, 24, 21, 16, 27, 33, 38, 18,
  34, 24, 20, 67, 34, 35, 46, 22, 35, 43,
  55, 32, 20, 31, 29, 43, 36, 30, 23, 23,
  57, 38, 34, 34, 28, 34, 31, 22, 33, 26,
  // Exodus
  22, 25, 22, 31, 23, 30, 25, 32, 35, 29,
  10, 51, 22, 31, 27, 36, 16, 27, 25, 26,
  36, 31, 33, 18, 40, 37, 21, 43, 46, 38,
  18, 35, 23, 35, 35, 38, 29, 31, 43, 38,
The difference for JSword is that we use a doubly nested array:
/* protected */ static final int[][] LAST_VERSE_OT =
{
// Genesis
{
   31,  25,  24,  26,  32,  22,  24,  22,  29,  32,
   32,  20,  18,  24,  21,  16,  27,  33,  38,  18,
   34,  24,  20,  67,  34,  35,  46,  22,  35,  43,
   55,  32,  20,  31,  29,  43,  36,  30,  23,  23,
   57,  38,  34,  34,  28,  34,  31,  22,  33,  26,
},
// Exodus
{
   22,  25,  22,  31,  23,  30,  25,  32,  35,  29,
   10,  51,  22,  31,  27,  36,  16,  27,  25,  26,
   36,  31,  33,  18,  40,  37,  21,  43,  46,  38,
   18,  35,  23,  35,  35,  38,  29,  31,  43,  38,
},

We’ve maintained the comments as the same and the number of elements on a line 
the same, allowing us to diff the corresponding canon.h for verification.

The practical difference is that we use sizeof to get the chapter count rather 
than a lookup in a 2D book array.

Looking at Костя’s file his representation, while easy to generate from a 
module’s original OSIS xml is too verbose. It has one XML element per verse. We 
only need chapters/book and verses/chapter. The above representations are 
sufficiently compact. The python script that is used to generate the canon file 
can be adapted to create any format we choose.

The format we choose should be:
easy to read
easy to parse and convert into the internal format needed
compact

The book names being standardized to OSIS is sufficient.
The array of chapters having 10 per line make it easy for people to read.
I’ve also spaced it so commas line up even for chapters with over 99 verses.

I’d suggest JSON over XML as it can represent arrays in a more compact form.

E.g. (off the top of my head, can be otherwise)
KJV = [
[
  [ "Gen", 
[
  31,  25,  24,  26,  32,  22,  24,  22,  29,  32,
  32,  20,  18,  24,  21,  16,  27,  33,  38,  18,
  34,  24,  20,  67,  34,  35,  46,  22,  35,  43,
  55,  32,  20,  31,  29,  43,  36,  30,  23,  23,
  57,  38,  34,  34,  28,  34,  31,  22,  33,  26
]
  ],
  [ "Exod",
[
  22,  25,  22,  31,  23,  30,  25,  32,  35,  29,
  10,  51,  22,  31,  27,  36,  16,  27,  25,  26,
  36,  31,  33,  18,  40,  37,  21,  43,  46,  38,
  18,  35,  23,  35,  35,  38,  29,  31,  43,  38
]
  ],
... rest of OT ...
],
[
... NT spec ...
]
]

Of course we could come up with a proprietary format. E.g.
KJV 29 27
Gen 50
  31  25  24  26  32  22  24  22  29  32
  32  20  18  24  21  16  27  33  38  18
  34  24  20  67  34  35  46  22  35  43
  55  32  20  31  29  43  36  30  23  23
  57  38  34  34  28  34  31  22  33  26
Exod 40
  22  25  22  31  23  30  25  32  35  29
  10  51  22  31  27  36  16  27  25  26
  36  31  33  18  40  37  21  43  46  38
  18  35  23  35  35  38  29  31  43  38

I favor a standard format over proprietary. For JSword, if standard, we'd use a 
3rd-party parser. But writing a parser is fairly trivial.

Response on standardizing mapping file next.

In Him,
DM

> On Oct 2, 2016, at 6:13 AM, Troy A. Griffitts  wrote:
> 
> Thanks for bringing this up Dominique. Костя, what do we need to move forward 
> into this next release?
> 
> I also, with you, would like to have one common format shared with JSword to 
> store our mappings.  Do you have any comments about their format?  Is it 
> something we should simply adopt and write a generator utility to our .h 
> mappings? Does JSword's format include anything we don't support? or vice 
> versa?
> 
> Troy
> 
> 
> 
> On 10/02/2016 09:08 AM, Dominique Corbex wrote:
>> On Sun, 24 Jul 2016 01:45:00 +0300
>> Костя Маслюк 

Re: [sword-devel] French versification schemes

[Peter Von Kaehne]

I have submitted quite some agfes ago a patch for the complete work. I am using it at home for now the better part of a year.

 

Peter

 

Gesendet: Donnerstag, 06. Oktober 2016 um 08:54 Uhr
Von: "Konstantin Maslyuk" <kostyamasl...@gmail.com>
An: "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
Betreff: Re: [sword-devel] French versification schemes



Dominique, you got it correctly. Prepare *.xml, convert it into cpp code with supplied python utility, you also have to insert code into cannon definition and add mappings data to versification registration.

I do not know, are you familiar with programming, so feel free to ask here or privately, or even send me prepared *.xml files so I will find time to integrate your work and send you back for testing.

Notice that you have to expand ranges to have entry for each verse, and probably, I m not sure, omit sub verse ids (pv, a,b, ...) for refMap2cpp to work.

Both cases are omissions and have to be fixed. And that are differences between JSword format and format I used. Implementation do not support sub verses anyway.

But initially I was about whole versification scheme format. If mappings data is generated separately this brings inconvenience. And not sure that it is convenient now to define scheme in cpp syntax.

I like osisId-s (something settle for me) and XML (for extensibility), so why not to make cannon generator from OSIS sources or something like that?


Blessings.



От: Troy A. Griffitts
Отправлено: ‎02.‎10.‎2016 13:15
Кому: SWORD Developers' Collaboration Forum
Тема: Re: [sword-devel] French versification schemes
 
Thanks for bringing this up Dominique. Костя, what do we need to move
forward into this next release?

I also, with you, would like to have one common format shared with
JSword to store our mappings.  Do you have any comments about their
format?  Is it something we should simply adopt and write a generator
utility to our .h mappings? Does JSword's format include anything we
don't support? or vice versa?

Troy



On 10/02/2016 09:08 AM, Dominique Corbex wrote:
> On Sun, 24 Jul 2016 01:45:00 +0300
> Костя Маслюк <kostyamasl...@gmail.com> wrote:
>
>> It is still important to place all we have for av11n schemes and mappings
>> in one place.
> I agree..
>
>>> At http://crosswire.org/~kalemas/work/v11nmapping there are examples
> I'd like to submit sword mappings to these French versification schemes
> before the next release of Sword.
>
> So, I just need to write 3 Bible xml files with all the 
> related to these schemes and the mappings  at the end, and run:
> $ python refMap2cpp.py Bible..xml
>
> and then add the resulting code to the associated .h file.
>
> Am I right?
>
> In Christ


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page




___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Konstantin Maslyuk]

Dominique, you got it correctly. Prepare *.xml, convert it into cpp code with 
supplied python utility, you also have to insert code into cannon definition 
and add mappings data to versification registration.

I do not know, are you familiar with programming, so feel free to ask here or 
privately, or even send me prepared *.xml files so I will find time to 
integrate your work and send you back for testing.

Notice that you have to expand ranges to have entry for each verse, and 
probably, I m not sure, omit sub verse ids (pv, a,b, ...) for refMap2cpp to 
work.

Both cases are omissions and have to be fixed. And that are differences between 
JSword format and format I used. Implementation do not support sub verses 
anyway.

But initially I was about whole versification scheme format. If mappings data 
is generated separately this brings inconvenience. And not sure that it is 
convenient now to define scheme in cpp syntax.

I like osisId-s (something settle for me) and XML (for extensibility), so why 
not to make cannon generator from OSIS sources or something like that? 


Blessings.

-Исходное сообщение-
От: "Troy A. Griffitts" <scr...@crosswire.org>
Отправлено: ‎02.‎10.‎2016 13:15
Кому: "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
Тема: Re: [sword-devel] French versification schemes

Thanks for bringing this up Dominique. Костя, what do we need to move 
forward into this next release?

I also, with you, would like to have one common format shared with 
JSword to store our mappings.  Do you have any comments about their 
format?  Is it something we should simply adopt and write a generator 
utility to our .h mappings? Does JSword's format include anything we 
don't support? or vice versa?

Troy



On 10/02/2016 09:08 AM, Dominique Corbex wrote:
> On Sun, 24 Jul 2016 01:45:00 +0300
> Костя Маслюк <kostyamasl...@gmail.com> wrote:
>
>> It is still important to place all we have for av11n schemes and mappings
>> in one place.
> I agree..
>
>>> At http://crosswire.org/~kalemas/work/v11nmapping there are examples
> I'd like to submit sword mappings to these French versification schemes
> before the next release of Sword.
>
> So, I just need to write 3 Bible xml files with all the 
> related to these schemes and the mappings  at the end, and run:
> $ python refMap2cpp.py Bible..xml
>
> and then add the resulting code to the associated .h file.
>
> Am I right?
>
> In Christ


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Troy A. Griffitts]

Thanks for bringing this up Dominique. Костя, what do we need to move 
forward into this next release?


I also, with you, would like to have one common format shared with 
JSword to store our mappings.  Do you have any comments about their 
format?  Is it something we should simply adopt and write a generator 
utility to our .h mappings? Does JSword's format include anything we 
don't support? or vice versa?


Troy



On 10/02/2016 09:08 AM, Dominique Corbex wrote:

On Sun, 24 Jul 2016 01:45:00 +0300
Костя Маслюк  wrote:


It is still important to place all we have for av11n schemes and mappings
in one place.

I agree..


At http://crosswire.org/~kalemas/work/v11nmapping there are examples

I'd like to submit sword mappings to these French versification schemes
before the next release of Sword.

So, I just need to write 3 Bible xml files with all the 
related to these schemes and the mappings  at the end, and run:
$ python refMap2cpp.py Bible..xml

and then add the resulting code to the associated .h file.

Am I right?

In Christ



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Dominique Corbex]

On Sun, 24 Jul 2016 01:45:00 +0300
Костя Маслюк  wrote:

> It is still important to place all we have for av11n schemes and mappings
> in one place.

I agree..

> >
> > At http://crosswire.org/~kalemas/work/v11nmapping there are examples

I'd like to submit sword mappings to these French versification schemes
before the next release of Sword.

So, I just need to write 3 Bible xml files with all the 
related to these schemes and the mappings  at the end, and run:
$ python refMap2cpp.py Bible..xml 

and then add the resulting code to the associated .h file.

Am I right? 

In Christ
-- 
domcox 

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Костя Маслюк]

Did not noticed mappings already made for JSword, i have to find time to
write a conversion tool for Sword canon format.

It is still important to place all we have for av11n schemes and mappings
in one place.

2016-06-26 20:06 GMT+03:00 Konstantin Maslyuk <kostyamasl...@gmail.com>:

> Hi all.
>
> To start with mappings we need at least text file with description of
> mappings to KJVA in free form.
>
> At http://crosswire.org/~kalemas/work/v11nmapping there are examples I
> could easily convert to portion of C code for cannon. Bible.Synodal.xml is
> surely suitable.
>
> Format is not important for me, my concern is that my work is not
> documented and not versioned by git/svn. Lets agree on some thing and make
> it suitable to reuse.
>
> Blessings.
> --
> От: Troy A. Griffitts <scr...@crosswire.org>
> Отправлено: ‎25.‎06.‎2016 14:45
> Кому: SWORD Developers' Collaboration Forum <sword-devel@crosswire.org>
> Тема: Re: [sword-devel] French versification schemes
>
> 3 new v11n schemes applied.  Dominique, thank you!
> Peter, thank you for the consolidated and reviewed patch.
> Konstantin, great suggestion.  Thank you for the mapping framework!
> Any chance Dominique or Konstantin might have time to submit sword
> mappings as well?
>
> It would be nice if we settled on a single mapping description format or
> at least a conversion tool between the formats.
>
> Any thoughts?
>
> Troy
>
>
>
> On 03/12/2016 09:01 PM, Dominique Corbex wrote:
>
> On Sat, 12 Mar 2016 09:46:07 -0500
> DM Smith <dmsm...@crosswire.org> <dmsm...@crosswire.org> wrote:
>
>
> In anticipation of these versifications being added to SWORD lib, I’ve added 
> them to JSword. If these are not current, I’ll update them with whatever is 
> checked into SWORD
>
> They are current, only a few changes to comments were made in canon_calvin.h
>
> In Christ,
>
>
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Konstantin Maslyuk]

Hi all.

To start with mappings we need at least text file with description of mappings 
to KJVA in free form.

At http://crosswire.org/~kalemas/work/v11nmapping there are examples I could 
easily convert to portion of C code for cannon. Bible.Synodal.xml is surely 
suitable.

Format is not important for me, my concern is that my work is not documented 
and not versioned by git/svn. Lets agree on some thing and make it suitable to 
reuse.

Blessings.

-Исходное сообщение-
От: "Troy A. Griffitts" <scr...@crosswire.org>
Отправлено: ‎25.‎06.‎2016 14:45
Кому: "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
Тема: Re: [sword-devel] French versification schemes

3 new v11n schemes applied.  Dominique, thank you!
Peter, thank you for the consolidated and reviewed patch.
Konstantin, great suggestion.  Thank you for the mapping framework!
Any chance Dominique or Konstantin might have time to submit sword mappings as 
well?

It would be nice if we settled on a single mapping description format or at 
least a conversion tool between the formats.

Any thoughts?

Troy




On 03/12/2016 09:01 PM, Dominique Corbex wrote:

On Sat, 12 Mar 2016 09:46:07 -0500
DM Smith <dmsm...@crosswire.org> wrote:

In anticipation of these versifications being added to SWORD lib, I’ve added 
them to JSword. If these are not current, I’ll update them with whatever is 
checked into SWORD
They are current, only a few changes to comments were made in canon_calvin.h

In Christ,___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Troy A. Griffitts]

3 new v11n schemes applied.  Dominique, thank you!
Peter, thank you for the consolidated and reviewed patch.
Konstantin, great suggestion.  Thank you for the mapping framework!
Any chance Dominique or Konstantin might have time to submit sword
mappings as well?

It would be nice if we settled on a single mapping description format or
at least a conversion tool between the formats.

Any thoughts?

Troy



On 03/12/2016 09:01 PM, Dominique Corbex wrote:
> On Sat, 12 Mar 2016 09:46:07 -0500
> DM Smith  wrote:
>
>> In anticipation of these versifications being added to SWORD lib, I’ve added 
>> them to JSword. If these are not current, I’ll update them with whatever is 
>> checked into SWORD
> They are current, only a few changes to comments were made in canon_calvin.h
>
> In Christ,

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Dominique Corbex]

On Mon, 21 Mar 2016 13:02:27 -0400
DM Smith  wrote:

> Thank you so much! I’ve checked these into JSword.

You're welcome, please find attached the two other mappings.

In Christ,
-- 
domcox 


mapping_calvin.properties
Description: Binary data


mapping_darbyfr.properties
Description: Binary data
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[DM Smith]

Thank you so much! I’ve checked these into JSword.

In Him,
DM Smith

> On Mar 16, 2016, at 5:38 PM, Dominique Corbex  wrote:
> 
> On Sat, 12 Mar 2016 21:02:05 +0100
> Dominique Corbex  wrote:
> 
>> I identified 1487 verses to be remapped from canon_segond.h to KJV. Based on 
>> the Vulgate example, I may write the mapping for JSword
> 
> Please, find attached the mappings for Jsword, from canon_segond.h to KJV.
> 
> -- 
> domcox 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Dominique Corbex]

On Sat, 12 Mar 2016 21:02:05 +0100
Dominique Corbex  wrote:

> I identified 1487 verses to be remapped from canon_segond.h to KJV. Based on 
> the Vulgate example, I may write the mapping for JSword

Please, find attached the mappings for Jsword, from canon_segond.h to KJV.

-- 
domcox 


mapping_segond.properties
Description: Binary data
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Michael H]

Whether a module will open depends on the conf file. The threads I've seen
suggest the conf should exclude all frontends pre sword 1.8 if they use
these versifications.

On Wed, Aug 26, 2015 at 3:33 PM, Kahunapule Michael Johnson <
kahunap...@ebible.org> wrote:

> If I use the new versifications to create Bibles, using the updated Sword
> library and osis2mod that includes these versifications, will those modules
> work properly with existing older Sword applications using older versions
> of the Sword library? Or should I wait for all field applications to be
> updated (which probably won't actually happen)?
>
>
> On 08/26/2015 09:50 AM, domcox wrote:
>
> As I mailed on Sunday, 23rd, I created 3 new versification schemes for French 
> Bibles in Sword:
> * Calvin for the original Bible d'Olivétan and followers, 1560+ Bible de 
> Genève, 1707-1855 Bible David Martin, 1744-1996 Bible Jean-Frederic Ostervald 
> and so on
> * DarbyFR for the French J.N. Darby Bible and revisions
> * Segond for the Louis Segond Bible and modern revisions, 1910, 1978, 2002 
> (NBS), 2007 (SG21)
> For more details, see: 
> http://www.crosswire.org/wiki/Survey_of_versification_schemes_in_French_Bibles
>
> Attached are the corresponding files canon_calvin.h, canon_darbyfr.h, 
> canon_segond.h, as well as a patch to apply to src/mgr/versificatiomgr.cpp.
> These files can also be downloaded from my website: http://dom.corbex.org
>
> Packages of Sword and Xiphos for Debian stable (Jessie 8),arch=amd64, based 
> on Sword-1.7.5a1 and including these 3 new versification schemes can be 
> downloaded from the same location:http://dom.corbex.org/pkg.
> Please note that you'll have to remove your existing libsword before 
> installing these packages.
>
> Verifications:
>
> For verification and functional tests, I used or made 3 Bibles in OSIS 
> format. A Darby Bible made with the tools developped by Sebastien Koechlin 
> from http://koocotte.org/darby, a D. Martin Bible from 
> http://www.martin1707.com and a L. Segond Bible from 
> http://www.richardlemay.com/AUD/BIB/LSG/Index.htm.
> Scripts for downloading and importing those Bibles are available at my 
> website: http://dom.corbex.org/scripts
> as well as modules ready to use : http://dom.corbex.org/sword
>
> osis2mod was used to convert each Bible into a Sword module, then emptyvss 
> was run to detect empty verses. Verses causing problems with the previous 
> versification schemes were checked with either Diatheke or Xiphos.
>
> #1. Martin 1707 (canon Calvin):
> osis2mod reports Acts.19.41 as a supplemental verse. That's correct, 
> Acts.19.40 is split in 2 verses in the source file, although it is not in the 
> printed Bible. Emptyvss does not detect any empty verses.
>
> #2. Darby 1975 (canon DarbyFR)
> osis2mod run without errors. Emptyvss reports 3 empty verses. That's correct, 
> those 3 verses are also empty in the printed Bible, a footnote informs that 
> they are only present in the Textus Receptus.
>
> #3. Segond 1910 (canon Segond)
> osis2mod reports Mark.10.53 as a supplemental verse. Depending of the 
> revision of the Segond 1910, Mark.10.52 is divided in 2 verses or not, it is 
> here. Emptyvss reports 4 empty verses from 2Tim.3.14 to 2.Tim.3.17, certainly 
> a glitch in the digitization process, the 4 verses, although present in the 
> printed Bible, are not in the source file.
>
> --Dominique
>
> domcox  
>
>
>
> ___
> sword-devel mailing list: 
> sword-devel@crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
>
>
> --
>
> Aloha,
> *Kahunapule Michael Johnson*
>
>
> *MICHAEL JOHNSON PO BOX 881143 PUKALANI HI 96788-1143*
> USA eBible.org
> MLJohnson.org
> Mobile: +1 *808-333-6921 <808-333-6921>*
> Skype: kahunapule
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Dominique Corbex]

On Sat, 12 Mar 2016 10:04:47 -0500
DM Smith  wrote:

> I’ll be adding such mappings to JSword. I’ll do my best to comment them well 
> so that they can be used as a basis for the SWORD mappings.

I've started to work on mappings, I identified 1487 verses to be remapped from 
canon_segond.h to KJV. Based on the Vulgate example, I may write the mapping 
for JSword, I have yet to figure out how to do it for Sword:)


-- 
domcox 

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Dominique Corbex]

On Sat, 12 Mar 2016 09:46:07 -0500
DM Smith  wrote:

> In anticipation of these versifications being added to SWORD lib, I’ve added 
> them to JSword. If these are not current, I’ll update them with whatever is 
> checked into SWORD

They are current, only a few changes to comments were made in canon_calvin.h

In Christ,
-- 
domcox 

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[DM Smith]

Konstantin,

I’ll be adding such mappings to JSword. I’ll do my best to comment them well so 
that they can be used as a basis for the SWORD mappings. Unfortunately, there 
is little resemblance between the two formats.

Below is an example for the Vulgate.

Working together in Christ,
DM Smith

# Vulgate => KJV
# pv=canonical title; v=verse; a,b etc = part verses.
# created by TyndaleSTEP at gmail dot com DIB 2013
# updated by DM Smith

# KJV's verse is split in two
Ps.2.12=Ps.2.12!a
Ps.2.13=Ps.2.12!b

# Has canonical title in KJV that is separate verse
Ps.3.1=Ps.3.1!pv
Ps.3.2=Ps.3.1!v
Ps.3.3-Ps.3.9=Ps.3.2-Ps.3.8

# Has canonical title in KJV that is separate verse
Ps.4.1=Ps.4.1!pv
Ps.4.2=Ps.4.1!v
Ps.4.3-Ps.4.8=Ps.4.2-Ps.4.7
# KJV's verse is split in two
Ps.4.9=Ps.4.8!a
Ps.4.10=Ps.4.8!b

# Has canonical title in KJV that is separate verse
Ps.5.1=Ps.5.1!pv
Ps.5.2=Ps.5.1!v
Ps.5.3-Ps.5.13=Ps.5.2-Ps.5.12

# Has canonical title in KJV that is separate verse
Ps.6.1=Ps.6.1!pv
Ps.6.2=Ps.6.1!v
Ps.6.3-Ps.6.11=Ps.6.2-Ps.6.10

# Has canonical title in KJV that is separate verse
Ps.7.1=Ps.7.1!pv
Ps.7.2=Ps.7.1!v
Ps.7.3-Ps.7.18=Ps.7.2-Ps.7.17

# Has canonical title in KJV that is separate verse
Ps.8.1=Ps.8.1!pv
Ps.8.2=Ps.8.1!v
Ps.8.3-Ps.8.10=Ps.8.2-Ps.8.9

# Has canonical title in KJV that is separate verse
Ps.9.1=Ps.9.1!pv
Ps.9.2=Ps.9.1!v
Ps.9.3-Ps.9.21=Ps.9.2-Ps.9.20
# Vulgate's Ps 9 contains KJV's Psalm 10. Following chapters shifted from here
# Need to explicitly map verse 0 for chapter shifts
# Here we want it to be shown at the same point as verse 1
Ps.9.22=Ps.10.0
Ps.9.22=Ps.10.1
Ps.9.23-Ps.9.39=Ps.10.2-Ps.10.18

# Has canonical title in KJV that is separate verse
# First full chapter shift in Psalms
Ps.10.0=Ps.11.0
Ps.10.1=Ps.11.1!pv
Ps.10.2=Ps.11.1!v
Ps.10.3-Ps.10.8=Ps.11.2-Ps.11.7

# Has canonical title in KJV that is separate verse
Ps.11.0=Ps.12.0
Ps.11.1=Ps.12.1!pv
Ps.11.2=Ps.12.1!v
Ps.11.3-Ps.11.9=Ps.12.2-Ps.12.8

# Has canonical title in KJV; Wholly in verse 1
Ps.12.0-Ps.12.6=Ps.13.0-Ps.13.6

# Has canonical title in KJV; Wholly in verse 1
Ps.13.0-Ps.13.7=Ps.14.0-Ps.14.7

# Has canonical title in KJV; Wholly in verse 1
Ps.14.0-Ps.14.5=Ps.15.0-Ps.15.5

# Has canonical title in KJV; Wholly in verse 1
Ps.15.0-Ps.15.9=Ps.16.0-Ps.16.9
Ps.15.10!a=Ps.16.10
Ps.15.10!b=Ps.16.11

# Has canonical title in KJV; Wholly in verse 1
Ps.16.0-Ps.16.15=Ps.17.0-Ps.17.15

# Has canonical title in KJV that is separate verse
Ps.17.0=Ps.18.0
Ps.17.1=Ps.18.1!pv
Ps.17.2=Ps.18.1!v
Ps.17.3-Ps.17.51=Ps.18.2-Ps.18.50

# Has canonical title in KJV that is separate verse
Ps.18.0=Ps.19.0
Ps.18.1=Ps.19.1!pv
Ps.18.2=Ps.19.1!v
Ps.18.3-Ps.18.15=Ps.19.2-Ps.19.16

# Has canonical title in KJV that is separate verse
Ps.19.0=Ps.20.0
Ps.19.1=Ps.20.1!pv
Ps.19.2=Ps.20.1!v
Ps.19.3-Ps.19.10=Ps.20.2-Ps.20.9

# Has canonical title in KJV that is separate verse
Ps.20.0=Ps.21.0
Ps.20.1=Ps.21.1!pv
Ps.20.2=Ps.21.1!v
Ps.20.3-Ps.20.14=Ps.21.2-Ps.21.13

# Has canonical title in KJV that is separate verse
Ps.21.0=Ps.22.0
Ps.21.1=Ps.22.1!pv
Ps.21.2=Ps.22.1!v
Ps.21.3-Ps.21.32=Ps.22.2-Ps.22.31

# Has canonical title in KJV; Wholly in verse 1
Ps.22.0-Ps.22.6=Ps.23.0-Ps.23.6

# Has canonical title in KJV; Wholly in verse 1
Ps.23.0-Ps.23.10=Ps.24.0-Ps.24.10

# Has canonical title in KJV; Wholly in verse 1
Ps.24.0-Ps.24.22=Ps.25.0-Ps.25.22

# Has canonical title in KJV; Wholly in verse 1
Ps.25.0-Ps.25.12=Ps.26.0-Ps.26.12

# Has canonical title in KJV; Wholly in verse 1
Ps.26.0-Ps.26.14=Ps.27.0-Ps.27.14

# Has canonical title in KJV; Wholly in verse 1
Ps.27.0-Ps.27.9=Ps.28.0-Ps.28.9

# Has canonical title in KJV; Wholly in verse 1
Ps.28.0-Ps.28.11=Ps.29.0-Ps.29.11

# Has canonical title in KJV that is separate verse
Ps.29.0=Ps.30.0
Ps.29.1=Ps.30.1!pv
Ps.29.2=Ps.30.1!v
Ps.29.3-Ps.29.13=Ps.30.2-Ps.30.12

# Has canonical title in KJV that is separate verse
Ps.30.0=Ps.31.0
Ps.30.1=Ps.31.1!pv
Ps.30.2=Ps.31.1!v
Ps.30.3-Ps.30.25=Ps.31.2-Ps.31.24

# Has canonical title in KJV; Wholly in verse 1
Ps.31.0-Ps.31.11=Ps.32.0-Ps.32.11

# Has no canonical title in KJV
Ps.32.0-Ps.32.22=Ps.33.0-Ps.33.22

# Has canonical title in KJV that is separate verse
Ps.33.0=Ps.34.0
Ps.33.1=Ps.34.1!pv
Ps.33.2=Ps.34.1!v
Ps.33.3-Ps.33.23=Ps.34.2-Ps.34.22

# Has canonical title in KJV; Wholly in verse 1
Ps.34.0-Ps.34.28=Ps.35.0-Ps.35.28

# Has canonical title in KJV that is separate verse
Ps.35.0=Ps.36.0
Ps.35.1=Ps.36.1!pv
Ps.35.2=Ps.36.1!v
Ps.35.3-Ps.35.13=Ps.36.2-Ps.36.12

# Has canonical title in KJV; Wholly in verse 1
Ps.36.0-Ps.36.40=Ps.37.0-Ps.37.40

# Has canonical title in KJV that is separate verse
Ps.37.0=Ps.38.0
Ps.37.1=Ps.38.1!pv
Ps.37.2=Ps.38.1!v
Ps.37.3-Ps.37.23=Ps.38.2-Ps.38.22

# Has canonical title in KJV that is separate verse
Ps.38.0=Ps.39.0
Ps.38.1=Ps.39.1!pv
Ps.38.2=Ps.39.1!v
Ps.38.3-Ps.38.14=Ps.39.2-Ps.39.13

# Has canonical title in KJV that is separate verse
Ps.39.0=Ps.40.0
Ps.39.1=Ps.40.1!pv
Ps.39.2=Ps.40.1!v
Ps.39.3-Ps.39.18=Ps.40.2-Ps.40.17

# Has canonical title in KJV 

Re: [sword-devel] French versification schemes

[DM Smith]

In anticipation of these versifications being added to SWORD lib, I’ve added 
them to JSword. If these are not current, I’ll update them with whatever is 
checked into SWORD.

We still need to add mapping files to and from the KJV for JSword. (Somebody 
will need to do that for SWORD too!) That’ll take a few hours apiece, but is 
not too hard. (I hope.) Doing so takes analysis of Psalm titles, figuring out 
which verses are split, merged or otherwise not present in one or the other. 
The format that JSword and SWORD uses is significantly different. I’ll comment 
the JSword mappings well enough that they can be helpful to creating the SWORD 
mappings.

None of the links to dom.corbex.org  that are mentioned 
below are current. Most give a 404 — Not Found error.

In His Service,
DM

> On Aug 26, 2015, at 3:50 PM, domcox  wrote:
> 
> 
> As I mailed on Sunday, 23rd, I created 3 new versification schemes for French 
> Bibles in Sword:
> * Calvin for the original Bible d'Olivétan and followers, 1560+ Bible de 
> Genève, 1707-1855 Bible David Martin, 1744-1996 Bible Jean-Frederic Ostervald 
> and so on
> * DarbyFR for the French J.N. Darby Bible and revisions
> * Segond for the Louis Segond Bible and modern revisions, 1910, 1978, 2002 
> (NBS), 2007 (SG21)
> For more details, see: 
> http://www.crosswire.org/wiki/Survey_of_versification_schemes_in_French_Bibles
>  
> 
> Attached are the corresponding files canon_calvin.h, canon_darbyfr.h, 
> canon_segond.h, as well as a patch to apply to src/mgr/versificatiomgr.cpp.
> These files can also be downloaded from my website: 
> http://dom.corbex.org
> 
> Packages of Sword and Xiphos for Debian stable (Jessie 8),arch=amd64, based 
> on Sword-1.7.5a1 and including these 3 new versification schemes can be 
> downloaded from the same location:
> http://dom.corbex.org/pkg. 
> Please note that you'll have to remove your existing libsword before 
> installing these packages.
> 
> Verifications:
> 
> For verification and functional tests, I used or made 3 Bibles in OSIS 
> format. A Darby Bible made with the tools developped by Sebastien Koechlin 
> from http://koocotte.org/darby, a D. Martin Bible from 
> http://www.martin1707.com and a L. Segond Bible from 
> http://www.richardlemay.com/AUD/BIB/LSG/Index.htm. 
> Scripts for downloading and importing those Bibles are available at my 
> website: 
> http://dom.corbex.org/scripts
> as well as modules ready to use : 
> http://dom.corbex.org/sword 
> 
> osis2mod was used to convert each Bible into a Sword module, then emptyvss 
> was run to detect empty verses. Verses causing problems with the previous 
> versification schemes were checked with either Diatheke or Xiphos.
> 
> #1. Martin 1707 (canon Calvin):
> osis2mod reports Acts.19.41 as a supplemental verse. That's correct, 
> Acts.19.40 is split in 2 verses in the source file, although it is not in the 
> printed Bible. Emptyvss does not detect any empty verses.
> 
> #2. Darby 1975 (canon DarbyFR)
> osis2mod run without errors. Emptyvss reports 3 empty verses. That's correct, 
> those 3 verses are also empty in the printed Bible, a footnote informs that 
> they are only present in the Textus Receptus.
> 
> #3. Segond 1910 (canon Segond)
> osis2mod reports Mark.10.53 as a supplemental verse. Depending of the 
> revision of the Segond 1910, Mark.10.52 is divided in 2 verses or not, it is 
> here. Emptyvss reports 4 empty verses from 2Tim.3.14 to 2.Tim.3.17, certainly 
> a glitch in the digitization process, the 4 verses, although present in the 
> printed Bible, are not in the source file.
> 
> --Dominique
> 
> domcox 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Konstantin Maslyuk]

Just looked at.

If your v11ns will be approved, what about to add mappings to KJVA so one would 
use them in parallel views in frontends?

Blessings.

-Исходное сообщение-
От: domcox dominique.cor...@gmail.com
Отправлено: ‎26.‎08.‎2015 22:50
Кому: sword-devel@crosswire.org sword-devel@crosswire.org
Тема: [sword-devel] French versification schemes


As I mailed on Sunday, 23rd, I created 3 new versification schemes for French 
Bibles in Sword:
* Calvin for the original Bible d'Olivétan and followers, 1560+ Bible de 
Genève, 1707-1855 Bible David Martin, 1744-1996 Bible Jean-Frederic Ostervald 
and so on
* DarbyFR for the French J.N. Darby Bible and revisions
* Segond for the Louis Segond Bible and modern revisions, 1910, 1978, 2002 
(NBS), 2007 (SG21)
For more details, see: 
http://www.crosswire.org/wiki/Survey_of_versification_schemes_in_French_Bibles 

Attached are the corresponding files canon_calvin.h, canon_darbyfr.h, 
canon_segond.h, as well as a patch to apply to src/mgr/versificatiomgr.cpp.
These files can also be downloaded from my website: 
http://dom.corbex.org

Packages of Sword and Xiphos for Debian stable (Jessie 8),arch=amd64, based on 
Sword-1.7.5a1 and including these 3 new versification schemes can be downloaded 
from the same location:
http://dom.corbex.org/pkg. 
Please note that you'll have to remove your existing libsword before installing 
these packages.

Verifications:

For verification and functional tests, I used or made 3 Bibles in OSIS format. 
A Darby Bible made with the tools developped by Sebastien Koechlin from 
http://koocotte.org/darby, a D. Martin Bible from http://www.martin1707.com and 
a L. Segond Bible from http://www.richardlemay.com/AUD/BIB/LSG/Index.htm. 
Scripts for downloading and importing those Bibles are available at my website: 
http://dom.corbex.org/scripts
as well as modules ready to use : 
http://dom.corbex.org/sword 

osis2mod was used to convert each Bible into a Sword module, then emptyvss was 
run to detect empty verses. Verses causing problems with the previous 
versification schemes were checked with either Diatheke or Xiphos.

#1. Martin 1707 (canon Calvin):
osis2mod reports Acts.19.41 as a supplemental verse. That's correct, Acts.19.40 
is split in 2 verses in the source file, although it is not in the printed 
Bible. Emptyvss does not detect any empty verses.

#2. Darby 1975 (canon DarbyFR)
osis2mod run without errors. Emptyvss reports 3 empty verses. That's correct, 
those 3 verses are also empty in the printed Bible, a footnote informs that 
they are only present in the Textus Receptus.

#3. Segond 1910 (canon Segond)
osis2mod reports Mark.10.53 as a supplemental verse. Depending of the revision 
of the Segond 1910, Mark.10.52 is divided in 2 verses or not, it is here. 
Emptyvss reports 4 empty verses from 2Tim.3.14 to 2.Tim.3.17, certainly a 
glitch in the digitization process, the 4 verses, although present in the 
printed Bible, are not in the source file.

--Dominique
 
domcox dominique.cor...@gmail.com
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Kahunapule Michael Johnson]

  
  
If I use the new versifications to
  create Bibles, using the updated Sword library and osis2mod that
  includes these versifications, will those modules work properly
  with existing older Sword applications using older versions of the
  Sword library? Or should I wait for all field applications to be
  updated (which probably won't actually happen)?
  
  On 08/26/2015 09:50 AM, domcox wrote:


  
As I mailed on Sunday, 23rd, I created 3 new versification schemes for French Bibles in Sword:
* Calvin for the original Bible d'Olivétan and followers, 1560+ Bible de Genève, 1707-1855 Bible David Martin, 1744-1996 Bible Jean-Frederic Ostervald and so on
* DarbyFR for the French J.N. Darby Bible and revisions
* Segond for the Louis Segond Bible and modern revisions, 1910, 1978, 2002 (NBS), 2007 (SG21)
For more details, see: 
http://www.crosswire.org/wiki/Survey_of_versification_schemes_in_French_Bibles 

Attached are the corresponding files canon_calvin.h, canon_darbyfr.h, canon_segond.h, as well as a patch to apply to src/mgr/versificatiomgr.cpp.
These files can also be downloaded from my website: 
http://dom.corbex.org

Packages of Sword and Xiphos for Debian stable (Jessie 8),arch=amd64, based on Sword-1.7.5a1 and including these 3 new versification schemes can be downloaded from the same location:
http://dom.corbex.org/pkg. 
Please note that you'll have to remove your existing libsword before installing these packages.

Verifications:

For verification and functional tests, I used or made 3 Bibles in OSIS format. A Darby Bible made with the tools developped by Sebastien Koechlin from http://koocotte.org/darby, a D. Martin Bible from http://www.martin1707.com and a L. Segond Bible from http://www.richardlemay.com/AUD/BIB/LSG/Index.htm. 
Scripts for downloading and importing those Bibles are available at my website: 
http://dom.corbex.org/scripts
as well as modules ready to use : 
http://dom.corbex.org/sword 

osis2mod was used to convert each Bible into a Sword module, then emptyvss was run to detect empty verses. Verses causing problems with the previous versification schemes were checked with either Diatheke or Xiphos.

#1. Martin 1707 (canon Calvin):
osis2mod reports Acts.19.41 as a supplemental verse. That's correct, Acts.19.40 is split in 2 verses in the source file, although it is not in the printed Bible. Emptyvss does not detect any empty verses.

#2. Darby 1975 (canon DarbyFR)
osis2mod run without errors. Emptyvss reports 3 empty verses. That's correct, those 3 verses are also empty in the printed Bible, a footnote informs that they are only present in the Textus Receptus.

#3. Segond 1910 (canon Segond)
osis2mod reports Mark.10.53 as a supplemental verse. Depending of the revision of the Segond 1910, Mark.10.52 is divided in 2 verses or not, it is here. Emptyvss reports 4 empty verses from 2Tim.3.14 to 2.Tim.3.17, certainly a glitch in the digitization process, the 4 verses, although present in the printed Bible, are not in the source file.

--Dominique
 
domcox dominique.cor...@gmail.com

  
  
  
  ___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page



-- 
  
  Aloha,
  Kahunapule Michael Johnson
  

  
MICHAEL JOHNSON
  PO BOX 881143
  PUKALANI HI 96788-1143
USA

eBible.org
MLJohnson.org
Mobile: +1 808-333-6921
Skype: kahunapule
  

  

  


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] French versification schemes

[Peter von Kaehne]

We keep a bunch of modules for older installs in Crosswire Attic repository. 

This has slowly fallen by the wayside as ww havent added recently any 
versification which had a similar impact as the French will have. But it is a 
mechanism you could use if you want to. Any module which is replaced by a new 
one with a better, new versification is stored for a while in the attic repo 
for use by older frontends

Peter

Sent from my phone. Apologies for brevity and typos.On 26 Aug 2015 21:33, 
Kahunapule Michael Johnson kahunap...@ebible.org wrote:

 If I use the new versifications to create Bibles, using the updated Sword 
 library and osis2mod that includes these versifications, will those modules 
 work properly with existing older Sword applications using older versions of 
 the Sword library? Or should I wait for all field applications to be updated 
 (which probably won't actually happen)?

 On 08/26/2015 09:50 AM, domcox wrote:


 As I mailed on Sunday, 23rd, I created 3 new versification schemes for 
 French Bibles in Sword:

 * Calvin for the original Bible d'Olivétan and followers, 1560+ Bible de 
 Genève, 1707-1855 Bible David Martin, 1744-1996 Bible Jean-Frederic 
 Ostervald and so on

 * DarbyFR for the French J.N. Darby Bible and revisions

 * Segond for the Louis Segond Bible and modern revisions, 1910, 1978, 2002 
 (NBS), 2007 (SG21)

 For more details, see: 

 http://www.crosswire.org/wiki/Survey_of_versification_schemes_in_French_Bibles
  



 Attached are the corresponding files canon_calvin.h, canon_darbyfr.h, 
 canon_segond.h, as well as a patch to apply to src/mgr/versificatiomgr.cpp.

 These files can also be downloaded from my website: 

 http://dom.corbex.org



 Packages of Sword and Xiphos for Debian stable (Jessie 8),arch=amd64, based 
 on Sword-1.7.5a1 and including these 3 new versification schemes can be 
 downloaded from the same location:

 http://dom.corbex.org/pkg. 

 Please note that you'll have to remove your existing libsword before 
 installing these packages.



 Verifications:



 For verification and functional tests, I used or made 3 Bibles in OSIS 
 format. A Darby Bible made with the tools developped by Sebastien Koechlin 
 from http://koocotte.org/darby, a D. Martin Bible from 
 http://www.martin1707.com and a L. Segond Bible from 
 http://www.richardlemay.com/AUD/BIB/LSG/Index.htm. 

 Scripts for downloading and importing those Bibles are available at my 
 website: 

 http://dom.corbex.org/scripts

 as well as modules ready to use : 

 http://dom.corbex.org/sword 



 osis2mod was used to convert each Bible into a Sword module, then emptyvss 
 was run to detect empty verses. Verses causing problems with the previous 
 versification schemes were checked with either Diatheke or Xiphos.



 #1. Martin 1707 (canon Calvin):

 osis2mod reports Acts.19.41 as a supplemental verse. That's correct, 
 Acts.19.40 is split in 2 verses in the source file, although it is not in 
 the printed Bible. Emptyvss does not detect any empty verses.



 #2. Darby 1975 (canon DarbyFR)

 osis2mod run without errors. Emptyvss reports 3 empty verses. That's 
 correct, those 3 verses are also empty in the printed Bible, a footnote 
 informs that they are only present in the Textus Receptus.



 #3. Segond 1910 (canon Segond)

 osis2mod reports Mark.10.53 as a supplemental verse. Depending of the 
 revision of the Segond 1910, Mark.10.52 is divided in 2 verses or not, it is 
 here. Emptyvss reports 4 empty verses from 2Tim.3.14 to 2.Tim.3.17, 
 certainly a glitch in the digitization process, the 4 verses, although 
 present in the printed Bible, are not in the source file.



 --Dominique

  

 domcox dominique.cor...@gmail.com



 ___

 sword-devel mailing list: sword-devel@crosswire.org

 http://www.crosswire.org/mailman/listinfo/sword-devel

 Instructions to unsubscribe/change your settings at above page



 -- 

 Aloha,
 Kahunapule Michael Johnson

 MICHAEL JOHNSON
 PO BOX 881143
 PUKALANI HI 96788-1143
 USA
 eBible.org
 MLJohnson.org
 Mobile: +1 808-333-6921
 Skype: kahunapule
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page