You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 29, 2019. It is now read-only.
First I have to say that this tool is absolutely awesome to extract bib data. So much time saved with just one command line, many many thanks!
However I had to build the gem myself to have the 0.1.1 version. The one in the repository seems to be outdated, without extract-bib etc... even though the version of the package indicate 0.1.1
Just wanted to point that out.
Thanks again.
The text was updated successfully, but these errors were encountered:
Any news on this? Same here, am a newcomer to Ruby it would be really helpful that such features were in the Gem itself, plus allowing to easily replicate setups between different machines. Plus the doc is inconsistent, telling that installation should be done with gem install pdf-extract but then presenting features that are not included in this build… =(
Take it easy, just build it for yourself : ) git clone https://github.com/CrossRef/pdfextract cd pdfextract gem build pdf-extract.gemspec gem install pdf-extract-0.1.1.gem
@AnikoG Sure, but I want to plug it to another library I am writing, written in Python. As most of my users will be Pythonistas, and not people from the Ruby side, it would be really nice if installing it could be as easy as gem install pdf-extract, without issues such as this one or #20 =(
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First I have to say that this tool is absolutely awesome to extract bib data. So much time saved with just one command line, many many thanks!
However I had to build the gem myself to have the 0.1.1 version. The one in the repository seems to be outdated, without extract-bib etc... even though the version of the package indicate 0.1.1
Just wanted to point that out.
Thanks again.
The text was updated successfully, but these errors were encountered: