Re: [Xpert]Problems with Type1 big fonts
AH> There's a problem with this at the moment. If you build a static AH> server you get two font renderers registered to deal with .pfa/.pfb AH> fonts. Solution Juliusz - is it just to disable Type1 for static builds AH> because it's too buggy ? For now, all I can tell for sure is that I do disable Type 1 in my personal build. This has the side-effect of disabling support for CIDFonts. Details about my medium-term ideas on the subject are in a different message. I am sorry for not having done that yet, and I apologise in advance for not being able to do it right now. Juliusz ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
AA> Warning: font renderer for ".pcf" registered more than once For some reason that I don't understand, all renderers get registered twice in the modular server. FreeType is not at fault. I've added this warning to fontfile/renderer.c in the hope that somebody competent will end up looking into that. Juliusz ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
On Wed, Oct 23, 2002 at 08:19:31PM +0200, Juliusz Chroboczek wrote: >AA> Warning: font renderer for ".pcf" registered more than once > >For some reason that I don't understand, all renderers get registered >twice in the modular server. FreeType is not at fault. I haven't seen any evidence of all renderers being registered twice. The "bitmap" module is always loaded by the core server, so also specifying it in the Modules section of the config file may lead to it being registered twice. >I've added this warning to fontfile/renderer.c in the hope that >somebody competent will end up looking into that. I modified that a little to only print the warnings for the first server generation -- otherwise you see them every time the X server recycles. I also modified the registration code to clear the list of renderers at the start of each new server generation. David ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
On Mon, 21 Oct 2002, 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 ? I think the module server does that too; I get Warning: font renderer for ".pcf" registered more than once Warning: font renderer for ".pcf.Z" registered more than once Warning: font renderer for ".pcf.gz" registered more than once Warning: font renderer for ".snf" registered more than once Warning: font renderer for ".snf.Z" registered more than once Warning: font renderer for ".snf.gz" registered more than once Warning: font renderer for ".bdf" registered more than once Warning: font renderer for ".bdf.Z" registered more than once Warning: font renderer for ".bdf.gz" registered more than once Warning: font renderer for ".pmf" registered more than once Warning: font renderer for ".pfa" registered more than once Warning: font renderer for ".pfb" registered more than once in my log at the moment. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
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 ? Alan. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
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. U> Any other solution ? Get the new FreeType driver from XFree86 CVS and recompile it for your system. Or else switch to current CVS. Sorry, there are no easier solutions at this time. Juliusz ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
On Mon, 21 Oct 2002, Alan Hourihane wrote: > That's probably because your loading "Type1" and "FreeType" in your > Module section. What does your module section look like ? Correct. # these 5 are fonts # tt and freetype are mutually incompatible # Load "tt" Load "freetype" Load "bitmap" Load "speedo" Load "type1" Are tt and freetype still incompatible ? -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
On Mon, Oct 21, 2002 at 10:39:22PM +0100, Dr Andrew C Aitchison wrote: > On Mon, 21 Oct 2002, Alan Hourihane wrote: > > > That's probably because your loading "Type1" and "FreeType" in your > > Module section. What does your module section look like ? > > Correct. > # these 5 are fonts > # tt and freetype are mutually incompatible > # Load "tt" > Load "freetype" > Load "bitmap" > Load "speedo" > Load "type1" > > Are tt and freetype still incompatible ? Yes, and now type1 isn't needed if your using freetype. Alan. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
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
Re: [Xpert]Problems with Type1 big fonts
> "David" == David Dawes <[EMAIL PROTECTED]> writes:
David> Unless the old Type1 backend can unreservedly be replaced by
David> the new FreeType2 backend, then it should be disabled, and
David> maybe even a "fake" type1 font module created for the modular
David> build so that existing configurations don't break. If there
David> are still reasons for wanting the old backend, then it needs to
David> be configurable, at least at build-time.
I beleive the old type1 backend is still required for type1 cid fonts.
It would be useful to have an easy way of compiling it w/ the moral
equivilent of:
--- t1funcs.c.~1~ Mon Feb 18 15:51:57 2002
+++ t1funcs.c Tue Oct 22 00:57:09 2002
@@ -1434,16 +1434,20 @@
FontRendererRec CIDRendererInfo[] = {
{ ".cid", 4, NULL, CIDOpenScalable,
+NULL, CIDGetInfoScalable, 0, CAPABILITIES },
+ { ".CID", 4, NULL, CIDOpenScalable,
NULL, CIDGetInfoScalable, 0, CAPABILITIES }
};
#endif
-#ifdef BUILDCID
+#ifndef BUILD_ONLY_CID
+# ifdef BUILDCID
FontRendererRec Type1RendererInfo[] = {
-#else
+# else
static FontRendererRec renderers[] = {
-#endif
+# endif
{ ".pfa", 4, NULL, Type1OpenScalable,
NULL, Type1GetInfoScalable, 0, CAPABILITIES },
{ ".pfb", 4, NULL, Type1OpenScalable,
NULL, Type1GetInfoScalable, 0, CAPABILITIES }
};
+#endif
so that it will load .cid and .CID files but leave .pfa or .pfb for
the ft2 driver.
-JimC
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problems with Type1 big fonts
On Tue, Oct 22, 2002 at 12:59:34AM -0400, James H. Cloos Jr. wrote:
>> "David" == David Dawes <[EMAIL PROTECTED]> writes:
>
>David> Unless the old Type1 backend can unreservedly be replaced by
>David> the new FreeType2 backend, then it should be disabled, and
>David> maybe even a "fake" type1 font module created for the modular
>David> build so that existing configurations don't break. If there
>David> are still reasons for wanting the old backend, then it needs to
>David> be configurable, at least at build-time.
>
>I beleive the old type1 backend is still required for type1 cid fonts.
>It would be useful to have an easy way of compiling it w/ the moral
>equivilent of:
>
>--- t1funcs.c.~1~ Mon Feb 18 15:51:57 2002
>+++ t1funcs.c Tue Oct 22 00:57:09 2002
>@@ -1434,16 +1434,20 @@
> FontRendererRec CIDRendererInfo[] = {
> { ".cid", 4, NULL, CIDOpenScalable,
>+NULL, CIDGetInfoScalable, 0, CAPABILITIES },
>+ { ".CID", 4, NULL, CIDOpenScalable,
> NULL, CIDGetInfoScalable, 0, CAPABILITIES }
> };
> #endif
>
>-#ifdef BUILDCID
>+#ifndef BUILD_ONLY_CID
>+# ifdef BUILDCID
> FontRendererRec Type1RendererInfo[] = {
>-#else
>+# else
> static FontRendererRec renderers[] = {
>-#endif
>+# endif
> { ".pfa", 4, NULL, Type1OpenScalable,
> NULL, Type1GetInfoScalable, 0, CAPABILITIES },
> { ".pfb", 4, NULL, Type1OpenScalable,
> NULL, Type1GetInfoScalable, 0, CAPABILITIES }
> };
>+#endif
>
>so that it will load .cid and .CID files but leave .pfa or .pfb for
>the ft2 driver.
A run-time method for assigning font file suffixes to backends would
take care of this too, at least for the XFree86 server (and maybe also
the font server?). Is anyone interested in looking into that?
For other servers, it's easiest to handle it at build time, and it would
be useful to imake switches to determine common useful combinations like
this. Any takers for implementing this?
David
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
