Re: [sword-devel] Release Wrapup

[Karl Kleinpaste]

On 02/21/2017 02:23 PM, Greg Hellings wrote:
> Karl? I feel like he prefers C

I write C++ literally every day. But you interact with me only re:
Xiphos, which is half C++, half C, and the boundary is unclean.

___
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] Release Wrapup

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

> There are a few others of us who know it, and can - in a pinch - make
some fixes to it. There are some others in the broader community who are in
the C++ world (Jaak, Gary, etc) but none of them are active on the engine
for myriad reasons

I d be happy if it would be possible to be more active in engine
development than Troy do.

Just a thought, blessings.
___
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] Release Wrapup

[Tomas Groth]

Regarding SWORD and python, I'll just leave this here:
https://gitlab.com/tgc-dk/pysword

No, it is *not* backed by anyone but me.
And no, it does not implement all the features of libSword, nor is it meant
to.

Best regards,
Tomas

Den 21/02/2017 20:52 skrev "Greg Hellings" :

>
>
> On Sun, Feb 19, 2017 at 1:52 PM, Matt Zabojnik  wrote:
>
>> I don't mean to derail this in any way. I've previously only had
>> experience with HTML/PHP/SQL, and I'm now learning Python (in order to
>> develop a SWORD-related Android app)
>>
>> Would it be beneficial to port the whole project to Python? That seems to
>> be a widely known and easy to learn language.
>> Forgive my ignorance if this question is completely unreasonable. I've
>> previously only ventured into hack-together type of workaround stuff when
>> it comes to computers, rather than true programming. (Learning RegEx has
>> been an amazing eye-opening experience in module making)
>>
>
> Not likely. There is already an existing Java port, and there is little
> interest in maintaining more than the one official port. The language is
> not a significant barrier to improvement, adoption, or advancement. In
> fact, being written in decently portable C and C++ is one of the best
> technical merits of the engine. It allows us to offer bindings to Perl (for
> scripting) and Python (for BPBible and the like), and wrappers into
> Objective-C (for our Mac and iPhone apps), and into the JNI interface (for
> at least one Android app). Maintaining a pure-Java port gives access to
> other environments (Java Swing UI, web, and native Android) and could allow
> easy access to others as well (e.g. Jython, JRuby, JavaScript).
>
> If you were going to start a whole new port into a language like Python
> you would begin to open the door to format shifting the modules, and a
> whole host of other things that would be incompatible with the current
> project. Not many Python developers are going to happily attack the binary
> flat format that a Sword module currently lives in. They're going to want
> to use something else, most likely. You're going to lose out on around two
> decades of support, features, bug fixes, and small tweaks and have to start
> again to re-gain the code maturity that the engine already has. And there's
> far more you'd lose out on.
>
> No, a new port is not likely to happen within the community. Not to say it
> couldn't happen outside of the community. But you're not likely to get core
> developer support for abandoning the current library and shifting to a new
> port into a language like Python. The closest you'll probably get is forks,
> like the existing Sword++ fork. Or people who have wrapped Sword in order
> to format shift content, e.g. into a SQL database or JSON or such, for use
> in a new application.
>
> --Greg
>
>
>> I know BPBible was written mostly in Python. If I get good enough at
>> Python and have the time I may fork and develop that front-end where I can.
>> I'm still pretty green though to say the least.
>>
>> On Sun, Feb 19, 2017 at 11:06 AM, David Haslam 
>> wrote:
>>
>>> Are we any closer to a release of SWORD v1.8 ?
>>>
>>> cf. Troy started this thread last October.
>>>
>>> As someone without any experience of C++ programming, I sometimes wonder
>>> how
>>> many C++ programmers are still active in CrossWire. It seems far, far
>>> fewer
>>> than when I first linked up with CrossWire in 2008.
>>>
>>> cf. Last month, Karl noted some anniversaries that are passing us by yet
>>> again
>>>
>>> Which known bugs in the engine will be fixed in v1.8 ?
>>>
>>> Best regards,
>>>
>>> David
>>>
>>>
>>>
>>> --
>>> View this message in context: http://sword-dev.350566.n4.nab
>>> ble.com/Release-Wrapup-tp4656501p4656698.html
>>> Sent from the SWORD Dev mailing list archive at Nabble.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
>>>
>>
>>
>>
>> --
>> --
>> PGP ID: 0x5fa5cbaecfd5690c
>> --
>>
>> ___
>> 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] Release Wrapup

[Greg Hellings]

On Sun, Feb 19, 2017 at 1:52 PM, Matt Zabojnik  wrote:

> I don't mean to derail this in any way. I've previously only had
> experience with HTML/PHP/SQL, and I'm now learning Python (in order to
> develop a SWORD-related Android app)
>
> Would it be beneficial to port the whole project to Python? That seems to
> be a widely known and easy to learn language.
> Forgive my ignorance if this question is completely unreasonable. I've
> previously only ventured into hack-together type of workaround stuff when
> it comes to computers, rather than true programming. (Learning RegEx has
> been an amazing eye-opening experience in module making)
>

Not likely. There is already an existing Java port, and there is little
interest in maintaining more than the one official port. The language is
not a significant barrier to improvement, adoption, or advancement. In
fact, being written in decently portable C and C++ is one of the best
technical merits of the engine. It allows us to offer bindings to Perl (for
scripting) and Python (for BPBible and the like), and wrappers into
Objective-C (for our Mac and iPhone apps), and into the JNI interface (for
at least one Android app). Maintaining a pure-Java port gives access to
other environments (Java Swing UI, web, and native Android) and could allow
easy access to others as well (e.g. Jython, JRuby, JavaScript).

If you were going to start a whole new port into a language like Python you
would begin to open the door to format shifting the modules, and a whole
host of other things that would be incompatible with the current project.
Not many Python developers are going to happily attack the binary flat
format that a Sword module currently lives in. They're going to want to use
something else, most likely. You're going to lose out on around two decades
of support, features, bug fixes, and small tweaks and have to start again
to re-gain the code maturity that the engine already has. And there's far
more you'd lose out on.

No, a new port is not likely to happen within the community. Not to say it
couldn't happen outside of the community. But you're not likely to get core
developer support for abandoning the current library and shifting to a new
port into a language like Python. The closest you'll probably get is forks,
like the existing Sword++ fork. Or people who have wrapped Sword in order
to format shift content, e.g. into a SQL database or JSON or such, for use
in a new application.

--Greg


> I know BPBible was written mostly in Python. If I get good enough at
> Python and have the time I may fork and develop that front-end where I can.
> I'm still pretty green though to say the least.
>
> On Sun, Feb 19, 2017 at 11:06 AM, David Haslam 
> wrote:
>
>> Are we any closer to a release of SWORD v1.8 ?
>>
>> cf. Troy started this thread last October.
>>
>> As someone without any experience of C++ programming, I sometimes wonder
>> how
>> many C++ programmers are still active in CrossWire. It seems far, far
>> fewer
>> than when I first linked up with CrossWire in 2008.
>>
>> cf. Last month, Karl noted some anniversaries that are passing us by yet
>> again
>>
>> Which known bugs in the engine will be fixed in v1.8 ?
>>
>> Best regards,
>>
>> David
>>
>>
>>
>> --
>> View this message in context: http://sword-dev.350566.n4.nab
>> ble.com/Release-Wrapup-tp4656501p4656698.html
>> Sent from the SWORD Dev mailing list archive at Nabble.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
>>
>
>
>
> --
> --
> PGP ID: 0x5fa5cbaecfd5690c
> --
>
> ___
> 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] Release Wrapup

[Greg Hellings]

On Sun, Feb 19, 2017 at 12:06 PM, David Haslam 
wrote:

> Are we any closer to a release of SWORD v1.8 ?
>

No. I don't think there's been a single commit to the engine since that
time. At least, I don't recall seeing any messages float across my desk.


>
> cf. Troy started this thread last October.
>
> As someone without any experience of C++ programming, I sometimes wonder
> how
> many C++ programmers are still active in CrossWire. It seems far, far fewer
> than when I first linked up with CrossWire in 2008.
>

As far as people who mainly work in C++, we're probably at one (Troy).
Maybe two (Karl? I feel like he prefers C).

There are a few others of us who know it, and can - in a pinch - make some
fixes to it. There are some others in the broader community who are in the
C++ world (Jaak, Gary, etc) but none of them are active on the engine for
myriad reasons.

--Greg


>
> cf. Last month, Karl noted some anniversaries that are passing us by yet
> again
>
> Which known bugs in the engine will be fixed in v1.8 ?
>
> Best regards,
>
> David
>
>
>
> --
> View this message in context: http://sword-dev.350566.n4.
> nabble.com/Release-Wrapup-tp4656501p4656698.html
> Sent from the SWORD Dev mailing list archive at Nabble.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
>
___
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] Release Wrapup

[Matt Zabojnik]

I don't mean to derail this in any way. I've previously only had experience
with HTML/PHP/SQL, and I'm now learning Python (in order to develop a
SWORD-related Android app)

Would it be beneficial to port the whole project to Python? That seems to
be a widely known and easy to learn language.
Forgive my ignorance if this question is completely unreasonable. I've
previously only ventured into hack-together type of workaround stuff when
it comes to computers, rather than true programming. (Learning RegEx has
been an amazing eye-opening experience in module making)

I know BPBible was written mostly in Python. If I get good enough at Python
and have the time I may fork and develop that front-end where I can. I'm
still pretty green though to say the least.

On Sun, Feb 19, 2017 at 11:06 AM, David Haslam 
wrote:

> Are we any closer to a release of SWORD v1.8 ?
>
> cf. Troy started this thread last October.
>
> As someone without any experience of C++ programming, I sometimes wonder
> how
> many C++ programmers are still active in CrossWire. It seems far, far fewer
> than when I first linked up with CrossWire in 2008.
>
> cf. Last month, Karl noted some anniversaries that are passing us by yet
> again
>
> Which known bugs in the engine will be fixed in v1.8 ?
>
> Best regards,
>
> David
>
>
>
> --
> View this message in context: http://sword-dev.350566.n4.
> nabble.com/Release-Wrapup-tp4656501p4656698.html
> Sent from the SWORD Dev mailing list archive at Nabble.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
>



-- 
--
PGP ID: 0x5fa5cbaecfd5690c
--
___
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] Release Wrapup

[David Haslam]

Are we any closer to a release of SWORD v1.8 ?

cf. Troy started this thread last October.

As someone without any experience of C++ programming, I sometimes wonder how
many C++ programmers are still active in CrossWire. It seems far, far fewer
than when I first linked up with CrossWire in 2008.

cf. Last month, Karl noted some anniversaries that are passing us by yet
again

Which known bugs in the engine will be fixed in v1.8 ?

Best regards,

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Release-Wrapup-tp4656501p4656698.html
Sent from the SWORD Dev mailing list archive at Nabble.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] Release Wrapup

[Peter Von Kaehne]

I will deal with it later tonight or tomorrow at latest. Thanks Dominique

> Gesendet: Montag, 23. Januar 2017 um 20:30 Uhr
> Von: "Dominique Corbex" 
> An: sword-devel@crosswire.org
> Betreff: Re: [sword-devel] Release Wrapup
>
> 
> Please find attached a patch against current svn which updates the French 
> translation.
> 
> This patch, result of a collective effort, updates the current French locale 
> and adds
> new translations for LXX, Vulgate, Ethiopian Orthodox and other canons.
>  
> Many thanks to Yvand and Cyrille for their help in this translation.
> 
> Already sent before, but still not merged in current svn.
> 
> 
> Dominique
> -- 
> domcox 
> 
> 
> On Sat, 21 Jan 2017 12:58:43 -0800 (PST)
> David Haslam  wrote:
> 
> > Where are we up to with supporting the three new av11ns for French Bibles
> > that Dominique documented?
> > 
> > If we're not about to release SWORD 2.0 anytime soon, what's preventing
> > releasing an interim SWORD 1.8 (or even SWORD 1.7.3) with the new av11ns?
> > 
> > I mean, right now, we can't even test osis2mod.exe and specify one of these
> > with the -v option.
> 
> 
> ___
> 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] Release Wrapup

[Dominique Corbex]

Please find attached a patch against current svn which updates the French 
translation.

This patch, result of a collective effort, updates the current French locale 
and adds
new translations for LXX, Vulgate, Ethiopian Orthodox and other canons.
 
Many thanks to Yvand and Cyrille for their help in this translation.

Already sent before, but still not merged in current svn.


Dominique
-- 
domcox 


On Sat, 21 Jan 2017 12:58:43 -0800 (PST)
David Haslam  wrote:

