Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

magick dependency #29

Closed
dmi3kno opened this issue May 30, 2018 · 2 comments
Closed

magick dependency #29

dmi3kno opened this issue May 30, 2018 · 2 comments

Comments

@dmi3kno
Copy link
Contributor

dmi3kno commented May 30, 2018

This is probably not an issue, but rather a suggestion and an invitation to discussion.

ImageMagick installation on Windows may be ... a little involved. Is there a reason you want to keep dependency on magick in tesseract? You only seem to use magick for saving magick images, so if you save them using other tools, you are afraid of losing class (do you even need to save them, as argued in #28)? I imagine that removing dependency on magick will help wider adoption of tesseract, particularly by folks to tend to use imager and other R image processing platforms

@jeroen
Copy link
Member

jeroen commented May 30, 2018

The magick package on windows is self contained and does not depend on imagemagick. Did you try:

install.packages("magick")

Also tesseract does not depend on magick, it is a suggests which means that it is only needed for running examples.

@jeroen jeroen closed this as completed May 30, 2018
@dmi3kno
Copy link
Contributor Author

dmi3kno commented May 30, 2018

I apologize for asking. You are right that magick is self-contained. I would love to hear your view on #28 re: TMP images. Thank you again and sorry for my lack of diligence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants