-
Notifications
You must be signed in to change notification settings - Fork 751
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
PixConverter Unavailable for NET CORE #477
Comments
I suppose that caused by the fact that System.Drawing is not built into .NET Core standard library, so all the code related to bitmap is surrounded by However, System.Drawing is now accessible as a nuget package, so you can probably copy-paste all the neccessary methods and classes from sources into your project. Alternatively, it should probably be possible to add System.Drawing under .NET support here without too much effort and compile fixed version for yourself. |
Actually, people have already done it. |
Note that the |
As far as I understand, Bitmap, even if limited, is very useful as common representation of image. I guess most imaging libraries support conversion to/from bitmap. At least that is probably better than doing conversion by saving image to temporary storage (memory or disk) and then loading it back using another library and much easier than writing complicated conversion code with direct memory access. |
My experience is that Tesseract is not as effective at recognition on Bitmaps as it is with Leptonica direct load from file. We haven’t attempted to learn why. We just stopped using Bitmap.
|
…ract.Drawing Created a new package called Tesseract.Drawing to support integration with System.Drawing from .net core, or any other target that supports .netstandard2 and the System.Drawing.Common package. This option was chosen so that core Tesseract package doesn't include unnecessary dependencies which could cause issues on other platforms.
FYI I've split of a new package Tesseract.Drawing, currently in beta, to support using Bitmaps in .net core if they are required. However I would agree with @tdhintz that just using pix should be preferred if possible (not sure why the results would be different though, odd). |
The PixConverter and other related seems to not be available when I reference the latest version of the Tesseract package.
Is there any reason for it?
The text was updated successfully, but these errors were encountered: