search

omarkerr / and-bible

Automatically exported from code.google.com/p/and-bible
0 stars 0 forks source link

Strong numbers missed in some chapters RusVZh #61

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Download RusVZh module from Crosswire.
2.Enable Strong numbers in settings.
3.Open Mat. 1.1.
4.Strong numbers are exist.
5.Open Col. 1.1.
6.Strong numbers does not exist.

What is the expected output? What do you see instead?
Strong numbers must be available everywhere in module. In Xiphos all Strong 
numbers are exist.

What version of the product are you using? On what operating system?
And Bible 0.5.07. HTC Desire. Android 2.3.3 (CyanogenMod).

Original issue reported on code.google.com by cepreu.m...@gmail.com on 8 Aug 2011 at 5:33

GoogleCodeExporter commented 9 years ago 
I too observed the problem in Colossians, with And Bible 1.6.0 in Android 4.0

The mystery is why ONLY missing from Colossians?
Is there some subtle module element that is misparsed by JSword and/or And 
Bible?

Needs checking in Bible Desktop, to see if any other JSword front-end has this 
issue.

Original comment by DFH...@gmail.com on 9 Dec 2012 at 1:33

GoogleCodeExporter commented 9 years ago 
Bible Desktop does NOT have the problem in Colossians, so it's not a JSword 
issue per se.

Original comment by DFH...@gmail.com on 9 Dec 2012 at 1:36

GoogleCodeExporter commented 9 years ago 
It's a subtle GBF markup issue!!!

In Colossians, the <WG....> elements all have a space between WG and the 
Strong's reference number.

Simplest solution would be to rebuild this module, though the fact that other 
front-ends can cope with the looser GBF syntax is an argument for making And 
Bible follow-suit.

Original comment by DFH...@gmail.com on 9 Dec 2012 at 2:24

GoogleCodeExporter commented 9 years ago 
According to http://www.ebible.org/bible/gbf.htm

the tag should not have a space.

Strong’s Greek Number <WGnnn> Ordinal number of Greek lexicon entry for 
previous word. (Optional)

Hence there is a case for raising a module issue on CrossWire JIRA.

Original comment by DFH...@gmail.com on 9 Dec 2012 at 2:39

GoogleCodeExporter commented 9 years ago 
Done!

http://www.crosswire.org/tracker/browse/MOD-227

Original comment by DFH...@gmail.com on 9 Dec 2012 at 2:45

GoogleCodeExporter commented 9 years ago 
Rebuilding the module works. 

 Used mod2imp to export the full text to an IMP file.
 Edited the IMP file to remove the spurious spaces.
 Used imp2vs to rebuild the module.
 Edited the conf file for version 1.1 and added history properties.

Our chief module maintainer could readily do likewise.

I have tested the rebuild version in And Bible
Colossians now displays Strong's OK.

Original comment by DFH...@gmail.com on 9 Dec 2012 at 4:24

GoogleCodeExporter commented 9 years ago 
This was a module issue.

Original comment by mjden...@gmail.com on 15 Mar 2014 at 9:04