How to teach Logos book aliases?
I'm importing some public domain personal books; they are Jewish and as such reference the Bible books by their Hebrew names, for example: Tehillim for Psalms, shemot for Exodus, etc.
Is there a way I can teach Logos these book names so it recognizes the verse references listed in these books?
I noticed Logos understands a few of them for example if I type Qohelet it knows to open Ecclesiastes but most it does not understand. My only other alternative in building these books is to go through each one in Word replacing all the Hebrew book references with English equivalences and I thought it would just be much easier if there is a way to alias book names or something like that.
Thanks in advance,
-Jeremiah
Dead languages are my mid-life crisis
Comments
-
I also imported a public domain all Hebrew language resource which references bible books in Hebrew. I told Logos the book is in Hebrew but it seems it doesn't understand the Hebrew bible names in Hebrew characters either. I know this is a longshot does anyone know if there is a workaround for that?
It's an old large rabbinical text so I'd rather not go through an manually change all bible references to English. Please note this 2nd post is different than my initial post concerning English language pub. domain works.
thanks
Dead languages are my mid-life crisis
0 -
Hi Jeremiah.
There may be quicker or more fancy ways but if it was me I would look to do a search and replace in the source document that added the logos tags next to the Jewish reference.
Jeremy
Scripture set to music for worship and aid memorization. https://www.youtube.com/channel/UC-DojPa0TlpCGhtUJq1e3Pw
0 -
And by search and replace I mean all entries of one type in one go. You could also go one step further and create a macro to do them all in one go and then resuse that macro in multiple documents.
Scripture set to music for worship and aid memorization. https://www.youtube.com/channel/UC-DojPa0TlpCGhtUJq1e3Pw
0 -
Agree with Jeremy. Though I use macros to insert the Logos-legal after the readable text, so the original isn't disturbed. And not just for Logos. Each Bible software has its own legal names ... no choice.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Denise said:
Though I use macros to insert the Logos-legal after the readable text, so the original isn't disturbed.
Basically, this means replacing e.g. Tehillim 2:2 with something like [[Tehillim 2:2 >> <BibleBHS Ps 2:2>]], depending on the Hebrew bible used (or assumed).
Tehillim 2:2 may not be the actual text for Psalm 2:2, but it has to be prefixed with [[ and the whole expression terminated with ]], so the actual text will not be disturbed.
Dave
===Windows 11 & Android 13
0 -
Thanks for your comments Jeremy and Denise.
Dave: if I use this "Logos legal" formatting, will the reference in my book also be picked up if I'm reading say Psalm 2:2 in a different version (Targum for example)? The first stab I had taken before writing the post was just a global replace in the source text of Tehillim for Psalms and I compiled the work as a "cross reference". It seems this way picks up the citations correctly.
My primary concern is using the personal books in the "cited by" pane so whenever there is a reference within those books to the scripture I'm working with, I'll see it.
If I make it [[Tehillim 2:2 >> <BibleBHS Ps 2:2>]] will this cause the reference to not come up if I'm using a Targum or BHW etc.?
Thanks all for the tips.
Dead languages are my mid-life crisis
0 -
Jeremiah said:
If I make it [[Tehillim 2:2 >> <BibleBHS Ps 2:2>]] will this cause the reference to not come up if I'm using a Targum or BHW etc.?
The important thing is that <BibleBHS Ps 2:2> is the correct reference i.e. Ps 2:2 in a bible that uses the BHS datatype. Thereafter, Logos will locate the appropriate/correct reference in bibles that use a different datatype, such as BHW 4.18, ESV, NAB, Tanakh. CAL Targums use the same BHS datatype.
Dave
===Windows 11 & Android 13
0 -
thanks
Dead languages are my mid-life crisis
0