> Where are we up to with supporting the three new av11ns for French Bibles
> that Dominique documented?
> 
> If we're not about to release SWORD 2.0 anytime soon, what's preventing
> releasing an interim SWORD 1.8 (or even SWORD 1.7.3) with the new av11ns?
> 
> I mean, right now, we can't even test osis2mod.exe and specify one of these
> with the -v option.


diff -Bru trunk/locales.d/fr_abbrev.conf trunk+02-fr-locale/locales.d/fr_abbrev.conf
--- trunk/locales.d/fr_abbrev.conf	2017-01-12 19:24:03.926746418 +0100
+++ trunk+02-fr-locale/locales.d/fr_abbrev.conf	2017-01-20 07:51:07.61156 +0100
@@ -1,9 +1,6 @@
-#
-#   French Bible bookname abbreviations -- derived from the "Louis Segond 1910"
-#   Corrections & Contributions welcome
-#
-#  Dominique Corbex dom...@users.sf.net
-#
+# File creation: 2017-01-20
+# French translation for Sword
+# Provided by yvand , Cyrille , domcox  
 
 [Meta]
 Name=fr_abbrev
@@ -11,152 +8,471 @@
 Encoding=ISO8859-1
 
 [Text]
-Genesis=Ge
+# Old Testament* (39)
+# Genesis
+Genesis=Gen
+# Exodus
 Exodus=Ex
-Leviticus=Lé
-Numbers=No
-Deuteronomy=De
+# Leviticus
+Leviticus=Lév
+# Numbers
+Numbers=Nb
+# Deuteronomy
+Deuteronomy=Deut
+# Joshua
 Joshua=Jos
-Judges=Jg
-Ruth=Ru
-I Samuel=1 S
-II Samuel=2 S
-I Kings=1 R
-II Kings=2 R
-I Chronicles=1 Ch
-II Chronicles=2 Ch
-Ezra=Esd
-Nehemiah=Né
-Esther=Est
+# Judges
+Judges=Jug
+# Ruth
+Ruth=Ruth
+# I Samuel
+I Samuel=1 Sam
+# II Samuel
+II Samuel=2 Sam
+# I Kings
+I Kings=1 Rois
+# II Kings
+II Kings=2 Rois
+# I Chronicles
+I Chronicles=1 Chr
+# II Chronicles
+II Chronicles=2 Chr
+# Ezra
+Ezra=Esdr
+# Nehemiah
+Nehemiah=Néh
+# Esther
+Esther=Esth
+# Job
 Job=Job
+# Psalms
 Psalms=Ps
-Proverbs=Pr
-Ecclesiastes=Ec
-Song of Solomon=Ca
-Isaiah=Es
-Jeremiah=Jé
-Lamentations=La
-Ezekiel=Ez
-Daniel=Da
+# Proverbs
+Proverbs=Prov
+# Ecclesiastes
+Ecclesiastes=Eccl
+# Song of Solomon
+Song of Solomon=Cant
+# Isaiah
+Isaiah=És
+# Jeremiah
+Jeremiah=Jér
+# Lamentations
+Lamentations=Lam
+# Ezekiel
+Ezekiel=Éz
+# Daniel
+Daniel=Dan
+# Hosea
 Hosea=Os
-Joel=Joë
+# Joel
+Joel=Joël
+# Amos
 Amos=Am
-Obadiah=Ab
+# Obadiah
+Obadiah=Abd
+# Jonah
 Jonah=Jon
-Micah=Mi
-Nahum=Na
-Habakkuk=Ha
-Zephaniah=So
-Haggai=Ag
-Zechariah=Za
+# Micah
+Micah=Mich
+# Nahum
+Nahum=Nah
+# Habakkuk
+Habakkuk=Hab
+# Zephaniah
+Zephaniah=Soph
+# Haggai
+Haggai=Agg
+# Zechariah
+Zechariah=Zach
+# Malachi
 Malachi=Mal
+
+# New Testament* (27)
+# Matthew
 Matthew=Mt
