[OS X TeX] Sierra and PDFKit
riseguin at earthlink.net
Fri Sep 23 23:47:32 EDT 2016
No, I don’t have any direct contact with the developers. As far as I know, the only way to contact them is through the forum
I think you need to somehow establish yourself with a user-id and password. You have to create a “ticket” for a new issue. (This is really clumsy compared to working with the TeXShop or BBEdit developers.) If I still have a valid id/password, I don’t even remember what it is. Bottom line: you’re welcome to jump through the hoops yourself and report your findings to Christiaan Hofman.
I just noticed at the above link that Skim is also having a few other problems that they have found workarounds for.
On Sep 23, 2016, at 2:26 PM, Richard Koch <koch at uoregon.edu> wrote:
Apparently a couple of issues showed up in Skim regarding PDFKit. It looks like the developer was able to find a workaround though:
I use Skim, but I’m still trying to verify if Capture One Pro has been fixed in regard to Sierra, so I haven’t upgraded to Sierra yet myself and can’t personally verify any of this.
Do you have contact with the Skim developers. If so, you might want to pass along this information.
There is definitely a bug in the PDF search routine in PDFKit under Sierra. I reported this bug to Apple, but haven't had a reply. TeXShop has a workaround for the bug.
Here is a description.
Asynchronous searches can be done either by responding to notifications
or by implementing documentDidBeginDocumentSearch, documentDidEndPageFind,
documentDidFindMatch, and documentDidEndDocumentSearch. I suspect both
methods will see the same bug, but my application implements these calls
and does not use notifications.
PDFKit contains two routines, findString and beginFindString. The first is for
searching for the first match to a string, and the second is for an asynchronous
call which will produce a list of matches.
A little debugging on El Capitan shows that "documentDidFindMatch" is not called
following a call to findString, but is called many times following a call to beginFindString.
The same debugging on Sierra shows the reverse. It is as if the PDFKit team just
switched findString and beginFindString by mistake.
And indeed, my patch was simply to call findString rather than beginFindString, but only on Sierra. I'll have to release a new version as soon as Apple fixes this bug.
----------- Please Consult the Following Before Posting -----------
TeX FAQ: http://www.tex.ac.uk/faq
List Reminders and Etiquette: https://www.esm.psu.edu/~gray/tex/
List Archives: http://dir.gmane.org/gmane.comp.tex.macosx
TeX on Mac OS X Website: http://mactex-wiki.tug.org/
List Info: https://email.esm.psu.edu/mailman/listinfo/macosx-tex
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MacOSX-TeX