Re: [racket-users] error with pdf-read / libpoppler on Windows

2018-03-23 Thread David Storrs
On Thu, Mar 22, 2018 at 6:45 PM, Neil Van Dyke wrote: > (Warnings: the PDF documentation is big, you'll appreciate why C and C++ > programmers have difficulty implementing PDF without filling it with > vulnerabilities, and you'll also get to see some totalitarian-friendly >

Re: [racket-users] error with pdf-read / libpoppler on Windows

2018-03-23 Thread Joel Dueck
This point is well taken. For my package's core functionality I mainly need to be able to get a page count and the size of the first page. I would rather not have to try and write my own functions to do that; even though it looks (from the docs you provided) like the parsing wouldn't be too

Re: [racket-users] error with pdf-read / libpoppler on Windows

2018-03-22 Thread Neil Van Dyke
Side comment for the list, on software engineering security practice... If what you have to do with the PDF is simple to do to the raw PDF format, and your code might be fed PDF files of provenance that you don't control, it's probably better security not to involve Poppler.