<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 7/15/20 1:23 PM, Karl Kleinpaste
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:274fb28e-3b3a-ae31-9480-d6e5936047a5@kleinpaste.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 7/15/20 2:15 AM, Tobias Klein
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:166045f9-b90a-74a6-ae43-514efcc5a269@tklein.info">Since
we don't have the NAS Heb/Grk lexicons</blockquote>
<font face="FreeSerif"><br>
Actually, we (well, I) do...which is why I could explain your
difficulty, after all.<br>
<br>
I just moved them from my private repo to the Xiphos repo. Feel
free to refresh and install.<br>
<br>
Troy and I discussed making them available a little while ago,
but we never got to a concrete point. At least for now, they're
available there. Perhaps we'll decide to move them a different
repo sometime, but he may want to regenerate them as, say, TEI
rather than the ThML in which they're currently encoded.<br>
<br>
Normalization of NASB's references might still be a good idea,
but Lockman may well have something to say about that.</font></blockquote>
<p><font face="FreeSerif">Thank you! :) I didn't expect to get
additional dictionary modules when starting my original post on
this. I just installed them both and started looking around a
bit.<br>
</font></p>
<p><font face="FreeSerif">Normalization of the actual references in
the dictionary module would be one thing, but the search is
another thing I think. So for me the question is still whether a
search for "G5179" could yield results for both "G5179a" and
"G5179b" in case of the NASB. Independent of the specifics of a
translation a user probably just thinks "Strong's" and doesn't
even know about this feature of the NASB Strong's. Is there any
other translation out there that uses these special Strong's
keys?</font></p>
<p><font face="FreeSerif">I'm asking all these questions because I'm
currently working on a Strong's based dictionary view that
combines the display for multiple Strong's based modules in one
view. The "standard Strong's keys" are the common denominator
here (even though some use a variant with a 0 prefix in front of
the actual Strong's number). So in case of using the NASB it
would still be nice for the user to have the same kind of search
behavior as with any other of the Strong's enabled bible
modules.<br>
</font></p>
<p><font face="FreeSerif">Best regards,<br>
Tobias<br>
</font></p>
</body>
</html>