Font attributes incorrect even when font is properly identified (is_italic, is_serif, etc.)
#907
Comments
|
Given that the amount of information retrieved for Even if this feature worked correctly (in that it accurately reported what Tesseract finds), it would still only be useful in extremely niche circumstances, if ever. Tesseract LSTM (the default) does not perform font detection at all, and Tesseract Legacy performs poorly with font identification, so this information would either be missing or inaccurate even if this bug was fixed. |
|
I looked into this, and it is caused by a typo in the function that gets boolean pointers. No booleans will be reported correctly using the current function. This should be fixed as it is a broader issue, regardless of whether or not this data is cut from a future version. |
|
Closing as this was resolved in |
The
blocksoutput format includes various font attributes on thewordlevel, includingis_italicandis_serif. These do not appear to be functioning properly, and seem to always returnfalse, even when using the Legacy model and when font identification worked correctly.For example, when running recognition with the Legacy engine on the image below, the font is correctly recognized as an italic/serif font (
Times_New_Roman_Italic). However, despite this, theis_italicandis_serifattributes are both false.If this is an issue with Tesseract.js/Tesseract.js-core we should fix. If it is an issue on the Tesseract side, where the information is always incorrect, these should be removed from our output to avoid confusion (in the next major version).
Note that this is distinct from general accuracy issues with Tesseract font recognition, or the fact that it only runs on Legacy, which are outside of the scope of this repo. This issue is specific to cases where Tesseract correctly identifies the font but is still returning the wrong font attributes.
The text was updated successfully, but these errors were encountered: