View Single Post
Old 08-18-2019, 04:39 PM   #14
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,911
Karma: 6120478
Join Date: Nov 2009
Device: many
I think the problem is the call to create a canonical path for each manifest file. On my machine it will not resolve the symlinks, and on your machine it resolves the symlinks so it converts:

converts:

"/var/folders/kl/5s_sbwr972n1qq9xrk7rlyvr0000gn/T/Sigil-DTjJwa/OEBPS/Text/ded01.xhtml"

to

/private/var/folders/kl/5s_sbwr972n1qq9xrk7rlyvr0000gn/T/Sigil-DTjJwa/OEBPS/Text/ded01.xhtml

And when I remove the length of the m_ExtractedFolderPath which was:

"/var/folders/kl/5s_sbwr972n1qq9xrk7rlyvr0000gn/T/Sigil-DTjJwa"

I end up with leaving 8 characters too many in the path (length of "/private").

So this appears to be caused by a change in how canonicalFilePaths are being resolved in macOS 10.13 and earlier and macOS10.14 and later.

This would cause lots of havoc in just about everything to do with launching a new file with open with as well.

"canonicalFilePaths" are supposed to have all symlinks resolved but that does not happen on my machine but does seem to happen on your machine.

So I think this is a bug fix made by Apple for macOS 10.14 that breaks Sigil.

I will look into fixing this.
KevinH is offline   Reply With Quote