-
Notifications
You must be signed in to change notification settings - Fork 47
feat: updated complex fonts #176
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Peter Staar <[email protected]>
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
|
|
✅ DCO Check Passed Thanks @PeterStaar-IBM, all your commits are properly signed off. 🎉 |
|
Hi @PeterStaar-IBM, are you still actively working on this? Every once in a while we encouter documents where the parsed text looks somewhat like this: It is particularly prevalent in documents that are created with corporate fonts. Would love to see a general fix for this issue (if possible) as it may tackle a variety of different parsing issues. |
yes, it is ongoing work. If you have pdf's with broken fonts, please add an example. It is the only way to fix it. |
|
@PeterStaar-IBM I gave you a ping on LinkedIn ;) |
|
@simonschoe thanks, will follow up! |
need to test on: https://www.provinzial-online.de/export/sites/wpv/_resources/download/privat_versicherungen/580-17-PIB_Unfall-Provinzial-IPID_Stand-12.2016.pdf