<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Ross -<br></div><div><br data-mce-bogus="1"></div><div><div>>| BTW, it takes rather delicate programming to properly locate where the</div><div>>| annotation rectangle resides on the page. It’s even harder when the</div><div>>| anchor text splits across 2 pages, as then you need to have two</div><div>>| rectangles, 1 for each page.</div><div><br data-mce-bogus="1"></div><div>Understood. A similar problem occurs when searching for text matches, when the phrase (or even a hyphenated single word) being searched for crosses a page or other document boundary.</div><div><br data-mce-bogus="1"></div><div>For now, I want only to rely on what Apple's PDFKit lets me access via their official API. Basically, given a point on a PDFPage object, one can retrieve a PDFAnnotation object associated with that point, then query the annotation object for its bounds. For now, it returns a single rectangle, presumably the first of several possible rectangles on different pages, though usually the only rectangle on one page. The "delicacy" of Apple's programming in this situation isn't clear. But for what I'm doing, I've not found any serious problems so far relying on the single bounds returned.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Doug McKenna<br data-mce-bogus="1"></div><div>Mathemaesthetics, Inc.<br data-mce-bogus="1"></div></div><div data-marker="__QUOTED_TEXT__"><div class=""><br data-mce-bogus="1"></div>
</div></div></body></html>