-Mark=Mc
-Luke=Lu
-John=Jn
-Acts=Ac
-Romans=Ro
-I Corinthians=1 Co
-II Corinthians=2 Co
-Galatians=Ga
-Ephesians=Ep
-Philippians=Ph
+# Mark
+Mark=Marc
+# Luke
+Luke=Luc
+# John
+John=Jean
+# Acts
+Acts=Act
+# Romans
+Romans=Rom
+# I Corinthians
+I Corinthians=1 Cor
+# II Corinthians
+II Corinthians=2 Cor
+# Galatians
+Galatians=Gal
+# Ephesians
+Ephesians=Éph
+# Philippians
+Philippians=Php
+# Colossians
 Colossians=Col
+# I Thessalonians
 I Thessalonians=1 Th
+# II Thessalonians
 II Thessalonians=2 Th
-I Timothy=1 Ti
-II Timothy=2 Ti
-Titus=Tit
+# I Timothy
+I Timothy=1 Tim
+# II Timothy
+II Timothy=2 Tim
+# Titus
+Titus=Tite
+# Philemon
 Philemon=Phm
-Hebrews=Hé
-James=Ja
-I Peter=1 Pi
-II Peter=2 Pi
+# Hebrews
+Hebrews=Hébr
+# James
+James=Jacq
+# I Peter
+I Peter=1 P
+# II Peter
+II Peter=2 P
+# I John
 I John=1 Jn
+# II John
 II John=2 Jn
+# III John
 III John=3 Jn
-Jude=Jud
-Revelation of John=Ap
+# Jude
+Jude=Jude
+# Revelation of John
+Revelation of John=Apoc
 
-[Book Abbrevs]
+# Apocrypha/Deuterocanon* (22)
+# Tobit
+Tobit=Tob
+# Judith
+Judith=Jdt
+# Esther (Greek)
+Esther (Greek)=Estgrec
+# Additions to Esther
+Additions to Esther=AddEst
+# Wisdom
+Wisdom=Sag
+# Sirach (Prologue)
+Sirach (Prologue)=PrSir
+# Sirach
+Sirach=Sir
+# Baruch
+Baruch=Bar
+# Epistle of Jeremiah
+Epistle of Jeremiah=LtJr
+# Daniel (Greek)
+Daniel (Greek)=Dangrec
+# Additions to Daniel
+Additions to Daniel=AddDan
+# Prayer of Azariah
+Prayer of Azariah=PrAzar
+# Susanna
+Susanna=Suz
+# Bel and the Dragon
+Bel and the Dragon=Bel
+# I Maccabees
+I Maccabees=1 M
+# II Maccabees
+II Maccabees=2 M
+# III Maccabees
+III Maccabees=3 M
+# IV Maccabees
+IV Maccabees=4 M
+# Prayer of Manasses
+Prayer of Manasses=Man
+# I Esdras
+I Esdras=3 Esd
+# II Esdras
+II Esdras=4 Esd
+# Additional Psalm
+Additional Psalm=Ps 151
+
+# Rahlfs' LXX* (2)
+# Odes
+Odes=Odes
+# Psalms of Solomon
+Psalms of Solomon=Ps Sal
+
+# Rahlfs' variant books* (6)
+# Joshua Codex Alexandrinus
+Joshua Codex Alexandrinus=JosA
+# Judges Codex Vaticanus
+Judges Codex Vatic

Re: [sword-devel] Release Wrapup

[Dominique Corbex]

Please find attached a new patch for adding
mappings to the French versification .h files.

Tested and works as expected.

I already sent a patch before, but changes were
not merged into svn.


Dominique
-- 
domcox 


On Sat, 21 Jan 2017 12:58:43 -0800 (PST)
David Haslam  wrote:

> Where are we up to with supporting the three new av11ns for French Bibles
> that Dominique documented?
> 
> If we're not about to release SWORD 2.0 anytime soon, what's preventing
> releasing an interim SWORD 1.8 (or even SWORD 1.7.3) with the new av11ns?
> 
> I mean, right now, we can't even test osis2mod.exe and specify one of these
> with the -v option.
> 
> David
> 


Seulement dans trunk+01-fr-mappings/include: #canon_calvin.h#
diff -Bru trunk/include/canon_calvin.h trunk+01-fr-mappings/include/canon_calvin.h
--- trunk/include/canon_calvin.h	2017-01-12 19:24:04.894746447 +0100
+++ trunk+01-fr-mappings/include/canon_calvin.h	2017-01-23 20:58:34.002953297 +0100
@@ -3,7 +3,7 @@
  *  canon_calvin.h -	Versification data for French Bibles de Genève
  *  (Bibles de Genève, Épée, Martin, Ostervald)
  *
