<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’d like to have Troy and Peter’s guidance on this. It is both a software and a module management issue. Back in the day, we knew this was likely to happen.<div class=""><br class=""></div><div class="">I’m still gathering stats. It is a slow process. I think it should help inform a decision. The upshot is that there are thousands of downloads of these three modules since they have been introduced. Some are more popular than others. Details to follow.<br class=""><div class=""><br class=""></div><div class="">The question is how to go forward. One way is to break backward compatibility. The other is to try to create a reasonable migration path. (Which is what I recommend.)</div><div class=""><br class=""></div><div class="">From an engineering perspective, we can have any number of versifications in the engine and they can have any name. However, we’ve been reluctant to add versifications, especially if they are one offs. So far versification names are a blend of A-Za-z0-9, I don’t know if there are other restrictions. It seems to follow C variable naming restrictions.</div><div class=""><br class=""></div><div class="">Things to consider when updating a module’s conf.</div><div class="">MinimumVersion. When we add a new versification, it is tied to a particular release. This means that new module potentially won’t be available until the SWORD engine is released (any day now….) and the front-end is updated.</div><div class=""><br class=""></div><div class="">Obsoletes. For a module to obsolete another, it needs a different [Name] and have Obsoletes. It probably should have a different Description (old JSword bug, long since fixed, doesn’t like it when two modules have the same Description).</div><div class=""><br class=""></div><div class="">Versification. It should give the appropriate v11n.</div><div class=""><br class=""></div><div class="">DM</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 9, 2017, at 11:13 AM, Cyrille <<a href="mailto:lafricain79@gmail.com" class="">lafricain79@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Not a lot! And Konnym doesn't have (not yet) the Old Testament. I
manage it...<br class="">
Then if you prefer to write a new v11n, I can do it. But what name
to give it? And I would to write 2 v11n, one for esther 10 and one
for Esther 16.<br class="">
A name can be CatholicEs10, and CatholicEs16?<br class="">
<br class="">
<div class="moz-cite-prefix">Le 09/06/2017 à 15:46, DM Smith a
écrit :<br class="">
</div>
<blockquote cite="mid:FEEA0D5C-0344-48A6-A7B5-2BF3E7A814FB@crosswire.org" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
On the CrossWire server the following are in the main repository:
<div class="">
<div style="margin: 0px; font-size: 18px; line-height: normal;
font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures:
no-common-ligatures" class="">konnym.conf:Versification=Catholic2</span></div>
<div style="margin: 0px; font-size: 18px; line-height: normal;
font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures:
no-common-ligatures" class="">porcap.conf:Versification=Catholic</span></div>
<div style="margin: 0px; font-size: 18px; line-height: normal;
font-family: Menlo; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures:
no-common-ligatures" class="">slostritar.conf:Versification=Catholic</span></div>
<div class=""><span style="font-variant-ligatures:
no-common-ligatures" class=""><br class="">
</span></div>
<div class="">Checking the download stats for these. Will get back with
the results.</div>
<div class=""><br class="">
</div>
<div class="">In Him,</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Jun 9, 2017, at 10:37 AM, Cyrille <<a moz-do-not-send="true" href="mailto:lafricain79@gmail.com" class="">lafricain79@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi,<br class="">
What the solution proposed? Is it possible to know
exactly how modules<br class="">
are compiled with the Catholic and Catholic2? I'm
interesting to know it...<br class="">
<br class="">
Le 06/06/2017 à 14:50, DM Smith a écrit :<br class="">
<blockquote type="cite" class="">If an existing v11n
changes, all modules released by it will have to be
re-released with the update and all front-ends will
have to be recompiled with it. JSword will need to
change too and front-ends based upon it, also.<br class="">
<br class="">
The reason is simple the index file for a testament is
an indexed array with each verse in the v11n having a
predetermined index.<br class="">
<br class="">
If no modules have been released with it, it is a
fairly safe change. The risk are older front-ends with
the wrong tables.<br class="">
<br class="">
Issuing a v2 (simply another v11n with a new name) and
deprecating the older probably is a safer change.<br class="">
<br class="">
In Him,<br class="">
</blockquote>
<br class="">
<br class="">
_______________________________________________<br class="">
sword-devel mailing list: <a moz-do-not-send="true" href="mailto:sword-devel@crosswire.org" class="">sword-devel@crosswire.org</a><br class="">
<a moz-do-not-send="true" href="http://www.crosswire.org/mailman/listinfo/sword-devel" class="">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="">
Instructions to unsubscribe/change your settings at
above page</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" class="">sword-devel@crosswire.org</a><br class=""><a href="http://www.crosswire.org/mailman/listinfo/sword-devel" class="">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br class="">Instructions to unsubscribe/change your settings at above page</div></blockquote></div><br class=""></div></div></body></html>