-
Notifications
You must be signed in to change notification settings - Fork 498
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
data:image/svg+xml;base64,... does not seem to be supported #1423
Comments
It looks like the data URI scheme isn't support for SVGs. The fix seems simple, so I'll plan to add it in the next release. Thanks for reporting! |
Thanks for quick response!
|
How do I install the version updated after this commit? I've installed asciidoctor-pdf using Error Code: Or the above command still points to package that doesn't include the fix yet?
|
The issue labels the version in which the issue is fixed. If that version is not yet available on rubygems.org, then the fix is only in the development tree (aka master). It's marked as 1.5.0 and 1.5.0 has not been released. (Though likely it will get moved to a beta or release candidate). The contributing guide describes how to install the gem from the development tree. See https://github.com/asciidoctor/asciidoctor-pdf/blob/master/CONTRIBUTING-CODE.adoc#development |
Used
|
The encoded data you provided is not a complete SVG. I assure you that if the encoded data is a valid SVG, it will work when using Asciidoctor PDF 2.3.x. If you need help using Asciidoctor PDF, please ask in the community chat at https://chat.asciidoctor.org. The issue tracker is not a support portal. |
Using gradle plugin:
I keep getting the following error as if reading data-uri is not supported:
In place of the image, the generated PDF shows:
As a workaround, I could extract the image data and write it to a temporary file, but that is not very convenient for me. Note that the use of image data-uri's in .adoc works as expected when generating HTML output. In both cases, .adoc file has
:data-uri:
The text was updated successfully, but these errors were encountered: