<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>So, LXX is hard. Chris Little did a bit of research a while back
on editions of the Greek OT. Some of his hard work is available
here:</p>
<p><a class="moz-txt-link-freetext" href="https://crosswire.org/svn/sword-tools/trunk/versification/lxx_v11ns/">https://crosswire.org/svn/sword-tools/trunk/versification/lxx_v11ns/</a></p>
<p>There are all kinds of crazy things in there, including our of
order verse numbers (SWORD doesn't current support), more than one
text tradition of the same book:</p>
<p><a class="moz-txt-link-freetext" href="http://crosswire.org/study/bookdisplay.jsp?mod=LXXM">http://crosswire.org/study/bookdisplay.jsp?mod=LXXM</a></p>
<p>Notice in the index along the left JoshB and JoshA, JudgB and
JudgA, etc.</p>
<p>In the end, we decided the worst of all evils was simply to
settle on a superset LXX v11n that contains a place for
everything. The downside of this is that you may find a empty
verses (as David has found). Another downside is that we allow
the same content to be versified in different ways IN THE SAME
V11N depending on how the edition versifies it-- this makes it
very hard to build a true parallel display in the future. The
upside is that we can simply show most LXX editions the way they
were published, and that outweighed the downsides. If we ever
actually improve our mapping data to show LXX next to Masoretic
versification, we can consider breaking out the LXX into multiple
v11ns or some other solution (v11n exception in the .conf file has
been a consideration), but this hasn't had anyone really step up
to do all this work-- except for the hard work from Костя for
initial design and implementation of v11n mappings support and a
few initial mappings.</p>
<p>Anyway, that's the background and problems, with the path to
where we are today,</p>
<p>Troy</p>
<p> <br>
</p>
<br>
<div class="gmail_quote">On September 1, 2022 2:12:31 PM GMT+02:00,
domcox <a class="moz-txt-link-rfc2396E" href="mailto:dominique@corbex.org"><dominique@corbex.org></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex;
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre dir="auto" class="k9mail">
David Haslam <a class="moz-txt-link-rfc2396E" href="mailto:dfhdfh@protonmail.com"><dfhdfh@protonmail.com></a> writes:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Thanks Pierre,
For information on 1 Enoch, see <a href="https://en.wikipedia.org/wiki/Book_of_Enoch" class="moz-txt-link-freetext">https://en.wikipedia.org/wiki/Book_of_Enoch</a>
I now rather wonder why this book is even specified in the LXX versification?
</blockquote>
IMHO, 1 Enoch should not be specified in the LXX v11n.
I propose to remove it from the current v11n definition,
SWORD source file: include/canon_lxx.h
<div class="k9mail-signature">--
Dom<hr>sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a href="http://crosswire.org/mailman/listinfo/sword-devel" class="moz-txt-link-freetext">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</div></pre>
</blockquote>
</div>
</body>
</html>