David Dawes wrote: > >> How does 2.1.4's handling of Type1 fonts compare with the Type1 > >> backend? > > > >Do you mean xc/lib/font/Type1/ vs xc/lib/font/FreeType/ ? In my opinion > >the xc/lib/font/Type1/ should be retired since it causes server crashes > >such as "Fatal server error: Beziers this big not yet supported" and > >seems to have huge problems with rasterisation at higher resolutions. At > > Yeah, FatalError() from a font backend is bad. It ought to print > a warning and return a relevant error code rather than killing the > whole server.
Unfortunately it isn't easy to handle that kind of error in a simple way... you can use setjmp/longjmp() for that case but that doesn't do any cleanup nor will it reset the Type1 engine... > >least for PS Type1 fonts the current code in xc/lib/font/FreeType/ is > >mature[1] enougth to let it handle all PS Type1 fonts (*.pfa, *.pfb). > >Unfortunately there are still the CID fonts where the FreeType backend > >and the FreeType library do not offer support for... but the question is > >- do we still need CID fonts when we have TTF/OTF font support ? > > I recently tracked down a problem report related to CID fonts, so I guess > someone is using them. What about handling *.pfa/*.pfb via the FreeType backend and let CID fonts be handled via the old Type1 backend ? At least the risk of hitting the "Beziers this big not yet supported"&co. minefield will be greatly lowered - and the workaround would be to remove the CID fonts from the font path (which doen't harm most users... removing all PS Type1 fonts from the font path will harm LOTS of users... ;-(). ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 2426 901568 FAX +49 2426 901569 (;O/ \/ \O;) _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