- * $Id: canon_calvin.h 2015-08-22 10:53:22 domcox $
+ *  $Id$
  *
  * Copyright 1998-2013 CrossWire Bible Society (http://www.crosswire.org)
  *	CrossWire Bible Society
@@ -289,6 +289,107 @@
   27, 21
 };
 
+unsigned char mappings_calvin[] = {
+0,
+4,   13,  1,   0,   12,  16,  0,
+4,   13,  2,   0,   13,  1,   0,
+4,   30,  1,   0,   29,  40,  0,
+4,   30,  2,   0,   30,  1,   0,
+9,   20,  43,  0,   20,  42,  0,
+9,   24,  1,   0,   23,  29,  0,
+9,   24,  2,   0,   24,  1,   0,
+11,  22,  44,  0,   22,  43,  0,
+18,  39,  1,   0,   38,  39,  0,
+18,  39,  4,   0,   39,  1,   0,
+18,  39,  34,  0,   40,  1,   0,
+18,  40,  1,   0,   40,  6,   0,
+18,  40,  20,  0,   41,  1,   0,
+18,  41,  1,   0,   41,  10,  0,
+19,  3,   2,   0,   3,   1,   0,
+19,  4,   2,   0,   4,   1,   0,
+19,  5,   2,   0,   5,   1,   0,
+19,  6,   2,   0,   6,   1,   0,
+19,  7,   2,   0,   7,   1,   0,
+19,  8,   2,   0,   8,   1,   0,
+19,  9,   2,   0,   9,   1,   0,
+19,  12,  2,   0,   12,  1,   0,
+19,  18,  2,   0,   18,  1,   0,
+19,  19,  2,   0,   19,  1,   0,
+19,  20,  2,   0,   20,  1,   0,
+19,  21,  2,   0,   21,  1,   0,
+19,  22,  2,   0,   22,  1,   0,
+19,  30,  2,   0,   30,  1,   0,
+19,  31,  2,   0,   31,  1,   0,
+19,  34,  2,   0,   34,  1,   0,
+19,  36,  2,   0,   36,  1,   0,
+19,  38,  2,   0,   38,  1,   0,
+19,  39,  2,   0,   39,  1,   0,
+19,  40,  2,   0,   40,  1,   0,
+19,  41,  2,   0,   41,  1,   0,
+19,  42,  2,   0,   42,  1,   0,
+19,  44,  2,   0,   44,  1,   0,
+19,  45,  2,   0,   45,  1,   0,
+19,  46,  2,   0,   46,  1,   0,
+19,  47,  2,   0,   47,  1,   0,
+19,  48,  2,   0,   48,  1,   0,
+19,  49,  2,   0,   49,  1,   0,
+19,  51,  2,   0,   51,  1,   0,
+19,  51,  3,   0,   51,  1,   0,
+19,  52,  2,   0,   52,  1,   0,
+19,  52,  3,   0,   52,  1,   0,
+19,  53,  2,   0,   53,  1,   0,
+19,  54,  3,   0,   54,  1,   0,
+19,  55,  2,   0,   55,  1,   0,
+19,  56,  2,   0,   56,  1,   0,
+19,  57,  2,   0,   57,  1,   0,
+19,  58,  2,   0,   58,  1,   0,
+19,  59,  2,   0,   59,  1,   0,
+19,  60,  2,   0,   60,  1,   0,
+19,  60,  3,   0,   60,  1,   0,
+19,  61,  2,   0,   61,  1,   0,
+19,  62,  2,   0,   62,  1,   0,
+19,  63,  2,   0,   63,  1,   0,
+19,  64,  2,   0,   64,  1,   0,
+19,  65,  2,   0,   65,  1,   0,
+19,  67,  2,   0,   67,  1,   0,
+19,  68,  2,   0,   68,  1,   0,
+19,  69,  2,   0,   69,  1,   0,
+19,  70,  2,   0,   70,  1,   0,
+19,  75,  2,   0,   75,  1,   0,
+19,  76,  2,   0,   76,  1,   0,
+19,  77,  2,   0,   77,  1,   0,
+19,  80,  2,   0,   80,  1,   0,
+19,  81,  2,   0,   81,  1,   0,
+19,  83,  2,   0,   83,  1,   0,
+19,  84,  2,   0,   84,  1,   0,
+19,  85,  2,   0,   85,  1,   0,
+19,  88,  2,   0,   88,  1,   0,
+19,  89,  2,   0,   89,  1,   0,
+19,  92,  2,   0,   92,  1,   0,
+19,  102, 2,   0,   102, 1,   0,
+19,  108, 2,   0,   108, 1,   0,
+19,  140, 2,   0,   140, 1,   0,
+19,  142, 2,   0,   142, 1,   0,
+21,  12,  1,   0,   11,  9,   0,
+21,  12,  3,   0,   12,  1,   0,
+23,  8,   23,  0,   9,   1,   0,
+23,  9,   1,   0,   9,   2,   0,
+26,  21,  1,   0,   20,  45,  0,
+26,  21,  6,   0,   21,  1,   0,
+28,  12,  1,   0,   11,  12,  0,
+28,  12,  2,   0,   12,  1,   0,
+32,  2,   1,   0,   1,   17,  0,
+32,  2,   2,   0,   2,   1,   0,
+41,  9,   51,  0,   9,   50,  0,
+41,  10,  53,  0,   10,  52,  0,
+44,  19,  40,  0,   19,  41,  0,
+45,  3,   23,  0,   3,   24,  0,
+46,  3,   22,  0,   3,   23,  0,
+64,  1,   15,  0,   1,   14,  0,
+66,  12,  18,

Re: [sword-devel] Release Wrapup

[David Haslam]

Where are we up to with supporting the three new av11ns for French Bibles
that Dominique documented?

If we're not about to release SWORD 2.0 anytime soon, what's preventing
releasing an interim SWORD 1.8 (or even SWORD 1.7.3) with the new av11ns?

I mean, right now, we can't even test osis2mod.exe and specify one of these
with the -v option.

David







--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Release-Wrapup-tp4656501p4656645.html
Sent from the SWORD Dev mailing list archive at Nabble.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] Release Wrapup

