Joachim,<br>
Apparantly the problem was
with double entries in the original, improper form of the
modules. Once I removed the cache and installed the modules
again, things have started to be displayed properly. The updating
of the cache still remained puzzling. After removing the double
entries in the module (an occrrence of "Advocate, Counselor" once with
no data and a second time with data) Bibletime picked up that change in
the module, even though it had cached the data. However, when I
removed the commas from the file, it did not update that fact.
All of that was without changing the module version. I have only
found one public module where thie behavior may be occuring. In
the AmTract, the entry "Ashtoreth, plural Ash'taroth" does not appear
in Bibletime (it does appear in Gnomesword2, so the data must be there
somewhere). In that particular module, there are a number of
entries with a comma that do appear properly (such as "Arimathew, or
Ramah" or "Atonement, Day of" or "Avim, or Avites" and so on) but
Ashtoreth does not. I will make a bug report on SF based off of
this.<br>
<br>
--Greg<br><br><div><span class="gmail_quote">On 6/22/05, <b class="gmail_sendername">Joachim Ansorg</b> <<a href="mailto:nospam+bt-devel@joachim-ansorg.de">nospam+bt-devel@joachim-ansorg.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>thank you for your reports.<br><br>I don't know atm what the reason is for bug no. 1.<br>Please submit a bug report for that and if possible give a reference to a<br>public Sword module where this occurs so we can test that.
<br><br>> The second problem comes from when I attempt to install a version of the<br>> dictionary with no entries containing a comma. I went through all of the<br>> removal/uninstall procedures I could. First I just tried overwriting the
<br>> files related to the dictionary, but that did not affect that content that<br>> Bibletime has recorded for the dicitonary, it still has entries with commas<br>> in them, although there are none in the new form of the module. I then
<br>> tried using the Bibletime installer program to uninstall the problem<br>> modules and then install the new form. Once again, when I open Bibletime I<br>> see the entries with the commas in them listed, not the new version. When I
<br>> tested the new module in Gnomesword, just to be certain that the new form<br>> of the module does not have a comma in the name, it correctly loaded the<br>> new form of the module without the commas, but Bibletime seems to have
<br>> cached the data somewhere so that I always end up with entries containing<br>> commas for the two modules under question.<br><br>Right, BT caches the lexicon entries.<br>But if a module update (i.e. a different version number of it) is installed
<br>the lexicon cache is removed and recreated.<br>Did you change the version before you loaded te new module data?<br><br>The cache is in .kde/share/apps/bibletime/.<br><br>Joachim<br></blockquote></div><br>