Questions re:new Help on Bible book abbreviations (ATTN: Eli?}
In Help and https://www.logos.com/support/windows/L4/abbreviations
- Isn't Greek Esther recognized?
- Isn't the most common abbreviation for Ad Ps Ps 151?
- Isn't the book Odes in the plural ... and why don't I find it in Factbook
- In canonical order doesn't Laodiceans come after the NT?
- Pss 152-155 appear to be missing - noted only because Psalms of Solomon are present.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
Comments
-
- The default verse map does support Greek Esther.*
- Both "Ad Ps" and "Ps 151" are recognized as abbreviations for that Psalm.
- Odes can be referred to by "Ode" or "Odes". I don't know why it isn't in Factbook. It should be.
- In canonical order, yes, but in the weird order of the Bible data type, no.**
- The default Bible data type has everything necessary to support the NRSV and some editions of the LXX. Psalms of Solomon (18 Psalms) are included in the Logos LXX, but Pss 152-155 are not. (I blame history.)
* That web page we referenced hasn't been updated since 2010. I'll see if there are any trees I can bark up loud enough to get it updated. [:)]
** I am led to believe that once a book is in a given order in a Bible data type, it is nearly impossible to move it, because the book names are translated into integers and then bit strings when the books are compiled. The only way to put a book into a new integer slot is to move all the ones after its original position, and then re-compile every resource that ever used that data type. However, most of the Bible data types are built with a large-ish gap in sequence between the testaments, and I assume that whoever first added Laodiceans to the default Bible data type just added it to the end of the inter-testamental gap.
0 -
I also just checked in changes to the help article "How do I enter a Bible book abbreviation that will be recognized by Logos?" that reflects the current code of the default/generic Bible data type. You should see changes in that article next time the resource is updated.
0 -
Thanks Eli - if I hadn't been admiring the updates to Help I wouldn't have run into this. [8-|]
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Thanks! You know what I like? That I can fix it easily when it's broked. [H]
By the by, I have generated documentation of this sort for _every_ data type. It is ungainly, but comprehensive and accurate. (That is to say that it has only the same mistakes and omissions as the software does.) I hesitate to include it in the general Help file, because it would end up being larger than the current size of the Help.
For example:
## Ephraem Syrus (au+ephraem-syrus)Supports: ranges, multiple reference parsing
Alias: Ephraem_syrus
Formats:
- {name}, {work}
- {name}, {work} {0-9}
- {name}, {work} {0-9}.{0-9}
- {name}, {work} {0-9}.{0-9}.{0-9}
- {name}, {work} {0-9}.{0-9}.{0-9}.{0-9}
- {name}, {work} {0-9}.{0-9}.{0-9}.{0-9}.{0-9}Where {name} is:
- Ephraem SyrusWhere {work} is:
- Sermo de virtutibus et vitiis
- Reprehensio sui ipsius atque Confessio
- Ad eversionem superbiae
- Sermo compunctorius
- Sermo asceticus
- Ad imitationem proverbiorum
- Ad correctionem eorum qui vitiose vivunt et honores appetunt
- Reprehensio sui ipsius et Confessio
- De passionibus animi
- De paenitentia
... 147 more lines of Latin titles ...0 -
That could be very useful compared to the current method of find, look, guess. [:D] Especially since in certain cases I always seem to guess wrong. Could it be in the wiki with a link from https://wiki.logos.com/List_of_Datatypes ? That's a place many would think to look.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Eli Evans (Faithlife) said:
## Ephraem Syrus (au+ephraem-syrus)
Supports: ranges, multiple reference parsing
Alias: Ephraem_syrus
Formats:
- {name}, {work}
- {name}, {work} {0-9}
- {name}, {work} {0-9}.{0-9}
- {name}, {work} {0-9}.{0-9}.{0-9}
- {name}, {work} {0-9}.{0-9}.{0-9}.{0-9}
- {name}, {work} {0-9}.{0-9}.{0-9}.{0-9}.{0-9}Where {name} is:
- Ephraem SyrusWhere {work} is:
- Sermo de virtutibus et vitiis
- Reprehensio sui ipsius atque Confessio
- Ad eversionem superbiae
- Sermo compunctorius
- Sermo asceticus
- Ad imitationem proverbiorum
- Ad correctionem eorum qui vitiose vivunt et honores appetunt
- Reprehensio sui ipsius et Confessio
- De passionibus animi
- De paenitentia
... 147 more lines of Latin titles ...Any possibility for search format
- {name}, ANY
so could search across all works for a given {name} ?
Keep Smiling [:)]
0 -
MJ. Smith said:
That could be very useful compared to the current method of find, look, guess.
Especially since in certain cases I always seem to guess wrong. Could it be in the wiki with a link from https://wiki.logos.com/List_of_Datatypes ? That's a place many would think to look.I hope this will become available right within Logos in some future form of search functionality, so we don't have to think to look on the wiki, down the road!
Thanks to FL for including Carta and a Hebrew audio bible in Logos 9!
0 -
Any possibility for search format
- {name}, ANY
so could search across all works for a given {name} ?
This is not possible. The format listed above is the format for specifying a specific datatype reference, and references don't support any kind of wildcard notation (otherwise they would not be a reference). However, given that the stuff Eli posted indicates that is supports ranges, it should be valid to specify a reference range in the normal way you specify reference ranges. All you would need to know at that point to do your search is what the datatype considers the first and last work.
In other words, you should be able to search for something like the following (assuming that "De paenitentia" was the last work, which I'm sure it's not): <Ephraem_syrus Ephraem Syrus, Sermo de virtutibus et vitiis-De paenitentia>
Andrew Batishko | Logos software developer
0 -
In other words, you should be able to search for something like the following (assuming that "De paenitentia" was the last work, which I'm sure it's not): <Ephraem_syrus Ephraem Syrus, Sermo de virtutibus et vitiis-De paenitentia>
Range challenge is knowing (or finding) first and last work so can search all works. Awesome would be a resource with ranges by name, ideally with link to open search.
Keep Smiling [:)]
0 -
In other words, you should be able to search for something like the following (assuming that "De paenitentia" was the last work, which I'm sure it's not): <Ephraem_syrus Ephraem Syrus, Sermo de virtutibus et vitiis-De paenitentia>
Given that the range in the statement is not in alphabetic order, what is there for the user to determine/find/lookup the necessary sequence?
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:
In other words, you should be able to search for something like the following (assuming that "De paenitentia" was the last work, which I'm sure it's not): <Ephraem_syrus Ephraem Syrus, Sermo de virtutibus et vitiis-De paenitentia>
Given that the range in the statement is not in alphabetic order, what is there for the user to determine/find/lookup the necessary sequence?
Given that Eli was talking about this being generated documentation, I would hazard a guess that the values are given in the actual defined sequence.
Andrew Batishko | Logos software developer
0 -
They were generated from the data type info files (which define what the data type is) but I don't know what the order in those files represents. It is likely ultimately from the first resource that was used to create the data type (common), or alphanumeric by _internal_ representation (rare).
0 -
I would hazard a guess that the values are given in the actual defined sequence.
Eli Evans (Faithlife) said:but I don't know what the order in those files represents. It is likely ultimately from the first resource that was used to create the data type (common), or alphanumeric by _internal_ representation (rare).
Funny how both of you sidestepped the question:
MJ. Smith said:what is there for the user to determine/find/lookup the necessary sequence?
I suspect this is another one of those potentially useful features for which the information necessary to use is unavailable to the user. Given the more general usefulness of the information, this ought to be addressed.
But thanks for the additional information. I do appreciate it.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:
Funny how both of you sidestepped the question:
MJ. Smith said:what is there for the user to determine/find/lookup the necessary sequence?
My apologies. I didn't answer because I had nothing further to add that you aren't already aware of. You arleady know that there is no formal datatype documentation, and that the example Eli had provided was just a snippet of an example that isn't publically available.
For completeness... the answer is that there is nothing currently available to answer that question.
Andrew Batishko | Logos software developer
0
said: