-
Notifications
You must be signed in to change notification settings - Fork 499
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
Unable to produce PDF due to prawn font/ image related issue #2415
Comments
Given the location of this error, this looks like a problem in Prawn itself (and perhaps due to bad data provided by ttfunk). Here's the code at the line in question:
This is not something we can deal with in Asciidoctor PDF. You'll need to file the issue in Prawn (or more likely, ttfunk). I recommend trying to reduce this to a reproducible scenario so that the authors are able to debug it. Another approach would be to open the fonts in FontForge and resave them. It's possible one of the fonts is malformed somehow. Sometimes reexorting it will fix it. |
Thank you for your reply. Solved the issue by replacing the
It works now without giving me error. |
Glad to hear it! Btw, if you extend the default theme, you don't have to declare the built-in fonts as it will use them by default. See https://docs.asciidoctor.org/pdf-converter/latest/theme/create-theme/#extend-default If you need to add your own fonts in addition to the default fonts, then you would use the |
Here is the version of
asciidoctor-pdf
I am using:I have been using the
asciidoctor-pdf
for quite some time. I don't remember the earlier version ofasciidoctor-pdf
I was using. But recently upgraded my system hardware and installed the application fresh. Following is the command I use for generating PDF file using a custom theme file:-However, it produces the following error.
Here is the content of
data/fonts
directory:and here is the custom theme font section I use:
I looked at the similar error reported at #2349 but it appears to be not related to it as I have not included any SVG image in my draft book. I used the same command earlier (around 4-5 months back) as well but that time, it produced PDF without error.
The text was updated successfully, but these errors were encountered: