BUG-BUG-BUG-BUG-BUG - External Links to Internal Resources - Especially MAC

Howdy!

I'm trying to create web pages that have embedded links to resources in Logos. I am using Logos 6.7 on both a Mac and a Windows PC. I have some questions and possibly a bug to report in the way that the Mac Logos application handles creating these links.

Here is a sample link that I made on the Windows PC:

<a target="_blank" href="http://ref.ly/Re2.18-24" class="bibleref" title="Revelation 2:18ñ24">Revelation 2:18ñ24</a> <a href="logosres:kjv1900;ref=BibleKJV.Re2.18-24;off=0;ctx=_that_receiveth_it.$0A~18$C2$A0And_unto_j$EF$BB$BFthe_an">»</a>

Here is the same link that Logos for Mac 6.7 created:

<a target="_blank" href="http://ref.ly/Re2.18-24" class="bibleref" title="Revelation 2:18–24">Revelation 2:18–24</a> <a href="logosres:kjv1900;ref=BibleKJV.Re2.18-24;off=0;ctx=_that_receiveth_it.$0A~18$C2$A0And_unto_j$EF$BB$BFthe_an">»</a>

The PC version plants an n with a tilde in the place that the Mac version plants a hyphen. The n with tilde is actually working. These would be for the Faithlife online Bible links.

For the internal reference links, both the PC and the Mac use a raquo as a place holder in the link. Is this correct functionality?

Can this please be fixed sometime soon, as I have to work my fingers to the bone editing each generated link by hand when this feature is supposed to be working.?

Thanks!

Find more posts tagged with

Comments

Bradley Grainger (Logos)

What application are you pasting these links into?

As far as I can tell, Logos 6 is generating the correct text (in both Unicode and Windows-1252 encodings) so it appears that the destination application is incorrectly interpreting an en dash as an ñ.

Michael Miles

https://community.logos.com/discussion/comment/780501#Comment_780501

What application are you pasting these links into?

As far as I can tell, Logos 6 is generating the correct text (in both Unicode and Windows-1252 encodings) so it appears that the destination application is incorrectly interpreting an en dash as an ñ.

I'm using Logos 6.7 on the Mac and pasting into BBEdit. Same results in other programming editors here.

Thank you.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/780501#Comment_780501

As it turns out, theMac OS Roman code page has ñ at 0x96. Are you running the Windows version of Logos 6 on a Mac in a VM? If so, I suspect there's a bug in the VM software that's not correctly translating 8 bit characters from Win1252 to MacRoman when transferring clipboard contents across the VM boundary. Pasting into a Unicode-aware application may help. (Does the problem occur in TextEdit?)

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/780502#Comment_780502

I'm using Logos 6.7 on the Mac and pasting into BBEdit.

And is that working or not? The HTML you pasted above (the second snippet, labelled from the Mac) looks correct to me.

Which application are you pasting into when copying from the Windows PC?

Michael Miles

https://community.logos.com/discussion/comment/780503#Comment_780503

As it turns out, theMac OS Roman code page has ñ at 0x96. Are you running the Windows version of Logos 6 on a Mac in a VM? If so, I suspect there's a bug in the VM software that's not correctly translating 8 bit characters from Win1252 to MacRoman when transferring clipboard contents across the VM boundary. Pasting into a Unicode-aware application may help. (Does the problem occur in TextEdit?)

Sorry for the dramatic post title, but I brought this up in a previous post that was skipped over by Logos.

I am not running any VMs for these. The Windows link was pasted into notepad and the Mac into BBEdit. I am away from the computers and am hammering an iPhone, so please excuse this response if it comes out mangled.

Tomorrow evening I will take a look at the document encoding settings that I am using in BBEdit and Brackets and see if I messed something up. Thanks for your help.

Michael

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/780512#Comment_780512

The Windows link was pasted into notepad and the Mac into BBEdit.

Ah. My guess is that you're saving the file in Notepad with an "ANSI" encoding, and the problem is that BBEdit is interpreting that character differently (because of Windows vs Mac differences). Try using "Unicode" or "UTF-8" as the encoding when saving the file in Notepad.

delete12066188

https://community.logos.com/discussion/comment/780513#Comment_780513

I'm trying to create web pages that have embedded links to resources in Logos.

Dit you try just Copy the Recource HTML in Logos and simply past it to the Webpage?

Sascha

Michael Miles

https://community.logos.com/discussion/comment/780518#Comment_780518

I'm trying to create web pages that have embedded links to resources in Logos.

Dit you try just Copy the Recource HTML in Logos and simply past it to the Webpage?

Sascha

What I have been doing is to highlight the full resource range that I wish to reference then I click on Option-Command-C in the Mac version of Logos to create the links. I do not have a Windows machine up and running this morning to check what key combination I use to grab them from the Windows version of Logos.

Yes, you can just paste them into a web page and have the online viewer click on the link in their browser and the resource will open in Logos on their desktop. On my iPhone, I have to click the reference twice before Logos steers me to the referenced resource range.

You can put an image inline and have the user click a Logos icon to open the reference:

That link references an icon a couple of levels back in the folder structure on your web server. If you click the link, Logos will open Ezekiel 13:20-23.

I am working on a template page that will serve as a model for other studies that I have to share. You can see how the Logos links work on that page:

http://7seals.net/Studies/Jezebel.Of.Thyatira/

I hope that this helps you to get this working.

Michael

Michael Miles

https://community.logos.com/discussion/comment/780513#Comment_780513

The Windows link was pasted into notepad and the Mac into BBEdit.

Ah. My guess is that you're saving the file in Notepad with an "ANSI" encoding, and the problem is that BBEdit is interpreting that character differently (because of Windows vs Mac differences). Try using "Unicode" or "UTF-8" as the encoding when saving the file in Notepad.

Hi Bradley,

I have not fired up the Windows machine today and I need to leave for work. On the Mac I am using BBEdit wit the Western (Mac OS Roman) encoding. The link forms exactly the same if I use UTF-8. I'll look at the Windows rig when I get home.

Thanks for your help and guidance on this.

Michael

Michael Miles

https://community.logos.com/discussion/comment/780559#Comment_780559

The Windows link was pasted into notepad and the Mac into BBEdit.

Ah. My guess is that you're saving the file in Notepad with an "ANSI" encoding, and the problem is that BBEdit is interpreting that character differently (because of Windows vs Mac differences). Try using "Unicode" or "UTF-8" as the encoding when saving the file in Notepad.

Hi Bradley,

OK, I'm on the Windows box that I was on when I reported a synchronization problem a few minutes ago here in the forums.

I was pasting the resource link from Logos into Windows notepad and I don't see anything in the application that indicated what encoding notepad uses. I'm on Windows 7 with 999 patches (fully patched) using the notepad that Microsoft has been shipping with Windows since the dawn of time. Am I missing anything? I must admit that I spend a whole lot more time on the Macs these days than I do on Windows. It must have been that 8 year foray into the realm of IT where even seeing a Windows desktop made me want to hurl over the side of the boat.

Should I try it in a different editor on Windows? What might you recommend?

Thank you,

Michael

Mark Barnes

https://community.logos.com/discussion/comment/780800#Comment_780800

I don't see anything in the application that indicated what encoding notepad uses

In Notepad, you can select the encoding when you chose "Save As". ANSI is the default, but you can switch to UTF-8.