PB linking to resource question
When creating a link from a PB to a Logos resource - in the Morris Proctor video he says to use "Copy location to URL" but on the wiki page for creating links it says to use "Copy location to Wiki". I've tried both and the first one works most of the time but sometimes the other one does. Sometimes no matter which one I use it doesn't work. Which one is correct? Will this still be worked on?
Comments
-
Leigh -
The four choices you have present the same information in different syntax. Compare the following:
URL logosres:esv;ref=BibleESV.Dt15.1-23
HTML <a target="_blank" href="http://ref.ly/Dt15.1-23;ESV" class="bibleref" title="Deuteronomy 15:1–23">Deuteronomy 15:1–23</a> <a href="logosres:esv;ref=BibleESV.Dt15.1-23">»</a>
WIKI [[Deuteronomy 15:1–23 >> logosres:esv;ref=BibleESV.Dt15.1-23]]
RL [[Deuteronomy 15:1–23 >> logosres:esv;ref=BibleESV.Dt15.1-23]] | English Standard Version
Generally, I would think you would want to use the "wiki" method (to save time). I did note that the PBB WIKI says the following:
If the link does not work its book and location will have to be re-typed in capital letters e.g. [[Authorship >> logosres:NBC;art=DEUTERONOMY3C]]
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Leigh Johnson said:
I've tried both and the first one works most of the time but sometimes the other one does. Sometimes no matter which one I use it doesn't work. Which one is correct?
I would like to know which ones do not work using the WIKI method. I've not detected differences (in the link) between URL and WIKI.
This WIKI method is recommended because it formats the link with a label that can be changed to suit your book's need.
Dave
===Windows 11 & Android 13
0 -
Dave -
In the example from the PBB WIKI I provided above (the last line of my previous post), the "copy wiki" does not work properly without changing the references to ALL CAPS. The screen shot below shows 1) the adjusted format and 2) the original format by the "copy wiki" method. If you don't change the references to all caps, it takes you to the beginning of the commentary instead of the specific location desired.
Note that "NBC" and "DEUTERONOMY3C" were capitalized to make the link function properly.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Leigh -
I didn't feel that I answered your questions well enough... Let me take another stab.
Leigh Johnson said:Which one is correct?
Either method is OK. I did not see the MP video, but I am guessing that he was showing how the syntax works. Using the WIKI method is generally faster, since it is roughly in the format you will want to use. According to the WIKI, sometimes the references need to be changed to ALL CAPS, as my previous post explains, which may be why it doesn't work sometimes. Also, you need to make sure that the syntax is written in an unformatted style. I have found that adding "BOLDING", for example, seems to break the link sometimes.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
alabama24 said:
Leigh -
The four choices you have present the same information in different syntax. Compare the following:
URL logosres:esv;ref=BibleESV.Dt15.1-23
HTML <a target="_blank" href="http://ref.ly/Dt15.1-23;ESV" class="bibleref" title="Deuteronomy 15:1–23">Deuteronomy 15:1–23</a> <a href="logosres:esv;ref=BibleESV.Dt15.1-23">»</a>
WIKI [[Deuteronomy 15:1–23 >> logosres:esv;ref=BibleESV.Dt15.1-23]]
RL [[Deuteronomy 15:1–23 >> logosres:esv;ref=BibleESV.Dt15.1-23]] | English Standard Version
Generally, I would think you would want to use the "wiki" method (to save time). I did note that the PBB WIKI says the following:
If the link does not work its book and location will have to be re-typed in capital letters e.g. [[Authorship >> logosres:NBC;art=DEUTERONOMY3C]]
What is the advantage of designating the Bible Version as opposed to using the default version in Logos?
Mission: To serve God as He desires.
0 -
Lynden Williams said:
What is the advantage of designating the Bible Version as opposed to using the default version in Logos?
You may have situations where you want to force the link to a particular translation of Bile because you are referring specifically to that - this risk being that the user does not have that version. An example might be that you want to force the link to RSVCE or NAB if it's a link to Macc, for example, which may not be in the user's default Bible.
If you do not specify a Bible, it allows the user to have the links work with their preferred Bible.
0 -
you might be after a specificly worded translation:
or if your chuch prefers a version
or you were using it as the base of your commentary/notes etc...though not sure what happens if version is absent on the destination platform
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
Lynden Williams said:
What is the advantage of designating the Bible Version as opposed to using the default version in Logos?
Those links are produced by Copy Location (Ctrl+Alt+C) from the resource, but not strictly needed with the ESV as it has the "Protestant" canon of Bible books. Bibles with the Apocrypha (KJV = BibleKJV) or with having books in different order or with different versification (Hebrew bibles=BibleBHS) need references to be designated by Bible "Version". I think there are some versification differences between the ESV and NIV, so the distinction of BibleESV and BibleNIV may matter.
Dave
===Windows 11 & Android 13
0 -
Thanks everyone. I have bookmarked the page.
Mission: To serve God as He desires.
0 -
In the MP videos it creates the link by using CTR-ALT-C set to Copy Location as URL, then highlighting the word in your PB that you want to make a link,select 'Insert Hyperlink' and then pasting the URL into the address line. I had been trying to create a link to a reference in DBL Greek. It looks like changing the resource name and reference to all caps is what I needed to do. Thanks for the help.
0 -
alabama24 said:
According to the WIKI, sometimes the references need to be changed to ALL CAPS, as my previous post explains, which may be why it doesn't work
This bug should be fixed in the next update.
0