[Konstantin Maslyuk]

I still suggest to have full versification definition with mappings and all 
related information in a single file. 

JSword format isn't good for me because of it is divided to two files and CSV 
format is not enough serious for long term.

http://www.ccel.org/refsys/refsys.html is good for me.

Also i will support your decision, Troy.


Blessings.

-Исходное сообщение-
От: "Troy A. Griffitts" 
Отправлено: ‎22.‎10.‎2016 6:48
Кому: "SWORD Developers' Collaboration Forum" 
Тема: [sword-devel] Release Wrapup

Hey guys,

I know our free time all comes in spurts and often not in sync with each 
other, but I'd like to try to push these final things to completion 
which need attention to wrap up this next release.

Thanks to everyone who have reported bugs here and the bug tracker and 
who have submitted patches and updates.  I will work on resolving these 
bugs quickly as well as being sure updated translations which have been 
submitted are applied.

The French versifications which were submitted by domcox and bundled up 
by refdoc I believe were committed a few months back, but we need to be 
sure.  There were some questioned posted on the list recently.  Can we 
confirm or deny we have the latest in trunk?

Versification mapping questions are still outstanding. Костя, DM, you 
both have written the mapping code for our C++ and Java libraries 
respectively.  You both seem to have different ways to record the 
mapping between v11n systems.  Is there one definition format we can use 
moving forward?  Can you open a discussion about this?  It would be 
really nice to define mappings once, put them in version control and 
then write a utility which can read these files and produce what each of 
you need to function-- if you cannot optimally read this one definition 
directly from your code.  Before we go too much further down the road 
here, it would be nice to discuss this now.

We might still have some outstanding issues with IBR contributed 
patches.  I believe we rolled back a commit in osis2mod which may have 
fixed one or more issues with the reports from IBR and thus eliminating 
the need for the IBR patches, but I am not sure.  We need to review this.

Finally, in the spirit of our push toward 2.0, I will continue to 
standardize another set of method names and possibly rename a class or 
two.  As always, the old method names will be marked at deprecated so 
you will receive warnings, but they will not be removed so as not to 
break any frontend code.  When 2.0 is finally released, all deprecated 
methods and class names will be removed.


