Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Scrambled rendering with NotoSansTC-Regular.otf
See original GitHub issuerelated: #243, googlei18n/noto-cjk#81 block: parlr/ruby-font-creator#29
I met rendering problems when using text-to-svg (shrhdk/text-to-svg#22, shrhdk/text-to-svg#23) with the NotoSansTC-Regular.otf.
Drilling down it appears text-to-svg is based on opentype.js.
Expected
This is for reference, I find that DroidSansFallbackFull.ttf worked fine.
| key | value |
|---|---|
| font | DroidSansFallbackFull.ttf |
| text | 㐅㐆丰wǔyǐnfēng |
Actual (with NotoSans)
I tested on opentype.js online demo and the result is scramble too (see below):
| key | value |
|---|---|
| font | NotoSansTC-Regular.otf |
| text | 㐅㐆丰wǔyǐnfēng |
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
OTF fonts rendering scrambled glyphs or not rendering #1203
It seems like there are two kinds of issues I run into when using certain OTF fonts within Prawn to generate PDFs. The...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We now parse CID-keyed fonts correctly!
The new version 0.7.0 includes the fix (with a big thanks to @tshinnic for the initial implementation).
It seems like this is a CID-keyed font, which we do not yet have support for. I’ll see what I can do.