search

nisaacson / pdf-extract

Node PDF Extract
MIT License
384 stars 76 forks source link

Broken Link #23

Open benjameep opened 7 years ago

benjameep commented 7 years ago

In the README under windows, the link 'pdftotext' http://manifestwebdesign.com/2013/01/09/xpdf-and-poppler-utils-on-windows/ now just redirects to the manifestwebdesign.com homepage.

designerx2 commented 7 years ago

Stuck at this point and scratching my head about which binary(ies) are actually needed.

manuvel commented 7 years ago

Any update on the broken link of xpdf????

josephrony277 commented 7 years ago

Hey guys,

Download poppler tools for windows and unzip the file and refer the bin folder path in the system environment variables (http://blog.alivate.com.au/poppler-windows/)

image

image

It will work!!!!!

mcnewbk commented 7 years ago

I have done all of this, but I still get this error: Error: spawn pdftotext ENOENT at exports._errnoException (util.js:1034:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9)

Have you found a way around this as well? I have added all the required downloads to my system environment variables as well.

josephrony277 commented 7 years ago

I have 2 doubts

  1. Did you restart the system after updating the environment variables?
  2. Did you install pdftotext module after updating the poppler environment variable?
mcnewbk commented 7 years ago

@josephrony277 My issue was actually solved by having pdftotext as both a system environment variable and also adding it to the 'path' system environment variable. I had not added it to the actual 'path' variable when I posted this comment. Thanks for your response.