<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">See below:<br>
<br>
On 09/04/2015 01:43 AM, Karl Kleinpaste wrote:<br>
</div>
<blockquote cite="mid:55E983F1.6050800@kleinpaste.org" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">On 09/03/2015 07:09 PM, Kahunapule
Michael Johnson wrote:<br>
</div>
<blockquote cite="mid:55E8D33D.4060104@gmail.com" type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
<font face="FreeSerif">Please make sure you get a fresh copy
from the repository.</font></blockquote>
I always refresh immediately before such tests; such was the case
90 seconds before I wrote.<br>
<br>
<blockquote cite="mid:55E8D33D.4060104@gmail.com" type="cite">the
morphology tags have been stripped from this module for now.
Those may come back, later, if I have time to deal with all of
that.<br>
</blockquote>
?!?<br>
<br>
Why did you do that? As I wrote when first looking over grcTisch
(Wed 09:02pm), all you needed to fix the problem was to add
GlobalOptionFilter=OSISMorph in order to trigger the apps' ability
to switch it on and off in the engine, and (in Xiphos' case) to
provide for the needed separate subtext layer to hold it, apart
from Strong's, when switching it on.<br>
<br>
There's nothing "to deal with," you just have to configure it
properly. Literally a one-line .conf fix. I had already manually
added it to my local copy and seen that it would then be fine.<br>
</blockquote>
<br>
Thank you for that information. There are two things to deal with
right now, for me, other than what looks like a one-line .conf fix.
One is a steep learning curve of how morphology tags work with the
markup variations and the different applications and front ends.
Your assurance that everything was fine except for the .conf line is
helpful. I was concerned that there might be other, deeper issues
and an unending quagmire of tweaks. The other thing is that I don't
do one-line .conf fixes directly. I fix the process, not the .conf
file, and let the process generate the correct .conf file. This is
slower for one module. It is orders of magnitude faster for hundreds
of modules. This is not a really hard thing, but I'm currently only
fixing repository show-stopper items for launching the eBible.org
repository. The rest will have to wait until the repository is
officially on line.<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
<p><font color="#000000">Aloha,<br>
<i>Kahunapule Michael Johnson</i></font></p>
<table cellpadding="7" cellspacing="0">
<tbody>
<tr>
<td style="background: rgb(255, 255, 0)"><font
color="#000000"><b>MICHAEL JOHNSON<br>
PO BOX 881143<br>
PUKALANI HI 96788-1143</b><br>
USA</font></td>
<td style="background: rgb(0, 255, 255)"><font
color="#000000">
<a href="http://eBible.org">eBible.org</a><br>
<a href="http://MLJohnson.org">MLJohnson.org</a><br>
Mobile: +1 <b>808-333-6921</b><br>
Skype: kahunapule</font></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>