Changing LORD to Yahweh

I just thought that I'd share how I'm using visual filters to reveal where יהוה (YHWH) is in the OT. I actually replace the text with Yahweh.
First create a new highlighting style (right click in the highlighting panel):
Then, create a Visual Filter (File Menu) and have it display your new style whenever יהוה is in the text (This will look in the reverse interlinear):
The text of your Bible will now display like this:
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org
Comments
-
Jacob Hantla said:
I just thought that I'd share how I'm using visual filters to reveal where יהוה (YHWH) is in the OT. I actually replace the text with Yahweh.
This is worthy of a blog entry and/or a wiki entry. Thanks for sharing.
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 -
Nice idea, Jacob. Too bad we can't get Logos to recognize the article as part of the word so 'the LORD' would be in italics above the line. Nevertheless this is a very creative use of highlighting.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Jacob-
That is really cool - good job. I plan on doing this.
Do you think you could get the article "the" in the visual filter so that the passage reads Yahweh instead of the Yahweh?
Regards,
Anthony
Anthony Uvenio
0 -
Thanks.
This technique obviously could be used to do this for any word. Differentiation among the greek words for love could be a good use too.
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
Anthony U said:
Jacob-
That is really cool - good job. I plan on doing this.
Do you think you could get the article "the" in the visual filter so that the passage reads Yahweh instead of the Yahweh?
Regards,
Anthony
I think that this is on Logos' end. They don't lump the article "The" in with LORD even though THE LORD is their translation from YHWH
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
-
-
Joe Miller said:
One filter finds all OT occurrences of "the Lord" in English and the second creates the insert for YHWH.
Except they don't always match, do they?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:Joe Miller said:
One filter finds all OT occurrences of "the Lord" in English and the second creates the insert for YHWH.
Except they don't always match, do they?
No that won't work 100% of the time:
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
This is why it is important to tie it to YHWH instead of the Lord. I might miss this kind of thing without visual filters:
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
Here's a string, which ought to work, but doesn't
(<Lemma = af/he/יהוה> ANDEQUALS Lord) AFTER 1 WORD the
It adds the "Yahweh" in twice - once for each word. Is that a bug?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
-
I tried tying the filter to "the LORD" and it seems to be working and replacing "the" as well. Please correct me if I'm wrong:
This also seems to work for bibles that do not have a reverse interlinear.
"It seems our problems solve themselves when we look beyond us to those truly in hell." - Beyond Our Suffering - AILD
0 -
This is wrong unfortunately, for several reasons (assuming the ESV for the example):
- There are 315 occassions where YHWH is used, but it's not translated as "Lord" (search for <Lemma = af/he/יהוה> NOTEQUALS "Lord" to find them).
- There are at least 654 occassions where Lord does translate YHWH, but it's not "the Lord" (search for (<Lemma = af/he/יהוה> ANDEQUALS "Lord") ANDNOT "the Lord" to find some of them).
- Also, you're not doing a case-sensitive search, which means you'll be getting several false positives(search for ("Lord" NOTEQUALS <Lemma = af/he/יהוה> ) AND "the Lord" to get an approximate list).
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thanks Jaco for sharing, I had not thought of using filters for that. It's a pretty cool concept. If it can catch the article as well then it would be really awesome.
In Christ,
Ken
Lenovo Yoga 7 15ITL5 Touch Screen; 11th Gen Intel i7 2.8Ghz; 12Gb RAM; 500Gb SDD;WIN 11
0 -
Mark Barnes said:
Haha! Wonderful. I really did laugh out loud at this.
Mark Barnes said:Here's a string, which ought to work, but doesn't
(<Lemma = af/he/יהוה> ANDEQUALS Lord) AFTER 1 WORD the
It adds the "Yahweh" in twice - once for each word. Is that a bug?
It seems this is a pretty fundamental thing with how L4 handles searches. Any time you do a search like this where a term serves as a condition for another term (like using the NEAR or WITHIN X WORDS keywords) the results include both terms (effectively double-counting the actual instances that fulfill the condition). Another way of saying it is that it's reversible with no term being primary and the other just a secondary condition. So
the BEFORE 1 WORD (<Lemma = af/he/יהוה> ANDEQUALS Lord)
returns the same results as
(<Lemma = af/he/יהוה> ANDEQUALS Lord) AFTER 1 WORD the
even though in the first case I really only want it to pick out "the" and not "Lord" and in the second case I really only want it to pick out "Lord" and not "the". I agree that it should be fixed but I think it could take some work to get the parsing engine to figure out which search term is the "primary" one that you are actually looking for as opposed to the secondary conditions you put on it.
The result is that any filter that uses a condition will highlight both the primary term and the condition.
0 -
I have not been able to confirm this yet, so let me ask. Did you restrict the english search for "the Lord" to the OT? Or do those hits include the NT? — which obviously we don't want :-)Mark Barnes said:This is wrong unfortunately, for several reasons (assuming the ESV for the example):
- There are 315 occassions where YHWH is used, but it's not translated as "Lord" (search for <Lemma = af/he/יהוה> NOTEQUALS "Lord" to find them).
- There are at least 654 occassions where Lord does translate YHWH, but it's not "the Lord" (search for (<Lemma = af/he/יהוה> ANDEQUALS "Lord") ANDNOT "the Lord" to find some of them).
- Also, you're not doing a case-sensitive search, which means you'll be getting several false positives(search for ("Lord" NOTEQUALS <Lemma = af/he/יהוה> ) AND "the Lord" to get an approximate list).
0 -
Mark Barnes said:
Here's a string, which ought to work, but doesn't
(<Lemma = af/he/יהוה> ANDEQUALS Lord) AFTER 1 WORD the
It adds the "Yahweh" in twice - once for each word. Is that a bug?
Oh, actually, what I described in my last post is a separate issue. You're talking about the fact that it currently applies highlight markings such as Label Text (which don't change the surface text itself but rather add in something new) twice when the search returns multiple words. I guess this makes more sense when a search returns multiple words separated by intervening text. (Like if I search for "disciple WITHIN 3 WORDS loved" and get "disciple whom Jesus loved" I'd want the highlight to apply to both "disciple" and "loved" but not "whom Jesus"). But it looks especially funny if the two words are together (like "the" and "LORD") and the extra element shows up twice in a row.. Would you want it to be coded so that highlighting that changes text font/color/etc. is applied to both words but extra elements like Label Text are only applied to one word? For example both "the" and "LORD" could be highlighted in red but only "LORD" would get the superscript label. That would require some extra level of distinction to tell which work gets which parts of the highlighting.
0 -
Joe Miller said:
Did you restrict the english search for "the Lord" to the OT?
No, they're just OT. Most of the first ones are "Lord GOD". Most of the second ones are "O Lord". Most of the third ones (which is not an accurate list) are Adonai, or where the YHWH is assumed but not stated.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Steve Mehaffey said:
But it looks especially funny if the two words are together (like "the" and "LORD") and the extra element shows up twice in a row.. Would you want it to be coded so that highlighting that changes text font/color/etc. is applied to both words but extra elements like Label Text are only applied to one word? For example both "the" and "LORD" could be highlighted in red but only "LORD" would get the superscript label. That would require some extra level of distinction to tell which work gets which parts of the highlighting.
Yes, that's exactly what I was suggesting. But I'm sure some people prefer the existing method for other searches.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Pretty cool.
However, I find that it does mess up the LHI. So in the LHI I unselected the visual filter that included that entry and all returned to normal. The AFAT (Andersen-Forbes) does this too. My version of the BHS doesn't have an issue. I don't know if any other Hebrew texts would be affected.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:
So in the LHI I unselected the visual filter that included that entry and all returned to normal.
It would probably be more efficient to apply the visual filter search just to a collection of English Bibles.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
It would probably be more efficient to apply the visual filter search just to a collection of English Bibles.
Or at least non-original language Bibles. The filter also works in the one Spanish reverse interlinear (RVR60) as well (though it uses Jehová - reducing the need for the identifier). As far as I know, the RVR60 is the only reverse interlinear in a language other than English.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Mark Barnes said:
Here's a string, which ought to work, but doesn't
(<Lemma = af/he/יהוה> ANDEQUALS Lord) AFTER 1 WORD the
It adds the "Yahweh" in twice - once for each word. Is that a bug?
The search works but double-counts the results from the ANDEQUALS expression. I don't like it but Logos wants to count each word ie. by design.
EDIT: sorry, wrong context!
Dave
===Windows 11 & Android 13
0 -
It would be very cool if search could be given the ability to search all highlighting fields, including custom ones now.
Logos Platinum
Windows 7 - 64 Bit
Lenovo laptop E520 i7-2640M, 2.8GHz 8G Ram, 2G GraphicsAustralia
0 -
The only other problem I see here is that you probably will want to limit this to only English Bibles. When I applied it to all Bibles it changes my Hebrew texts.
0 -
Love this thanks
0 -
-
Hi Jacob,
Super! Thanks for sharing this!
Charlene
0 -
Jonathan said:
The only other problem I see here is that you probably will want to limit this to only English Bibles. When I applied it to all Bibles it changes my Hebrew texts.
As discussed above, visual filters can be restricted to particular collections to achieve exactly this.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Hmmm... For some reason I did not read/see that there was already a post about this above. Weird, I must have been sleeping.
0 -
Tom Geswein said:
Tom this would work if Yahweh was the underlying word behind every instance of "The Lord" in the OT. But it isn't. There are times when Yahweh is not translated: "The Lord". And there are times when "The Lord" didn't come from Yahweh (See my example from Is 6).
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
-
Mark Barnes said:Joe Miller said:
One filter finds all OT occurrences of "the Lord" in English and the second creates the insert for YHWH.
Except they don't always match, do they?
If you do it this way, they match:
That gives me:
And if I set the color to white and the size to 20% (in addition to the superscript) in the first style, I can make the original text practically disappear:
(Although having a white style in the styles list also makes the style entry seem to disappear [:^)] )
MacBook Pro (2019), ThinkPad E540
0 -
Well done Todd! That's the best yet.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
-
-
Mark Barnes said:
Hey Mark, you'll need the mileneium stadium for a church if you adopt this method for church growth, a bit too liberal for my tastes [:P]
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
The solution is particularly helpful (time saving) for English Bibles that do not distinguish between the translations of YHWH and adonai (such as, inexplicably in my books, the NKJV).
Jacob, I love the filder for doulos (= slave instead of servant). Wished I could do this in my print Bible!
The other one I have often wished for but might be trickier to implement even in Logos 4 is to signal which second person pronouns (you) are singular and which are plural and to do so in a way that is not visually excessive (or perhaps the focus should be on verbs, not pronouns). Considering how the initial idea was even improved in this thread, perhaps the collective wisdom can come up with a wonderful idea for this too?
Thanks again, Jacob, Todd and others for sharing.
Blessings,
Francis
0 -
MacBook Pro (2019), ThinkPad E540
0 -
Recently I've begun to notice that this visual filter is being inconsistently or not at all applied even though it is active.
It is active and it does work sometimes. Any ideas?
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
interesting Jacob... I have the same problem if I bring up the ESV & apply the visual filter. I haven't noticed that in the NASB though, which is my primary translation for study.
Urban Scholar - http://urban-scholar.com
Christ-centered Hip-Hop - http://www.sphereofhiphop.com0 -
Jacob Hantla said:
Your filter needs to use "<lemma = lbs/el/δοῦλος>" instead of just "δοῦλος". (FYI, if you changed the search type to Morph, then the syntax would be the simpler "lemma:δοῦλος"). Otherwise you're just matching the manuscript text, and it's not "δοῦλος" in those cases.
MacBook Pro (2019), ThinkPad E540
0 -
Todd Phillips said:
Your filter needs to use "<lemma = lbs/el/δοῦλος>" instead of just "δοῦλος". (FYI, if you changed the search type to Morph, then the syntax would be the simpler "lemma:δοῦλος"). Otherwise you're just matching the manuscript text, and it's not "δοῦλος" in those cases.
Thanks Todd. I guess I thought it was basing it off of either lemma or manuscript. Thanks for clarifying and fixing it. Works great now.
Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org0 -
Francis said:
The other one I have often wished for but might be trickier to implement even in Logos 4 is to signal which second person pronouns (you) are singular and which are plural and to do so in a way that is not visually excessive (or perhaps the focus should be on verbs, not pronouns). Considering how the initial idea was even improved in this thread, perhaps the collective wisdom can come up with a wonderful idea for this too?
I have used a few variations of this, but currently, I am using a Visual Filter style that writes a portion of the Morp Codes under the hits.
You need to create a style for every different morph code, and save(exit) the Highlighter Panel, before creating or updating the Visual Filter(s). I am using a text size that is 40%, so its readable, but easy to ignore too.
I would do this also for the original example of this thread. I would leave the supplied translation-text unchanged, and write "YHWH" below "Lord". This would tend to avoid the problems with "the Lord" or "O Lord" and such variations.
(I would love it if we could provide a tag as part of each rule within a given Visual Filter, and then draw on that tag within a Highlight Style. Then we could use "[T]" or "%T" or something within a Highlight Style, to pick up the tag. Until then, I guess I'm going to be creating a LOT of new Highlights. Hint for developers: like %s in printf to insert a string at that spot.)
P.S. For the record, I really did not like the modified Ten Commandments, and would rather such "jokes" not be posted in the Logos Forums.
0 -
JimT said:
P.S. For the record, I really did not like the modified Ten Commandments, and would rather such "jokes" not be posted in the Logos Forums.
Sorry, no offence intended.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Francis said:
The other one I have often wished for but might be trickier to implement even in Logos 4 is to signal which second person pronouns (you) are singular and which are plural and to do so in a way that is not visually excessive
Francis, after reading this post, this is a visual filter I implemented. The "Pl" is not very intrusive and is enough to remind me that the second person pronouns and verbs are plural.
"For the kingdom of God does not consist in words but in power"
Wiki Table of Contents
0 -
Jacob Hantla: Thanks for this wonderful tip. I find it rather annoying that translators continue to incorrectly translate the Lord's personal name (YHWH) into a title (LORD). This will save me a lot of time in my studies.
Todd Phillips: Thanks for helping to make it even better (by getting rid of "the").
0 -
0
-
It would be nice if we could add a more powerful form of pattern to the Visual Filter rules.
This is something thats possible in various programming languages or regular expression tools. The ability to provide an optional context that comes before and comes after the target match.
An example, "invented" pattern of the form /pre/match/post/ to look for "fox" after "brown", and then highlight the find.
Pattern: /brown/fox//
Text: The quick brown fox jumped, or did the other fox push him?
Result: The quick brown fox jumped, or did the other fox push him?
The 2nd "fox" does not have the matching prefix, and "brown" is not highlighted as its part of the context, not the actual target.
0