However, I am willing to contribute a fix if I can get confirmation that it will be merged (there appears to be a few stale PRs here with no responses on them). Unfortunately I can't provide a link to reproduce right now, as Adobe Fonts are privately licensed so I cannot include the Proxima Nova font in an example. Current BehaviorĮmbedding the Proxima Nova font fails with the following error:Įrror loading remote css Synta圎rror: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the delimiters. The resulting image should look exactly like the HTML it was extracted from. This problem occurs because a fallback font is selected that has wider glyphs for some characters, causing the text to overflow since the element is given a fixed width during the conversion. in the field labelled TextGeneral, the full text is T qq, which should more than comfortably fit in that enormous grid cell. In a single font file, it contains all the weights and styles of Proxima Novaplus any style between them along any of three dimensions (weight, width, and slant) without the distortion that comes with artificial manipulation such as squeezing, stretching, or slanting. I can't figure out what changed recently. I can save documents as PDFs just fine as long as they don't contain Proxima Nova. I get the font as an asset from Creative Cloud.
Here's a screenshot showing one that has an ellipsis on an element with `display: -webkit-box': Proxima Vara is a variable version of the Proxima Nova type family. All of a sudden I'm having trouble creating a PDF for a document that uses Proxima Nova. This leads to some strange issues with elements that are not fixed width in the HTML but end up with a fixed width due to cloning of computed styles for elements. When using a particular font from Adobe Fonts, in this case Proxima Nova, I don't see the correct font rendered in the image when I call toSVG().