Lynn,
Thanks for the report. Most of this stuff won't be fixed for the
release of BibleCS. A few comments below.
> * ESV search finds "Jesus" in 2 Sam 1:1, Jonah 1:1, and Malachi
> 1:1. I think these are "hits" from the notes (opening of chapter)
> rather than the actual Bible te
Looks like quite a few improvements. Good work.
Some comments/notes/problems (some may be related to ESV markup)
* ESV search finds "Jesus" in 2 Sam 1:1, Jonah 1:1, and Malachi
1:1. I think these are "hits" from the notes (opening of chapter)
rather than the actual Bible text. Is this inte
Paul,
I started to make some changes for you. First, I forced AnsiString
for the ambiguity error:
SWBuf origText = Trim(AnsiString(clickText.c_str())).c_str();
Then I came to the second error and see this line:
ListKey tmpVerseList =
DefaultVSKey->ParseVerseList(WideStringToUTF8(free
Troy and Chris,
I got the latest BibleCS from SVN and tried to compile it with CB6.
Here are the 4verrors I got:
(1) [C++ Error] mainfrm.cpp(1717): E2015 Ambiguity between '_fastcall
Sysutils::Trim(const System::AnsiString)' and '_fastcall
Sysutils::Trim(const System::WideString)'
(2) [C++ Error]
Barry,
sword should be able to parse them all. Our verse parser handles
pretty crazy stuff. You can use tests/parsekey or utilities/vs2osisref
We have a simple web form to vs2osisref up at:
http://crosswire.org/study/examples/parsevs.jsp
Hope this helps,
-Troy.
Barry Drake w
