JSword never had this problem. It has been well ahead of SWORD for many years
(on this).
As a reminder, JSword is not a port of SWORD. It is an independent
implementation. As such, how it handles Strong's numbers is entirely different.
On occasion, JSword differs from SWORD in a way that can on
I also added a further note:
# This is only available in SWORD version 1.7 or later. JSword will need to
catch up later.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/StrongsPadding-tp4651872p4651874.html
Sent from the SWORD Dev mailing list archive at Nabble.c
Done.
http://crosswire.org/wiki/DevTools:conf_Files#StrongsPadding
For the time being, I've not made this a new row in one of the existing
tables, though that might be sensible at a later date.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/StrongsPadding-tp4651
We have old logic in the heart of our lexicon/dictionary drivers which
try to detect if a key value is a Strongs number and then zero pad it
accordingly, if so. I've added recognition of a new .conf entry for
lexicon/dictionary modules:
StrongsPadding=true|false
So as not to break everything
