[sword-devel] 1.5.5 Strong's number bug

[Troy A. Griffitts]

Steve,
	Noted and reproduced your bug.  Thanks.  I'll get right on it.  There 
is special code that says, "Hey, when I'm doing a word lookup, see if it 
is surrounded by <> or (); if so, strip those off cuz we're probably a 
strongs number."  Well, problem is, the RTF control returns the current 
word as "<0776>."  Strange, but we can take care of it.  It's definitely 
a windows frontend thing.  Thanks again for reporting it.

	-Troy.



Steve Tang wrote:
> Go to KJV & turn on Strong's number. E.g. in Gen 1:1, when you right click
> on <07225> and choose 'Dictionary Lookup', your chosen Hebrew dictionary
> show 07225, right? Try do the same at the end of the verse: <0776>.
> Instead of showing 0776, <0776>. comes up.
> 
> Go to verse 7 where there is '<07549>:', the same thing happens when
> there's is a colon after the right angle bracket. In verse 29, there's a
> semicolon like '<02233>;'.
> 
> On Wed, 23 Oct 2002, Martin Gruner wrote:
> 
> 
>>Date: Wed, 23 Oct 2002 15:10:31 +0200
>>From: Martin Gruner <mg.pub@gmx.net>
>>Reply-To: sword-devel@crosswire.org
>>To: sword-devel@crosswire.org
>>Subject: Re: [sword-devel] 1.5.5 Strong's number bug
>>
>>Steve, could you tell us more detailed what exactly is happening? I don't 
>>really understand what you wanted to point out.
>>
>>Martin
>>
>>
>>>Comma is fine now. But not period and semicolon.
>>>
>>>I made a Chinese module with Strong's numbers. And I don't know why. This
>>>funny thing also happens before Chinese marks like comma, period,
>>>semicolon, but not words, as if sword knows the difference between
>>>Chinese words and marks. My guess is that this 'problem' occurs in all
>>>languages.
>>>
>>>This goes away when I put spaces after '>'s.
>>>
>>>So my suggestion is: instead of hard code all possible punctuation marks
>>>in, we may need to just put spaces after the right angle brackets.
>>>
>>>If nobody volunteers, I can remake a KJV module. How do I upload a test
>>>module?
>>>
>>>Steve Tang...
>>
> 
> Steve Tang...
>