<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks for the links, Michael. I'll have a look at Autographa.<br>
</p>
<p>Best regards,<br>
Tobias<br>
</p>
<div class="moz-cite-prefix">On 13.04.19 14:03, Michael H wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ9hia-r-0ShRCF2GupPwjg5C9v91tNzvH7=jUK2i15P0K+xug@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:garamond,serif;font-size:large">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"
moz-do-not-send="true">https://forum.ccbt.bible/t/gl-ugnt-alignment-process/101</a><br>
<br>
<a href="http://www.autographa.com/about/"
moz-do-not-send="true">http://www.autographa.com/about/</a><br>
<br>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Apr 13, 2019 at 6:52
AM Tobias Klein <<a href="mailto:contact@tklein.info"
target="_blank" moz-do-not-send="true">contact@tklein.info</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Hi David,</p>
<p>Cool! Thanks for the hint! Do you happen to know whether
that software used by the STEP team is open source?</p>
<p>Best regards,<br>
Tobias<br>
</p>
<div
class="gmail-m_-3725700820176316755gmail-m_-3264344759559549830moz-cite-prefix">On
13.04.19 13:00, David Haslam wrote:<br>
</div>
<blockquote type="cite">
<div>This was done already by the Tyndale STEP team for
adding Strong’s Numbers to the ESV. </div>
<div><br>
</div>
<div>They used bespoke software followed by manual
adjustments. </div>
<div><br>
</div>
<div>Ask David Instone-Brewer for details. </div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>David</div>
<div><br>
</div>
<div
id="gmail-m_-3725700820176316755gmail-m_-3264344759559549830protonmail_mobile_signature_block">Sent
from ProtonMail Mobile</div>
<div><br>
</div>
<div><br>
</div>
On Sat, Apr 13, 2019 at 11:33, Tobias Klein <<a
href="mailto:contact@tklein.info" target="_blank"
moz-do-not-send="true">contact@tklein.info</a>>
wrote:
<blockquote
class="gmail-m_-3725700820176316755gmail-m_-3264344759559549830protonmail_quote"
type="cite"> 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
class="gmail-m_-3725700820176316755gmail-m_-3264344759559549830moz-txt-link-abbreviated"
href="mailto:sword-devel@crosswire.org"
target="_blank" moz-do-not-send="true">sword-devel@crosswire.org</a><br>
<a
class="gmail-m_-3725700820176316755gmail-m_-3264344759559549830moz-txt-link-freetext"
href="http://www.crosswire.org/mailman/listinfo/sword-devel"
target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at
above page<br>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<br>
<fieldset
class="gmail-m_-3725700820176316755gmail-m_-3264344759559549830mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_-3725700820176316755gmail-m_-3264344759559549830moz-quote-pre">_______________________________________________
sword-devel mailing list: <a class="gmail-m_-3725700820176316755gmail-m_-3264344759559549830moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org" target="_blank" moz-do-not-send="true">sword-devel@crosswire.org</a>
<a class="gmail-m_-3725700820176316755gmail-m_-3264344759559549830moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
</div>
_______________________________________________<br>
sword-devel mailing list: <a
href="mailto:sword-devel@crosswire.org" target="_blank"
moz-do-not-send="true">sword-devel@crosswire.org</a><br>
<a
href="http://www.crosswire.org/mailman/listinfo/sword-devel"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></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://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>
</body>
</html>