Tim has over-simplified the situation.
Other systems include different ways of abbreviating the books.
In the following, Am is an abbreviation which does not include the
end of the word,
while Jas (ie James) does include the end of the word, so it
shouldn't have a dot after it,
which results
I was somewhat amused by the sentence that reads, I'd suggest the following
is the best compromise between humans and people.
Notwithstanding, should spans of verse be punctuated by a hyphen or by the
ndash character?
cf. I came across a tip for MS-Word yesterday which claimed that the ndash
On Fri, Jun 18, 2010 at 8:37 AM, David Haslam d.has...@ukonline.co.uk wrote:
I was somewhat amused by the sentence that reads, I'd suggest the following
is the best compromise between humans and people.
Notwithstanding, should spans of verse be punctuated by a hyphen or by the
ndash
Perhaps more to the point for CrossWire developers, should we create a new
wiki page to address this subject?
Within David IB's examples, which of these are not valid references in
relation to our software?
Assuming we could [eventually] make use of any of these referenced biblical
texts within
Regarding what we accept currently, you can try experimenting with:
http://crosswire.org/study/examples/parsevs.jsp
We do have the ability to provide alternate versification schemes which
include other books (e.g., apoc.), or completely different book names
like a versification of Josephus or
Troy, This is great! Where's the source code for the reference parser?
As part of the Open Scriptures osis.py module for representing OSIS
identifier objects (osisID, osisRef, osisWork, etc), the next step is to
have a pluggable/extensible system for converting human-formatted references
into
The source code for the reference parser lives mostly in
src/keys/versekey.cpp:ParseVerseList in the sword source code.
Though it does work quite well, it has a number of problems and is very hard
to maintain/add new features to.
God Bless,
Ben