These are the issue I plan to work on over the next few days and I would 
so appreciate your collaboration to help bring this long overdue release 
to light.  If there are issue which you feel need immediate attention 
beyond these, please bring them up to remind me.  We probably need new 
threads about each of these items, individually, so I'd ask that you not 
reply to this thread regarding any of these individual items, but start 
a thread with an appropriate subject.

Thanks for sharing in work together.  May God bless our efforts to bring 
this release to fruition,

Troy


___
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] Release Wrapup

[Troy A. Griffitts]

Hi David,

Thanks for the wiki page.  No, we're not about to release 2.0. The 
purpose of 2.0 has been a more intuitive API, including regular 
camelCase naming of API methods.  We've been slowly working toward this 
for a number of years, attempting to not breaking API compatibility with 
older frontends by leaving the old names around but adding a deprecated 
flag to them to produce warnings.  When we do finally release 2.0, all 
deprecated methods will be removed and we will break API compatibility.  
Each .x release, we normalize a few more methods, deprecating the old 
names.  I only mentioned it because frontend developers might get new 
warnings in their code if they are using any of soon to be newly 
deprecated methods.


Thanks for asking,

Troy


On 10/22/2016 03:11 AM, David Haslam wrote:

Hi Troy,

Some time back, I added a placeholder in this wiki page.

https://crosswire.org/wiki/Alternate_Versification#1.8.0

Should I change that from 1.8.0 to 2.0 ?

Once the new version is released, I will list all the new av11ns in this
section of the page.
Are there any others besides the three French ones from domcox?

Best regards,

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Release-Wrapup-tp4656501p4656504.html
Sent from the SWORD Dev mailing list archive at Nabble.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



___
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] Release Wrapup

[David Haslam]

Hi Troy,

Some time back, I added a placeholder in this wiki page.

https://crosswire.org/wiki/Alternate_Versification#1.8.0

Should I change that from 1.8.0 to 2.0 ?

Once the new version is released, I will list all the new av11ns in this
section of the page.
Are there any others besides the three French ones from domcox?

Best regards,

David



--
View this message in context: 
http://sword-dev.350566.n4.nabble.com/Release-Wrapup-tp4656501p4656504.html
Sent from the SWORD Dev mailing list archive at Nabble.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

[sword-devel] Release Wrapup

[Troy A. Griffitts]

Hey guys,

I know our free time all comes in spurts and often not in sync with each 
other, but I'd like to try to push these final things to completion 
which need attention to wrap up this next release.


Thanks to everyone who have reported bugs here and the bug tracker and 
who have submitted patches and updates.  I will work on resolving these 
bugs quickly as well as being sure updated translations which have been 
submitted are applied.


The French versifications which were submitted by domcox and bundled up 
by refdoc I believe were committed a few months back, but we need to be 
sure.  There were some questioned posted on the list recently.  Can we 
confirm or deny we have the latest in trunk?


Versification mapping questions are still outstanding. Костя, DM, you 
both have written the mapping code for our C++ and Java libraries 
respectively.  You both seem to have different ways to record the 
mapping between v11n systems.  Is there one definition format we can use 
moving forward?  Can you open a discussion about this?  It would be 
really nice to define mappings once, put them in version control and 
then write a utility which can read these files and produce what each of 
you need to function-- if you cannot optimally read this one definition 
directly from your code.  Before we go too much further down the road 
here, it would be nice to discuss this now.


We might still have some outstanding issues with IBR contributed 
patches.  I believe we rolled back a commit in osis2mod which may have 
fixed one or more issues with the reports from IBR and thus eliminating 
the need for the IBR patches, but I am not sure.  We need to review this.


Finally, in the spirit of our push toward 2.0, I will continue to 
standardize another set of method names and possibly rename a class or 
two.  As always, the old method names will be marked at deprecated so 
you will receive warnings, but they will not be removed so as not to 
break any frontend code.  When 2.0 is finally released, all deprecated 
methods and class names will be removed.



These are the issue I plan to work on over the next few days and I would 
so appreciate your collaboration to help bring this long overdue release 
to light.  If there are issue which you feel need immediate attention 
beyond these, please bring them up to remind me.  We probably need new 
threads about each of these items, individually, so I'd ask that you not 
reply to this thread regarding any of these individual items, but start 
a thread with an appropriate subject.


Thanks for sharing in work together.  May God bless our efforts to bring 
this release to fruition,


Troy


___
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