Text Reference Notation
#1
Posted 30 August 2006 - 01:30 PM
Shouldn't it be possible for Accordance to be able to handle this kind of reference? Obviously I don't understand all of what is involved, but it seems like it wouldn't take too many lines of code to get this functionality. It's not a big deal, but I just find that I fight with it on a regular basis.
Thanks for considering this request!
-Ryan
#2
Posted 30 August 2006 - 04:30 PM
#3
Posted 30 August 2006 - 05:38 PM
Therefore you can enter 1 John 2John and you get the contents of both books
but if you enter 1 John 2 John Accordance cannot know whether you mean 1 John ch 2 or all of both books
so, unless we were to require a semicolon before a new book name, we have to continue to require a space between the book number and name, after the first reference.
OakTree Software
#4
Posted 12 September 2006 - 06:13 PM
Wouldn't it be possible to allow the "1 John" notation if the user includes semicolons? Accordance could simply "assume" that the number referred to the book and not the chapter whenever it is preceded by a semi-colon. This would still allow for using a space as a reference divider whenever a user chose to do that, in which case the user would be required to use the "1John" notation so that Accordance doesn't get confused, but it would also allow easy importation of lists of text references that are separated by a semi-colon and include the standard "1 John" notation.
Do my thoughts make sense? Perhaps a few examples will aid in clarification:
1 John 3:5; 2 John 1; 2 Cor. 3:11
(Accordance would accept this and understand the notation because of the use by the user of the semi-colons.)
1John 3:5 2John 1 2Cor. 3:11
(Accordance would accept this and understand the notation just like it does now. Semi-colons are absent, but there are no spaces between book number and book name, so there is no confusion.)
1 John 3:5 2 John 1 2 Cor. 3:11
(Accordance would have a problem here and would pop up an error box indicating that there was ambiguity just like it already does.)
In conclusion, unless there is some other factor I haven't considered, it seems that this suggestion would add a valuable feature, but would not add any significant problems. What do you think?
Thanks again,
Ryan
#5
Posted 12 September 2006 - 08:45 PM
1 John 3:5; 2 John 1; 2 Cor. 3:11
is interpreted as 1John ch 3 v5 and ch 2, followed by John ch 1 and ch 2 followed by an unknown book Cor.
OakTree Software
#6
Posted 13 September 2006 - 01:50 PM
Do you think it would be worthwhile to add another character that could be optionally used as a book separator? Perhaps '|' or something?
I notice that when I copy/paste a CR (or is it LF... or CR/LF... I can't keep them straight) separated list of text references into the Accordance search window, Accordance is kind enough to replace the CR's (or LF's or whatever) into semi-colons so that the entire list is readable in the window. This is fine except that then I have to go through and look for any notations that are incorrect and remove the spaces between the book and the book number, or else Accordance gives me an error. Am I the only one who does this on occasion?
Perhaps Accordance could even have an option added so that I can choose whether I want the CR's to be replaced by semi-colons...
Anyway, these are some of my thoughts. The current system just seems somewhat counter intuitive, and doesn't accommodate the standard way of referencing book titles, so I was looking for a solution. Please pardon my persistence!
-Ryan
#7
Posted 13 September 2006 - 11:31 PM
I can sympathize. I've hand-edited many sets of reference lists from Accordance because they did not conform to style guides, mainly inserting spaces after numbers but also changing the actual abbreviations.
I would have to say, though, that adding another character would not be optimal (as I'm sure you agree). I'd prefer for Accordance to look ahead beyond any number after a semicolon to see if in fact it is "going up a level" or is actually another book reference. Easier said than done, of course, but that's really the proper way to resolve those kinds of ambiguities.
J. P.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users










