<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Ok, then if I understand well, we work on the "full" text, and then
with some scripts we remove some parts of the full text. <br>
Can you list this parts?<br>
<br>
<div class="moz-cite-prefix">Le 25/04/2023 à 21:57, David Haslam a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:WZ-XIuiGaSj0WawXb5PX4x5yEkNeAlvjSoDMqlPBViQP0ae7KAYyGfE-JosgdYxo9DMbFIBz0o-k4umL6jKRGY2xPuN1CmWp-8dhGIp1QrA=@protonmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div style="font-family: Arial, sans-serif; font-size: 14px;">To
answer your question briefly.</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;">Please
note that such XML files having ".full" as part of the filename
contain [informational] elements that are removed before making
a module.<br>
ie. The processed source files for the KJV project have more
parts to the filename.</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;">Aside:
Although DM had his own method for removing these elements, I
made a simple <i>bespoke</i> TextPipe filter solely for this
purpose.</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br>
</div>
<div class="protonmail_signature_block" style="font-family: Arial,
sans-serif; font-size: 14px;">
<div class="protonmail_signature_block-user"> Best regards,<br>
<br>
David </div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br>
</div>
<div class="protonmail_signature_block-proton"> Sent with <a
target="_blank" href="https://proton.me/" rel="noopener
noreferrer" moz-do-not-send="true">Proton Mail</a> secure
email. </div>
</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br>
</div>
<div class="protonmail_quote"> ------- Original Message -------<br>
On Tuesday, April 25th, 2023 at 8:21 PM, Fr Cyrille
<a class="moz-txt-link-rfc2396E" href="mailto:fr.cyrille@tiberiade.be"><fr.cyrille@tiberiade.be></a> wrote:<br>
<br>
<blockquote class="protonmail_quote" type="cite"> Sincerely
thank you David for all this information.<br>
I will now put all this on git, and open issues for what you
suggest.<br>
On the Kjv2.9 we have the kjv.xml and the kjvfull.xml? Which
one is the right one?<br>
I can see also the kjv2.10a version. This version does not
matter?<br>
<br>
<div class="moz-cite-prefix">Le 25/04/2023 à 15:01, David
Haslam a écrit :<br>
</div>
<blockquote type="cite">
<div style="font-family: Arial, sans-serif; font-size:
14px;">Dear Fr. Cyrille, dear Troy, </div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">As regards, the KJV source text managed by DM, it's
no secret that he stored all of them in his <a
title="personal area"
href="https://www.crosswire.org/~dmsmith/"
rel="noreferrer nofollow noopener" target="_blank"
moz-do-not-send="true">personal area</a> on the
CrossWire server.</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">The files used for KJV release 2.9 that preceded
Troy's emergency update (2.10.2) are stored here:</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><span><a class="moz-txt-link-freetext"
href="https://www.crosswire.org/~dmsmith/kjv2011/kjv2.9/"
rel="noreferrer nofollow noopener" target="_blank"
moz-do-not-send="true">https://www.crosswire.org/~dmsmith/kjv2011/kjv2.9/</a></span><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">cf. From the latest kjv.conf</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><span style="font-family: Menlo, Consolas,
"Courier New", monospace; font-size: 9pt;
line-height: normal;">Version=2.10.2</span>
<div><span style="font-family: Menlo, Consolas,
"Courier New", monospace; font-size: 9pt;
line-height: normal;">History_2.10.2=Fixed errant
article Strong's markup (2021-04-04)</span></div>
<div><span style="font-family: Menlo, Consolas,
"Courier New", monospace; font-size: 9pt;
line-height: normal;">History_2.9=Added markup to
notes. Improved markup of Selah. (2016-01-21)</span></div>
<div><span style="font-family: Menlo, Consolas,
"Courier New", monospace; font-size: 9pt;
line-height: normal;"><br>
</span></div>
<span></span></div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">NB. The verse where Troy fixed the Strong's markup
error is Romans 3:36</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><span><span><span style="background-color:rgb(255,
255,
255);font-size:9pt;line-height:normal;display:inline
!important">Aside: IIRC, the Strong's markup error
in Romans 3:36 had already been corrected (evidently
it was in the pipeline for the next release by DM,
even before Troy took action).</span></span></span><br>
<br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">There's a lot more that could be said, and a lot of
subsequent exchanges took place between myself and DM from
January 2016 to June 2021, but none of them resulted in
preparing a new release from the OSIS XML that I had been
processing by means of various <i>bespoke</i> TextPipe
filters. </div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">Throughout that period, I had continued to work on
enhancing the KJV source file, testing it in-house using
Xiphos on my old Windows 7 x64 PC as eXperimental module
KJVX.</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">NB. Last July, I discovered <span style="color:
rgb(37, 37, 37); font-family: sans-serif; text-align:
left; background-color: rgb(255, 255, 255); display:
inline !important;">multiple implementation bugs in my
change to render pilcrows as normal black text even when
these are within text marked for red letters as words of
Jesus. See the following line in the table for <b>Version
2.11</b> being prepared.</span></div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><span style="color: rgb(37, 37, 37); font-family:
sans-serif; text-align: left; background-color: rgb(255,
255, 255); display: inline !important;"><span
style="background-color:rgb(255, 255,
255);display:inline !important"><br>
</span></span></div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><span style="color: rgb(37, 37, 37); font-family:
sans-serif; text-align: left; background-color: rgb(255,
255, 255); display: inline !important;"><span
style="background-color:rgb(255, 255,
255);display:inline !important">Changed red ¶ to black
(i.e. within text marked as "words of Jesus")<a
style="color:rgb(6, 69,
173);background:none;font-size:11.6667px;white-space:nowrap"
href="https://wiki.crosswire.org/CrossWire_KJV#cite_note-57"
rel="noreferrer nofollow noopener" target="_blank"
moz-do-not-send="true">[2]</a></span></span></div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">Notes on various thoughts and ideas are recorded in
DM's wiki user page:</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><span><a class="moz-txt-link-freetext"
href="https://wiki.crosswire.org/User:Dmsmith/KJV_2.6"
rel="noreferrer nofollow noopener" target="_blank"
moz-do-not-send="true">https://wiki.crosswire.org/User:Dmsmith/KJV_2.6</a></span><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">Last updated 2016-02-20</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">Many more proposals and a detailed revision history
are recorded in this wiki page:</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><span><a class="moz-txt-link-freetext"
href="https://wiki.crosswire.org/CrossWire_KJV"
rel="noreferrer nofollow noopener" target="_blank"
moz-do-not-send="true">https://wiki.crosswire.org/CrossWire_KJV</a></span><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;">Last updated 2022-07-28</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;" class="protonmail_signature_block">
<div class="protonmail_signature_block-user"><span
style="font-size: 9pt; line-height: normal;">NB. My
old Win7 PC is currently in a state of non-use, as I
started to see hard drive errors reported first in
August 2022 with the result that I've not taken it out
of sleep mode since last September. I've not begun to
formulate a plan to tackle this problem, though it's
worth recording that it's one of the PCs in my
Carbonite account that has online backup using
Carbonite Safe (albeit it's shown as "out-of-date" in
every backup status email I receive <span
style="background-color:rgb(255, 255,
255);display:inline !important">monthly<span> </span></span>from
Carbonite).</span></div>
<div class="protonmail_signature_block-user"><br>
</div>
<div class="protonmail_signature_block-user">Since my wife
died in October 2020, I've not found it so easy to
maintain the same level of technical activities as a
CrossWire volunteer that I had attained during the years
preceding.</div>
<div class="protonmail_signature_block-user"><br>
</div>
<div class="protonmail_signature_block-user">I trust that
this reply helps to clarify the state of art for going
forward with future updates to our flagship KJV module.
It's not ideal in regard to modern systems for version
control, but the KJV project began well before GitHub
was a gleam in anyone's eyes.</div>
<div class="protonmail_signature_block-user"><br>
</div>
<div class="protonmail_signature_block-user"> Best
regards,<br>
<br>
David </div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div class="protonmail_signature_block-proton"> Sent with
<a rel="noreferrer nofollow noopener"
href="https://proton.me/" target="_blank"
moz-do-not-send="true">Proton Mail</a> secure email. </div>
</div>
<div style="font-family: Arial, sans-serif; font-size:
14px;"><br>
</div>
<div class="protonmail_quote"> ------- Original Message
-------<br>
On Tuesday, April 25th, 2023 at 12:33 PM, Fr Cyrille <a
href="mailto:fr.cyrille@tiberiade.be"
class="moz-txt-link-rfc2396E" rel="noreferrer nofollow
noopener" target="_blank" moz-do-not-send="true"><fr.cyrille@tiberiade.be></a>
wrote:<br>
<br>
<blockquote type="cite" class="protonmail_quote"> <br>
<br>
<div class="moz-cite-prefix">Le 25/04/2023 à 12:03,
David Haslam a écrit :<br>
</div>
<blockquote type="cite">
<div dir="auto">NB. Troy’s emergency update to the KJV
was made using IMP2VS after exporting the text using
MOD2IMP.</div>
<div dir="auto"><br>
</div>
<div dir="auto">It’s not the OSIS XML source text that
DM Smith was managing.</div>
</blockquote>
<span class="HwtZe" lang="en"><span class="jCAhz ChMk0b"><span
class="ryNqvb">Okay David, we're not going to redo
the discussion, we had agreed to provide the
community with a text, it seemed to be Troy's
because it's the last one that had modifications.</span></span>
<span class="jCAhz ChMk0b"><span class="ryNqvb">It
could be another one, but then we'll have to know
what modifications Troy made to it.</span></span><span
class="jCAhz"><span class="ryNqvb"> </span></span><span
class="jCAhz ChMk0b"><span class="ryNqvb">I hope we
can get this project moving forward before we're
all dead <img style="width: 3ex; height: 3ex;
min-width: 20px; min-height: 20px; display:
inline-block; margin: 0 .15em .2ex; line-height:
normal; vertical-align: middle"
class="joypixels" alt="😂"
src="https://cdn.jsdelivr.net/gh/joypixels/emoji-assets@v7.0.0/png/64/1f602.png"
moz-do-not-send="true" width="20" height="20"
align="middle"><br>
How much energy have we spent in endless
discussion just to be able to contribute to this
module.<br>
</span></span><span class="jCAhz"><span
class="ryNqvb"></span></span></span>
<blockquote type="cite">
<div dir="auto"><br>
</div>
<div dir="auto">I’m still in contact with DM.</div>
</blockquote>
<br>
<span class="HwtZe" lang="en"><span class="jCAhz ChMk0b"><span
class="ryNqvb">Glad to hear it, even if he doesn't
seem to be in touch with us anymore.</span></span></span>
<blockquote type="cite">
<div dir="auto"><br>
</div>
<div dir="auto">David</div>
<div><br>
</div>
<div id="protonmail_mobile_signature_block">
<div>Sent from Proton Mail for iOS</div>
</div>
<div><br>
</div>
<div><br>
</div>
On Tue, Apr 25, 2023 at 10:40, Fr Cyrille <<a
target="_blank" rel="noreferrer nofollow noopener"
class="" href="mailto:On Tue, Apr 25, 2023 at 10:40,
Fr Cyrille <<a href=" moz-do-not-send="true">fr.cyrille@tiberiade.be</a>>
wrote:
<blockquote type="cite" class="protonmail_quote"> <br>
<br>
<div class="moz-cite-prefix">Le 24/04/2023 à 21:11,
Troy A. Griffitts a écrit :<br>
</div>
<blockquote type="cite">
<div dir="auto">Hi guys. The NASB is done. I have
the scripts checked in and the source data from
Lockman on our server. The problem I have had is
that I haven't had time to figure out how to
insert my scripts to run to convert the data
into your wonderful module team automation.<br>
<br>
Just to restate my position on module data
processing, and not to squelch the wonderful
work you guys are doing.<br>
<br>
My position is that I hold that checking in the
results of source data converted to OSIS files
is very bad practice.<br>
<br>
In my mind, the only thing we should be checking
in is the script to convert the data from the
source to the intermediate OSIS. We should never
check-in the OSIS. EVER. It is an intermediate
step between the source data and a SWORD module.<br>
<br>
All the module work ends with a process which
takes publisher data converts to OSIS and
results in a SWORD module.<br>
<br>
The conversion process can be reproduced
automatically.<br>
<br>
The steps taken for the conversion are all
clearly defined in the script-- it is not a
mystery how the conversion happened.<br>
<br>
I believe we lose these two very important
things in the way we currently work.<br>
<br>
One more negative aspect in checking in our
converted OSIS data is that we appear to be a
source for other software, when it would be
better that other software go to the actual
source for that data and bypass any conversion
errors we introduced.<br>
<br>
Anyway, my point is not to mandate this
automated flow from source data to module; only
to interject that I believe this is the ideal to
work toward.<br>
<br>
I have done the extra work to make this happen
with the modules I have done, NA28, NASB, LXXM,
etc., and I would at least like the automation
pipeline you have to give me the option to call
out to a script to produce the OSIS, instead of
download it from some location.<br>
<br>
Troy<br>
<br>
</div>
</blockquote>
Thank you Troy for all this informations. I
understand your point of view very well and it seems
relevant. Now as long as it remains a goal to wait
for, I validate it. But if you take into account the
real thing, it's a lot of work. First of all, on my
side, in the case where we have access to a source,
<span class="HwtZe" lang="en"><span class="jCAhz
ChMk0b"><span class="ryNqvb">my scripts are damn
tinkered that I would be ashamed to share
them! But it's one of my project.</span></span></span><br>
As for the sources you say we seem to offer, I take
responsibility for them. Firstly because it's much
less work for me once the source is either lost or
no longer maintained to make corrections when a
problem is detected. Look at the complication it has
made since Chris left to find acceptable sources for
a multitude of modules. I only do this in cases
where the source is really hard to find or is in a
state that is too complicated for conversion. The
case of the BYZ and TR module is an example. I take
care of the text, since nobody else does it anymore
and I have made some pretty serious corrections.<br>
If you're worried about it, you don't have to assume
it's Crosswire, but me.<br>
As for NASB, as you don't have time, could you in
this case share the osis file, at least to allow us
to have a nice updated text, and when you are ready
or someone can help you then add the options you ask
for to the module production script.<br>
Isn't it more important to have a bible with a
corrected text?<br>
You don't mention the KJV, could you send me your
corrected file so we can work on it? An user has
sent several errors to be corrected to the sword
list, I am afraid that it gets lost in the
messages...<br>
<br>
Thanks for the great work.<br>
<blockquote type="cite">
<div dir="auto"><br>
<br>
On April 24, 2023 11:35:01 AM MST, Fr Cyrille <a
target="_blank" rel="noreferrer nofollow
noopener"
href="mailto:fr.cyrille@tiberiade.be"
class="moz-txt-link-rfc2396E"
moz-do-not-send="true"><fr.cyrille@tiberiade.be></a>
wrote:<br>
><br>
><br>
><br>
>-------- Message transféré --------<br>
>Sujet : [sword-devel] KJV and NASB updates<br>
>Date : Mon, 17 Apr 2023 00:36:25 +0200<br>
>De : Fr Cyrille <a target="_blank"
rel="noreferrer nofollow noopener"
href="mailto:fr.cyrille@tiberiade.be"
class="moz-txt-link-rfc2396E"
moz-do-not-send="true"><fr.cyrille@tiberiade.be></a><br>
>Répondre à : SWORD Developers' Collaboration
Forum <a target="_blank" rel="noreferrer
nofollow noopener"
href="mailto:sword-devel@crosswire.org"
class="moz-txt-link-rfc2396E"
moz-do-not-send="true"><sword-devel@crosswire.org></a><br>
>Pour : SWORD Developers' Collaboration Forum
<a target="_blank" rel="noreferrer nofollow
noopener"
href="mailto:sword-devel@crosswire.org"
class="moz-txt-link-rfc2396E"
moz-do-not-send="true"><sword-devel@crosswire.org></a><br>
><br>
><br>
><br>
>Hello Troy,<br>
>2 things we could make progress on, which I
would like to remind you of:<br>
><br>
> * NASB update still pending<br>
> * Moving KJV to our gitlab (you have the
latest version)<br>
><br>
><br>
>Would this be possible?<br>
><br>
>Br Cyrille<br>
<div class="k9mail-signature">-- <br>
Sent from my Android device with K-9 Mail.
Please excuse my brevity.</div>
</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">_______________________________________________
modules mailing list
<a target="_blank" rel="noreferrer nofollow noopener" href="mailto:modules@crosswire.org" class="moz-txt-link-abbreviated moz-txt-link-freetext" moz-do-not-send="true">modules@crosswire.org</a>
<a target="_blank" rel="noreferrer nofollow noopener" href="http://www.crosswire.org/mailman/listinfo/modules" class="moz-txt-link-freetext" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/modules</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre">_______________________________________________
modules mailing list
<a target="_blank" rel="noreferrer nofollow noopener" class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:modules@crosswire.org" moz-do-not-send="true">modules@crosswire.org</a>
<a target="_blank" rel="noreferrer nofollow noopener" class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/modules" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/modules</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre">_______________________________________________
modules mailing list
<a href="mailto:modules@crosswire.org" class="moz-txt-link-abbreviated moz-txt-link-freetext" rel="noreferrer nofollow noopener" target="_blank" moz-do-not-send="true">modules@crosswire.org</a>
<a href="http://www.crosswire.org/mailman/listinfo/modules" class="moz-txt-link-freetext" rel="noreferrer nofollow noopener" target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/modules</a>
</pre>
</blockquote>
<br>
</blockquote>
<br>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
modules mailing list
<a class="moz-txt-link-abbreviated" href="mailto:modules@crosswire.org">modules@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/modules">http://www.crosswire.org/mailman/listinfo/modules</a>
</pre>
</blockquote>
<br>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>