Can't use pdf-reader-turtletext with pdf-reader 1.3.x

[timigod]

Unfortunately, it seems like this gem has a fixed dependency on pdf-reader v1.1.1. So it's not usable with the latest version 1.3.3. We're having serious issues merging code where one person used the latest pdf-reader and another used pdf-reader-turtletext. pdf-reader methods are being overridden. Is there any solution to this?

[tardate]

@timigod the fixed dependency was intentional at the time. Looks like the reason has already been addressed by 1.3.3, so perhaps about time to refresh this gem. Thanks for the nudge!

I'll take a look at bringing this back up-to-date and compatible with latest pdf-reader. If you've already done that work, please send me a P/R.

However, in the meantime, using turtletext does come with a fixed pdf-reader dependency

[timigod]

@tardate unfortunately, my skill level isn't quite there yet. So no, I've not done that work. Thanks for the response, however, and please do notify when we can use it with 1.3.x.

[ndbroadbent]

@tardate Thanks for the work on this gem! I would also love to use this with Ruby 2.4 and pdf-reader 2.0.0. No problem if this is no longer being maintained, but it looks like a very useful library.

[emmeryn]

For anyone still having this issue, I submitted a pull request (#10) to fix compatibility with pdf-reader 2.4.0. You can find it here: https://github.com/emmeryn/pdf-reader-turtletext in the update-gem branch.

[michaelschmitz]

@tardate Thanks for updating the code and thanks to @emmeryn for the improvement.

When running bundle install or update it still seems to pull 0.2.2 without the fix for 2.4, not sure whether the gem version needs to be updated or something else to be done (error could also be due to me doing something wrong, no expert in this).

For now, I simply added a reference to the latest commit to my gemfile: gem 'pdf-reader-turtletext', git: 'https://github.com/tardate/pdf-reader-turtletext.git', ref: '82869af'

[emmeryn]

Yeah I didn't update the gem version in my pull request that was merged, so @tardate would have to do that and push the new version of the gem for the latest version with the fixes to be retrieved.

[zagraves]

I'd love to have a new version of the gem published to use, @tardate. Thank you!