<style>
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and (-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
</style>
<div id="email-body">
<table id="email-wrap" align="center" border="0" cellpadding="0" cellspacing="0" style="background-color:#f0f0f0;color:#000000;width:100%;">
<tr valign="top">
<td id="email-page" style="padding:16px !important;">
<table align="center" border="0" cellpadding="0" cellspacing="0" style="background-color:#ffffff;border:1px solid #bbbbbb;color:#000000;width:100%;">
<tr valign="top">
<td bgcolor="#4d5c47" style="background-color:#4d5c47;color:#ffffcc;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;"><img src="http://www.crosswire.org/bugs/s/en_US-l73y3/783/14/_/jira-logo-scaled.png" alt="" style="vertical-align:top;" /></td>
</tr><tr valign="top">
<td id="email-banner" style="padding:32px 32px 0 32px;">
<table align="left" border="0" cellpadding="0" cellspacing="0" width="100%" style="width:100%;">
<tr valign="top">
<td style="color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;">
<img id="email-avatar" src="http://www.crosswire.org/bugs/secure/useravatar?avatarId=10062" alt="" height="48" width="48" border="0" align="left" style="padding:0;margin: 0 16px 16px 0;" />
<div id="email-action" style="padding: 0 0 8px 0;font-size:12px;line-height:18px;">
<a class="user-hover" rel="dmsmith" id="email_dmsmith" href="http://www.crosswire.org/bugs/secure/ViewProfile.jspa?name=dmsmith" style="color:#000000;">DM Smith</a>
commented on <img src="http://www.crosswire.org/bugs/images/icons/bug.gif" height="16" width="16" border="0" align="absmiddle" alt="Bug"> <a style='color:#000000;text-decoration:none;' href='http://www.crosswire.org/bugs/browse/JS-226'>JS-226</a>
</div>
<div id="email-summary" style="font-size:16px;line-height:20px;padding:2px 0 16px 0;">
<a style='color:#000000;text-decoration:none;' href='http://www.crosswire.org/bugs/browse/JS-226'><strong>Robinson's morphology is not indexed in JSword modules</strong></a>
</div>
</td>
</tr>
</table>
</td>
</tr>
<tr valign="top">
<td id="email-fields" style="padding:0 32px 32px 32px;">
<table border="0" cellpadding="0" cellspacing="0" style="padding:0;text-align:left;width:100%;" width="100%">
<tr valign="top">
<td id="email-gutter" style="width:64px;white-space:nowrap;"></td>
<td>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr valign="top">
<td colspan="2" style="color:#000000;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;padding:0 0 16px 0;width:100%;">
<div class="comment-block" style="background-color:#edf5ff;border:1px solid #dddddd;color:#000000;padding:12px;"><p>Looking at the code now. There's something about it that isn't quite right.</p>
<p>In the OT we don't have morphology codes that have semantic meaning. In fact, the codes (strongsMorph aka "thayers") that are used are placeholders for the future. We don't have a dictionary for those codes. I'd love it if David I-B, Daniel Owens and Chris Little would work together to come up with a meaningful code pattern that can be used. Chris has talked about a code that would not require an external dictionary. As long as we have a mapping from existing (robinson and "thayer") codes to the new one, I'll do the work in the KJV to update it.</p>
<p>But regarding the code, we should put the morph codes in to the searchable morph field regardless if they are Robinsons or strongsMorph.</p>
<p>The form of SN@MC (Strong's Number@Morph Code) is useful if the Morph Code has semantic meaning (as above).</p>
<p>The other thing, is that the lemma, morph and src attribute values form parallel arrays. Here are 3 examples from the upcoming KJV of the longest ones:<br/>
<w src="2 3 4 5" lemma="strong:G3956 strong:G3739 strong:G5100 strong:G302 tr:παν tr:ο tr:τι tr:αν" morph="robinson:A-ASN robinson:R-ASN robinson:X-ASN robinson:PRT">whatsoever</w><br/>
<w src="15 16 17 18" lemma="strong:G3588 strong:G4286 strong:G3588 strong:G740 tr:η tr:προθεσις tr:των tr:αρτων" morph="robinson:T-NSF robinson:N-NSF robinson:T-GPM robinson:N-GPM">the shewbread</w><br/>
<w src="10 13 14 15" lemma="strong:G3756 strong:G1519 strong:G3588 strong:G165 tr:ουκ tr:εις tr:τον tr:αιωνα" morph="robinson:PRT-N robinson:PREP robinson:T-ASM robinson:N-ASM">never</w></p>
<p>It is not a valid assumption that they always form parallel arrays. It took a lot of effort to clean up the KJV NT to make it so. Here is an example from the KJV OT:<br/>
<w morph="strongMorph:TH8799 strongMorph:TH8675 strongMorph:TH8686" lemma="strong:H05749 strong:H05749">What thing shall I take to witness</w></p>
<p>There's no reason to think other modules are error free. See an example from ABP here:<br/>
<a href="http://www.crosswire.org/tracker/browse/MOD-245">http://www.crosswire.org/tracker/browse/MOD-245</a><br/>
This has Strong's Numbers but they are pretty goofy.</p>
<p>So I think we should do the following:<br/>
Have one or more fields with SN, MC and SN@MC.</p>
<p>The construction of SN@MC needs to be best effort, pairing the first Strong's Number with the first morph code, the second with the second and so forth until no more pairs can be formed.</p>
<p>The question I have is do we really need more than one field if the codes are not overlapping?</p>
<p>And I wonder about the - in the code. I was under the impression that the - formed a word break. It seems to me that we need to normalize the code so that it can be searched well.</p>
<p>Similar question regarding @ does it get stripped out by Lucene? Do we need to protect it?</p>
<p>I'm inclined to say that the easiest path is 3 fields: strong:SN, morph:MC and lex:SN@MC.</p></div>
<div style="color:#505050;padding:4px 0 0 0;"> </div>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td><!-- End #email-page -->
</tr>
<tr valign="top">
<td style="color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:10px;line-height:14px;padding: 0 16px 16px 16px;text-align:center;">
This message is automatically generated by JIRA.<br />
If you think it was sent incorrectly, please contact your JIRA administrators<br />
For more information on JIRA, see: <a style='color:#000000;' href='http://www.atlassian.com/software/jira'>http://www.atlassian.com/software/jira</a>
</td>
</tr>
</table><!-- End #email-wrap -->
</div><!-- End #email-body -->