You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And now the ghostscript fonts are working. At a minimum the enableGhostscriptFonts documentation should mention this requirement. Even better would be if enableGhostscriptFonts enabled the option, or at least gave a warning or error if allowType1 is not true.
I am leaving this issue open since enableGhostscriptFonts = true is not sufficient to enable the ghostscript fonts.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Search for maintainers and people that previously touched the related code and @ mention them in a comment.
Issue description
I have
enableGhostscriptFonts = true
in my config,The ghostscript fonts are visible to
fc-cache
andfc-cat
, but notfc-list
orfc-match
.When I run
fc-cache -rv
the fonts are found in the ghostscript directory:And
fc-cat | grep Nimbus
shows multiple matches such as:But when I run
fc-list
none of the ghostscript fonts show up:And
fc-match Nimbus
does not match:Technical details
The text was updated successfully, but these errors were encountered: