| Summary: | media-libs/fontconfig-infinality rejects all Type-1 fonts, so ghostscript based applications cannot find fonts | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | José Romildo Malaquias <jrmalaq> |
| Component: | [OLD] Library | Assignee: | Gentoo Fonts Team <fonts> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bircoph, cruzki123, endymion+gentoo, eugene.shalygin, ganastasiouGR, gentoo, nikoli, pacho, printing, the.paraw |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=620148 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Output of "emerge --info" | ||
|
Description
José Romildo Malaquias
2012-09-28 13:20:35 UTC
Created attachment 325214 [details]
Output of "emerge --info"
Following some advice from the infinality forum at http://www.infinality.net/forum/viewtopic.php?t=238, after commenting the lines in /etc/fonts/infinality/infinality.conf that causes the rejection of type1 fonts, ghostscript works again. Same problem happens to me when building dev-lang/nasm-2.10.05[doc] with infinality fonts enabled: $ ps2pdf nasmdoc.ps nasmdoc.pdf Error: /invalidfont in /findfont Operand stack: Times-Italic-NASM Times-Italic Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --n ostringval-- false 1 %stopped_push 1894 1 3 %oparray_pop 1893 1 3 %oparray_pop 1877 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push -- nostringval-- --nostringval-- 1852 2 3 %oparray_pop Dictionary stack: --dict:1171/1684(ro)(G)-- --dict:0/20(G)-- --dict:98/200(L)-- Current allocation mode is local Last OS error: No such file or directory Current file position is 3090 GPL Ghostscript 9.06: Unrecoverable error, exit code 1 Proposed solution works for me. It is a good idea to have Type 1 fonts allowed by default and warn users about possible implications. I can confirm this. Exact same problem happens to me. Same failure of ps2pdf, but also of Okular when opening ps files. The workaround provided indeed works, and the problem seems to be the one identified in Comment 2, namely that infinality bans all Type-1 fonts. I can confirm this, also that the workaround pointed to in Comment 2 does the trick. Is there a way to block type-1 for screen rendering, but not for other purposes? I just spent a few hours debugging an issue with CUPS spewing blank pages from app-text/enscript. I finally found the same page as https://bugs.gentoo.org/show_bug.cgi?id=436500#c2 did, which fixed the issue. It took me hours to associate the problem with the infinality fonts. It seems to me that this is a fairly widespread problem among numerous applications, and deserves at least a warning being added to the infinality ebuild output. +*fontconfig-infinality-20130404 (05 Apr 2013) + + 05 Apr 2013; Ben de Groot <yngwin@gentoo.org> + +fontconfig-infinality-20130404.ebuild, files/Xresources: + Version bump, thanks to lxnay for rolling the tarball. + Fixes bugs #456652 (version bump), #430550 (broken link), #452860 (wrong + Xresources syntax), #462924 (multiple values in test warning), and adds + a warning about type-1 fonts (#436500). Implements readme.gentoo eclass. + Apologies for the delay. *** Bug 472520 has been marked as a duplicate of this bug. *** *** Bug 546630 has been marked as a duplicate of this bug. *** (In reply to Ben de Groot from comment #7) > +*fontconfig-infinality-20130404 (05 Apr 2013) > + > + 05 Apr 2013; Ben de Groot <yngwin@gentoo.org> > + +fontconfig-infinality-20130404.ebuild, files/Xresources: > + Version bump, thanks to lxnay for rolling the tarball. > + Fixes bugs #456652 (version bump), #430550 (broken link), #452860 (wrong > + Xresources syntax), #462924 (multiple values in test warning), and adds > + a warning about type-1 fonts (#436500). Implements readme.gentoo eclass. > + Apologies for the delay. Ben, from my point of view it would be better to install a conf file that doesn't break ghostscript like in just seen bug 546630 instead of telling people to fix it manually :/ What do you think? Thanks :) Ah, no problem, it looks to be solved in ghostscript side with its 9.15-r1 :O Sorry for the noise |
