-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Unicode fonts (utf-8) in Safari (iOS and OSX) error #3190
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
Comments
Please provide a complete repro, so we can reproduce the issue. |
Hi Lukas, here is a complete repro:
|
Is this repro adequate? |
Looks good at first glance, thanks. I haven't found the time to look into this so far, sorry. |
Ok, |
Does it only look broken when opening the PDF in Safari or the MacOS file preview? Or is the PDF generated in Safari different than when generated with Chrome? We've had similar issues in the past. Please try opening a file generated in Safari in Adobe Reader or Chrome. Also: which jsPDF version are you using? |
I'm using jsPDF version 2.1.1 The PDF generated in Safari desktop or Safari mobile (iPhone) is different than Chrome on desktop or Android device, Firefox on desktop or on Android device & Edge on desktop - in a way that utf-8 hebrew characters are displayed as gibberish. |
Please attach two files: one that's generated in Safari and is broken, one that's generated in Chrome and is not broken. |
Please also try updating to 2.3.1 |
This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant. |
Hi guys
We are using the
jsPDF.text(text, x, y, optionsopt, transform)
in order to insert text to the pdf document.
Since we need to support Hebrew language we used the following api calls to add unicode fonts:
I downloaded *.ttf file with Hebrew fonts and it all works well on all major browsers: Chrome, Firefox & Edge.
However to my regret on Safari browser whether on iPhone or Macbook it gives me gibberish text... :-(
What should i do?
The text was updated successfully, but these errors were encountered: