<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;
mso-fareast-language:EN-GB;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang="EN-GB" link="blue" vlink="purple">The code I use for mapping across translations is in our tools repo here. It does a reasonable job on same language literal Bibles and isolates to word alignment algorithm to a single method so it can be adjusted without understanding all the other code in there.<br><br><a href="http://crosswire.org/svn/sword-tools/trunk/migratetags/">http://crosswire.org/svn/sword-tools/trunk/migratetags/</a><br><br>I think I have a newer matching algorithm I've used for adding strongs to the Tyndale Greek New Testament and to NA28, which I still need to check in, but the shell to do the work is generally there. I'll try to checkin any updates soon.<br><br>For what it's worth,<br><br>Troy<br><br><br><br><div class="gmail_quote">On April 13, 2019 6:12:28 AM MST, Jamie <araj@critos.co.uk> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">David H is correct that David Instone Brewer has worked on this kind of thing. I won’t attempt to characterise how things stand at present, nor the approach he has adopted, since I may be out of date, and may end up misrepresenting things. I did notice this thread, though, and have drawn it to his attention, so I imagine he’ll be in touch (he’s not answering my emails currently so I assume he may be out for the day).<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Jamie<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p><p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> David Haslam [mailto:dfhdfh@protonmail.com] <br><b>Sent:</b> 13 April 2019 13:37<br><b>To:</b> SWORD Developers' Collaboration Forum <sword-devel@crosswire.org><br><b>Subject:</b> Re: [sword-devel] Mapping Strongs numbers to translations that do not come with Strongs support<o:p></o:p></span></p><p class="MsoNormal"><o:p> </o:p></p><div><p class="MsoNormal">Further stuff written by memory from my hospital bed:<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">I myself developed a worksheet based editing environment so that Vince LaRue has been able to start the big task of manually adding Strong’s to the Spanish RV1865 (modern orthography) Source Text. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">The WIP is in a shared folder in my Box account. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">The pre-&-postprocessing uses bespoke TextPipe filters. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">But there’s one more gain in the worksheet WPL environment. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Providing the WPL worksheet includes a column with line numbers, the text can be sorted on the Word column. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">This facilitated adding Strong’s to multiple instances of the same Spanish word (ignoring context). The original textual order can be restored by a sort on the line numbers column. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Much more detail is involved in how (eg) punctuation is dealt with and preserved. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Even so, the trial run on 2JN was a success and Vince has since done MAT 1-11 or more when I last looked at the progress. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Aside: The same environment also facilitated adding markup for \wj_...\wj*<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Best regards,<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">David<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div id="protonmail_mobile_signature_block"><p class="MsoNormal">Sent from ProtonMail Mobile<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><p class="MsoNormal">On Sat, Apr 13, 2019 at 13:16, <a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a> <<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>> wrote:<o:p></o:p></p><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">I have been thinking about this for years but not done much yet. <br><br>I think there are a bunch of steps which could make this a machine driven process<br><br>1) use verse,mapping from KJV or other already tagged texts (Synodal) and drop on each verse the relevant numbers<br><br>2) use names of places and people to tag those first<br><br>3) use dictionaries to align further<br><br>4) check by hand, but use any realignment to further inform not yet checked verses<br><br><br>Sent from my mobile. Please forgive shortness, typos and weird autocorrects.<o:p></o:p></p><div><p class="MsoNormal"><br><br>-------- Original Message --------<br>Subject: Re: [sword-devel] Mapping Strongs numbers to translations that do not come with Strongs support<br>From: Michael H <br>To: SWORD Developers' Collaboration Forum <br>CC: <br><br><br><o:p></o:p></p><blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><div><div><p class="MsoNormal" style="margin-bottom:18.0pt"><span style="font-size:18.0pt;font-family:"Garamond",serif">The Unfolding Word Team is using Autographa for its "alignment" process (which means adding strongs numbers, but they also are working on fixing stray words into a common (UnfoldingWord) versification across languages, if I understand chat room babble. <br><br><a href="https://forum.ccbt.bible/t/gl-ugnt-alignment-process/101">https://forum.ccbt.bible/t/gl-ugnt-alignment-process/101</a><br><br><a href="http://www.autographa.com/about/">http://www.autographa.com/about/</a><br><br><o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><div><div><p class="MsoNormal">On Sat, Apr 13, 2019 at 6:52 AM Tobias Klein <<a href="mailto:contact@tklein.info">contact@tklein.info</a>> wrote:<o:p></o:p></p></div><blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><div><p>Hi David,<o:p></o:p></p><p>Cool! Thanks for the hint! Do you happen to know whether that software used by the STEP team is open source?<o:p></o:p></p><p>Best regards,<br>Tobias<o:p></o:p></p><div><p class="MsoNormal">On 13.04.19 13:00, David Haslam wrote:<o:p></o:p></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal">This was done already by the Tyndale STEP team for adding Strong’s Numbers to the ESV. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">They used bespoke software followed by manual adjustments. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Ask David Instone-Brewer for details. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Best regards,<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">David<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div id="gmail-m_-3725700820176316755gmail-m_-3264344759559549830protonmail_mobile_signature_block"><p class="MsoNormal">Sent from ProtonMail Mobile<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><p class="MsoNormal">On Sat, Apr 13, 2019 at 11:33, Tobias Klein <<a href="mailto:contact@tklein.info">contact@tklein.info</a>> wrote: <o:p></o:p></p><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><p class="MsoNormal">Hi,<br><br>I have an idea that I would like to run by you guys.<br><br>Would it be possible to automatically map Strongs numbers to<br>translations that do not come with Strongs support?<br><br>The approach would be like this:<br>- Take a translation that comes with Strongs numbers<br>- Map each word (and Strongs number) to a corresponding word in the<br>target translation, by using a regular dictionary<br><br>There may be some validation / manual checking needed when there is not<br>a clear match between a word in the source translation and the target<br>translation.<br>Furthermore, this would probably only work with pairs of translations<br>that are both aiming to be literal. In that case the order of words<br>would be very similar and would increase chances of mapping<br>words/Strongs correctly.<br><br>What do you think?<br>I'd be very happy to see Strongs mapped to German translations<br>specifically. But it could technically even work for English/English<br>translation mapping.<br><br>Have a nice weekend!<br><br>Best regards,<br>Tobias<br><br><br>_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page<o:p></o:p></p></blockquote><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><p class="MsoNormal"><o:p> </o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><o:p></o:p></pre><pre><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><o:p></o:p></pre><pre>Instructions to unsubscribe/change your settings at above page<o:p></o:p></pre></blockquote></div><p class="MsoNormal">_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page<o:p></o:p></p></blockquote></div></blockquote></div></blockquote><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div></div></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>