Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
David Dawes wrote: 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... Yeah, it wouldn't be simple. Disabling the Type1 engine completely when one of these errors happens would even be preferable to aborting the whole X server. What about removing the CID support from the default setup ? [snip] What about handling *.pfa/*.pfb via the FreeType backend and let CID fonts be handled via the old Type1 backend ? That is the current default behaviour. Thanks for the hint (which helped narrowing down the issue... I thought I removed all CID fonts from my Linux machine but somehow I found another bunch... after removing the fonts the Xfree86 server is rock-solid again... :) Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, CJAVASunUnix programmer /O /==\ O\ TEL +49 2426 901568 FAX +49 2426 901569 (;O/ \/ \O;) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
Hi! What about updating the FreeType code shipped with Xfree86 to version 2.1.7 before Xfree4.4.0 gets released (see bugzilla RFE below) ? Original Message Subject: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7... Date: Mon, 01 Dec 2003 23:51:57 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=931 Summary: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7... Product: Client Libraries Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Freetype AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] RFE: Update xc/extras/freetype2/ to Freetype 2.1.7 (current version seems to be V2.1.4). -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
Does fontconfig work with it yet? When FreeType 2.1.7 was announced I tried building it, then building fontconfig 2.2.1 and finding fontconfig couldn't build since it didn't use the #include MACROs preferred by the FreeType developers, and now required to use the FreeType headers in 2.1.7. I haven't had a chance to go back and check if fontconfig CVS was fixed. -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc.- Sun Software Group User Experience Engineering: G11N: X Window System Roland Mainz wrote: Hi! What about updating the FreeType code shipped with Xfree86 to version 2.1.7 before Xfree4.4.0 gets released (see bugzilla RFE below) ? Original Message Subject: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7... Date: Mon, 01 Dec 2003 23:51:57 -0500 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter your comments there. http://bugs.xfree86.org/show_bug.cgi?id=931 Summary: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7... Product: Client Libraries Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Freetype AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] RFE: Update xc/extras/freetype2/ to Freetype 2.1.7 (current version seems to be V2.1.4). -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
On Fri, Dec 05, 2003 at 03:16:23AM +0100, Roland Mainz wrote: Hi! What about updating the FreeType code shipped with Xfree86 to version 2.1.7 before Xfree4.4.0 gets released (see bugzilla RFE below) ? The feature freeze was over 6 weeks ago. The integration phase is over. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
On Fri, Dec 05, 2003 at 04:58:07AM +0100, Roland Mainz wrote: David Dawes wrote: What about updating the FreeType code shipped with Xfree86 to version 2.1.7 before Xfree4.4.0 gets released (see bugzilla RFE below) ? The feature freeze was over 6 weeks ago. The integration phase is over. I wasn't considering this as feature, more as a way to get rid of the problems with PS Type1 fonts in the tree (and likely some other stuff was fixed, too) ... 25% of the FreeType changelog since 2.0 is for changes since 2.1.4. For integration purposes, that counts as a feature. ... OK... agreed ;-( If there are specific isolated fixes that would address the Type1 issues, they could certainly be considered. There is a simple fix for the FreeType Type1 parser which corrects the problem when someone has placed PostScript comments into Type1 fonts... maybe that's worth enougth for a backport to Xfree86 CVS... or not... If it's a problem people are running into, then it might be worth it. 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. 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. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
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 supportedco. 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, CJAVASunUnix programmer /O /==\ O\ TEL +49 2426 901568 FAX +49 2426 901569 (;O/ \/ \O;) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Fwd: [Bug 931] New: RFE: Update xc/extras/freetype2/ to Freetype 2.1.7...]
On Fri, Dec 05, 2003 at 06:04:54AM +0100, Roland Mainz wrote: 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... Yeah, it wouldn't be simple. Disabling the Type1 engine completely when one of these errors happens would even be preferable to aborting the whole X server. 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 ? That is the current default behaviour. David -- David Dawes developer/release engineer The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
