<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I'm happy to read on the wiki the addition of the new Catholic v11n.
Do you have an idea when the 1.8.1 version will be released?<br>
I give you a proposition of text for the wiki (need correction of my
English!) because I can't access it, (there is also a mistake in<b>
</b>"sig<b>n</b>ificant" in the wiki):<br>
<br>
<tt><i>Catholic variants, base on the Catholic liturgical
translations (based itself on the neovulgate), of which two
correspond to existing Catholic versifications:</i></tt><tt><i><br>
</i></tt><tt><i><br>
</i></tt><tt><i>Catholic_lit – like Catholic but with significant
differences, Esther with 10 chapters</i></tt><tt><i><br>
</i></tt><tt><i>Catholic2_lit – like Catholic2 but with
significant differences, Esther with 16 chapters</i></tt><tt><i><br>
</i></tt><tt><i>Catholic3_lit – a new Catholic versification
corresponding to Catholic1, but where Esther's alternate
versification is integrated into the current 10 chapters, to
allow a better reading. This means that the verses of the
chapters numbered with letters are integrated into the current
10 chapters of Esther.</i></tt><b><i><br>
</i></b><br>
Maybe when the 1.8.1 version will be released, It should be added to
point out that Catholic and Catholic2 v11n are obsolete, in favour
of the new Catholic_lit...<br>
<br>
Best regards, Br Cyrille<br>
<b><i></i></b><br>
<div class="moz-cite-prefix">Le 29/12/2017 à 17:52, DM Smith a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:7AD73BBE-02CA-499B-B8CF-D9CEBC172DF0@crosswire.org">
<pre wrap="">My concern at the time was that once we’ve a v11n that has been released and modules have been built with it we really can’t change it. People keep modules around long after we’ve updated or obsoleted them. We want them to be able to update their front-end without losing functionality of the modules that they have. If we had never released a module with them then they could be fixed.
If I understand Cyrille has addressed those concerns by essentially creating a v2 for two of them using new names. The third is novel and wasn’t an issue.
If so, then I don’t see any problems with adding them.
In Him,
DM
</pre>
<blockquote type="cite">
<pre wrap="">On Dec 29, 2017, at 11:44 AM, Cyrille <a class="moz-txt-link-rfc2396E" href="mailto:lafricain79@gmail.com"><lafricain79@gmail.com></a> wrote:
This is my first post:
Le 05/06/2017 à 09:18, Cyrille a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
Working with Catholic bibles I realized that there were some errors in
the versifications currently proposed.
I found for all those in which I could verify the following errors:
Ps 101 8 verses, not 9
Job 25 6 verses not 14
Job 27 23 verses not 24
CT 4 16 verses not 17
Zach 4 14 verses not 16
These proposed corrections, moreover, correspond to th canon.h file
I don't if I need to open an new issue on github or no?
Best regards, Br Cyrille
</pre>
</blockquote>
<pre wrap="">After it I created 3 new v11n. Two the same as the existing, with the
corrections, and with a new name, and a new one that add the extra
versification of Esther in the 10 chapters.
Nothing really complicated, if you agree, just to add it to sources :)
_______________________________________________
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>
<pre wrap="">
_______________________________________________
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>
</body>
</html>