On Mon, Oct 21, 2002 at 06:10:26PM +0100, Alan Hourihane wrote: >On Mon, Oct 21, 2002 at 07:01:23PM +0200, Juliusz Chroboczek wrote: >> U> Does anybody know any solution around the problem of X crashing with >> U> Type1 big fonts ? >> >> The current Type 1 backend will no longer be the default in 4.3.0. >> The new Type 1 backend does not have this problem. > >There's a problem with this at the moment. If you build a static >server you get two font renderers registered to deal with .pfa/.pfb >fonts. Solution Juliusz - is it just to disable Type1 for static builds >because it's too buggy ?
Unless the old Type1 backend can unreservedly be replaced by the new FreeType2 backend, then it should be disabled, and maybe even a "fake" type1 font module created for the modular build so that existing configurations don't break. If there are still reasons for wanting the old backend, then it needs to be configurable, at least at build-time. Also, I'd really like to see some resolution to the separate "FreeType" and "X-TT" backends for TrueType fonts. As it is now, if someone chooses "X-TT", they will still need the old Type1 backend for Type1 fonts regardless of other considerations. Is it still not possible to resolve the issues that led to two TrueType backends in the first place? As it is now, the first renderer registered for a suffix is the one that gets used. I'm not sure what order they're registered in right now for the static build. If we want to provide more flexibility in allowing the user to control what font suffixes are handled by what backend, there would need to be some type of run-time configurability. For the modular server this could probably be done fairly easily via the XF86Config file. David _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
