-
Notifications
You must be signed in to change notification settings - Fork 3
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
Incorrect charset encoding when export to PDF #36
Comments
@ulion Hi, can you share with us a link to your original Gitbook online and a copy of the Export zip so we can look into it. @scottsteinbeck This may be related to Lucee no longer bundling all the fonts it used to. |
Thanks @ulion I have reproduced your issue, but after spending a few hours on this, I'm having issues getting my PDF library to render these characters correctly. I've put in some messages for the library maintainers to see if I can get it working. I'm unclear whether it's related to charset or the font in use. |
Thank you for the explanation. So what's is the PDF library you are using? |
@ulion Heh, that's a complicated question. CommandBox CLI is written in a JVM language called CFML and uses a FOSS engine called Lucee Server which bundles a Java PDF library inside itself as a first-class feature. We're also in the process of updating CommandBox to a new major version of Lucee Server which also adds a wrinkle as the latest version switched from the Java iText library I think to Flying Saucer (PD4ML). The version of box you're on uses the older PDF lib that produces gibberish but our testing has also found that Flying Saucer has separate issues of its own which is simply not even outputting the unicode chars at all! We didn't have any luck getting your PDF to render correctly on either library, but the extra layers of my code, Lucee's code, and the underlying Java lib makes it tricky to determine where the issue lies. |
the generated html is just fine, but the PDF is not generated in correct charset. Any setting for correct this?
The text was updated successfully, but these errors were encountered: