-
Notifications
You must be signed in to change notification settings - Fork 4
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
PDF specification #2
Comments
Thanks for finding this and sending such a helpful writeup! I think I've found and fixed the issue, though it only happens with some inputs, and I haven't found one which reproduces your issue. Are you able to test a build for me? If you use Linux, this is a test build I just made: https://rescribe.xyz/tmp/rescribe-fixissue2-v1 - If you'd rather some other OS, let me know and I can make a test for you (or you can build one yourself from the |
Thank you for addressing this, I really appreciate it! I tested the new build and
The resulting pdf imports into r fine, but if I (just to see, if it gives any suggestions) repair it again with gs, I get the following message:
Thanks again! |
Thanks for checking and reporting that the original issue was fixed! I have just released v1.3.0, which includes the fix, and includes the embedded training data as other proper releases do (well done figuring out how to get that test build to work without it, by the way!) Regarding the new issue you found, |
Thanks again! When looking with |
I have some issues with the pdf that rescribe creates. I'm using the latest version (1.2.0) and having trouble importing the produced text into r with pdftools. Error message is:
When repairing the pdf with ghostscript (with options -sDEVICE=pdfwrite -dPDFSETTINGS=/prepress) it gives the following advice:
After repairing the file with gs the import into r with pdftools works fine.
The text was updated successfully, but these errors were encountered: