> If brackets being stored as @[NUM]# turns out to be common I could handle that too I was unclear: The PDF's publisher decided to print the character '[' usin

> If brackets being stored as @[NUM]# turns out to be common I could handle that too I was unclear: The PDF's publisher decided to print the character '[' using the character code for '@' and a font choice that made '@' look like '['. The text content in the PDF did not match the displayed content. These kind of bizarre publishing choices make automated processing of research literature pretty frustrating IMO, so if you decide to just handle well-formed PDFs (e.g., LaTeX output) I think that's reasonable. Re: zoom & pan in the helper window: I meant zoom & pan post-capture, but I can see how re-capturing is a solution. I was resizing both windows a lot while testing so my portal captures were very inconsistent, which probably isn't the intended workflow. Thanks for working to make reading research and technical documents a better experience.