<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">Le 25/04/2023 à 02:06, Michael Johnson
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:163de461-ee84-b918-7fae-5ae9f17b17df@eBible.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">OK, Troy. I hear you saying that it
is not "broken", but working perfectly as designed. That is
actually worse, because if it were broken, there might be some
motivation to fix it. As it is, I have no hope that the World
English Bible Ecumenical Editions will ever be properly
displayed in any Sword software, at least as far as having both
versions of Daniel goes. That isn't important to you. I get
that. It is more important to me to preserve the versifications
of the original works than it is to support Sword, especially if
DAN and DAG are not allowed to coexist in the same Bible. Time
for a fork?<br>
</div>
</blockquote>
<br>
Hi Michael,<br>
I think there seems to be something inconsistent in your choice of a
Greek translation of Daniel alongside a translation from the Hebrew
(no disrespect in the word inconsistent I will explain). If you take
this option you should do so for all the OT books which all have a
Greek translation and a Hebrew text. That's why it seemed to me that
the choice of a versification that takes into account only the Greek
text was relevant. In Catholic translations in general, both the
Greek and the Hebrew are taken into account, i.e. if the Hebrew is
difficult, the Greek is taken into account. If one makes a
translation from the LXX only in this case it becomes a proper
translation, for example in French we have the translation of
Giguet. So I don't think anyone would be shocked to see a book of
Daniel translated from the Hebrew but adding the Greek passages, as
in most Catholic translations.<br>
Another aspect I'm thinking about is the book of Tobit, we have a
short text, and a long text so again we have to choose, one or the
other, often the Catholic translations add in notes the differences
between the two texts. This is what I did for the neo-Crampon-libre,
which takes into account the Vulgate, the short version in Greek and
the long version!<br>
In any case for the Catholic versification as you only have one file
for Daniel as for Esther, I have no hesitation to pass the id in DAN
and EST. Nothing inconsistent there.<br>
Maybe a solution for the web with DC, my idea would be to use
variant. I did this for the Greek NT. I "invented" a tag \var and
use it as second variant in the osis file. This can be great.<br>
<br>
David's idea is also interesting but much heavier. Besides, I've
been dreaming of an updated Catholic versification for some time...
In which case, if one day we add a versification proper to WEB we
could take advantage of it to correct the Catholic one.<br>
<br>
<br>
<br>
<br>
<blockquote type="cite"
cite="mid:163de461-ee84-b918-7fae-5ae9f17b17df@eBible.org"><br>
<div class="moz-cite-prefix">On 4/24/23 08:47, Troy A. Griffitts
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:92B24D9F-1F25-440C-81D9-CA3BE9FB8725@crosswire.org">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div dir="auto">😊<br>
<br>
I would obvious encourage the use of "well balanced" over
"broken".<br>
<br>
The use cases we need to solve are varied, but the typical
cases have to be priorities.<br>
<br>
1) Users lookup verses by reference, e.g., for Dan 3:7. What
should they get? Majority of users don't ask for the Greek or
Hebrew version of Daniel or even know about the difference.<br>
<br>
2) Users want to compare a verse across translations. This is
the primary motivator for defined versification schemes and
maps between them. e.g. when a user is reading Ps 10:1, and
ask to see it in an LXX translation, we need to show them
Ps.9.21.<br>
<br>
I understand the desire to let publishers flow their texts
however they want, and we should do better for the publishers,
but that is by far not the majority use case for users.</div>
<br>
<br>
<div class="gmail_quote">
<div dir="auto">On April 24, 2023 9:51:56 AM MST, Michael
Johnson <a class="moz-txt-link-rfc2396E"
href="mailto:Michael@eBible.org" moz-do-not-send="true"><Michael@eBible.org></a>
wrote:</div>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div class="moz-cite-prefix">Hi Br. Cyrille,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Actually, that work-around
might work for Catholic versification, but not for the
ecumenical versification of the WEB. That is because the
World English Bible contains both Daniel translated from
the Hebrew traditional text (DAN) and Daniel translated
from the Greek Septuagint (DAG). The USFM markup is
correct. The ability of the Sword Engine to interpret it
is broken.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 4/24/23 01:43, Fr Cyrille
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:60949844-1435-6677-4b47-f7e273cbc1d8@tiberiade.be">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
Hi Michael,<br>
THe problem is the same with xiphos.<br>
If you want your file readable with the Catholic
versification, you need to use the DAN \id in your usfm
file, and not \id DAG.<br>
It's not a front-end issue but an usfm issue.<br>
@Jon, you probably know, with Andbible in the list of the
bible books, the DC and accessible with the +.<br>
<br>
<div class="moz-cite-prefix">Le 23/04/2023 à 09:29,
Michael Johnson a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:25990721-5fc8-24e4-f4a6-59472ebc73a9@eBible.org">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<p>Hello, Jonathan.</p>
<p>WEB and WEBC indeed contain Daniel (Greek). However,
I don't know how to select a Sword Engine
versification that can cause the front ends (AndBible,
Bishop, Xiphos, etc.) to properly display Daniel
(Greek). They can display some fragments of Daniel
(Greek), like Susanna and Bel and the Dragon, but the
World English Bible isn't split up that way, and won't
be. Daniel (Greek) makes more sense when presented as
a whole. I'm not sure if this is possible to do within
the Sword ecosystem.</p>
<p>In the mean time, eBible.org epub files work well
with Google Books and Apple Books, among other epub
readers, no matter what their versification. You can
get to any chapter in about 3 taps. The Sword Engine
tries to force-fit every Bible translation into a
small set of predefined, hard-coded versification
schemes, none of which exactly match the World English
Bible. In fact, they don't exactly match a very high
percentage of Bible translations.<br>
</p>
<p><br>
</p>
On 4/22/23 19:36, you wrote:<br>
<blockquote type="cite"><br>
Name-> Jonathan Faust<br>
Email-> <a class="moz-txt-link-abbreviated
moz-txt-link-freetext"
href="mailto:jonfaust@tutanota.com"
moz-do-not-send="true">jonfaust@tutanota.com</a><br>
Subject-> AndBible WEBC Daniel<br>
Form URL-> <a class="moz-txt-link-freetext"
href="https://eBible.org/cgi-bin/contact.cgi"
moz-do-not-send="true">https://eBible.org/cgi-bin/contact.cgi</a><br>
Remote IP-> 172.69.204.168<br>
Hi there!<br>
<br>
Apologies if I'm mistaken, but I'm not seeing Daniel
(Greek) in my bible app. It looks like both the WEB
and WEBC contain Esther (Greek) but lack Daniel
(Greek). This would imply WEBC contains no translation
of Daniel. I see it on browser bible and in the EPUB.
Is this an issue with AndBible, the source WEB files,
or something else?<br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=UTF-8">
<title>signature</title>
<p><font color="#000000">Aloha,<br>
<b><big><i>Michael Johnson</i></big></b></font><b><br>
<font color="#000070"> 26 HIWALANI LOOP • MAKAWAO
HI 96768-8747</font></b><font color="#000070"> •
USA<br>
<a href="https://mljohnson.org/"
moz-do-not-send="true">mljohnson.org</a> • <a
href="https://eBible.org" moz-do-not-send="true">eBible.org</a>
• <a href="https://WorldEnglish.Bible"
moz-do-not-send="true">WorldEnglish.Bible</a> •
<a href="https://PNG.Bible" moz-do-not-send="true">PNG.Bible</a><br>
Signal/Telegram/WhatsApp/Telephone: +1
808-333-6921<br>
Skype: kahunapule • Telegram/Twitter: @kahunapule
• <a href="https://www.facebook.com/kahunapule"
moz-do-not-send="true">Facebook:
fb.me/kahunapule</a></font></p>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:sword-devel@crosswire.org" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:sword-devel@crosswire.org" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<p><br>
</p>
</blockquote>
</div>
<div dir="auto">
<div class="k9mail-signature">-- <br>
Sent from my Android device with K-9 Mail. Please excuse my
brevity.</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:sword-devel@crosswire.org" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://crosswire.org/mailman/listinfo/sword-devel" moz-do-not-send="true">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<p><br>
</p>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=UTF-8">
<title>signature</title>
<p><font color="#000000">Aloha,<br>
<b><big><i>Michael Johnson</i></big></b></font><b><br>
<font color="#000070"> 26 HIWALANI LOOP • MAKAWAO HI
96768-8747</font></b><font color="#000070"> • USA<br>
<a href="https://mljohnson.org/" moz-do-not-send="true">mljohnson.org</a>
• <a href="https://eBible.org" moz-do-not-send="true">eBible.org</a>
• <a href="https://WorldEnglish.Bible"
moz-do-not-send="true">WorldEnglish.Bible</a> • <a
href="https://PNG.Bible" moz-do-not-send="true">PNG.Bible</a><br>
Signal/Telegram/WhatsApp/Telephone: +1 808-333-6921<br>
Skype: kahunapule • Telegram/Twitter: @kahunapule • <a
href="https://www.facebook.com/kahunapule"
moz-do-not-send="true">Facebook: fb.me/kahunapule</a></font></p>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-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://crosswire.org/mailman/listinfo/sword-devel">http://crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
</pre>
</blockquote>
<br>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>