I am trying to troubleshoot a font mixup on my Debian Sid machine. I am having trouble with the "Courier 10 Pitch" font that is in the xfonts-scalable package. The following packages are installed: XFree86 4.2.1-6 xfonts-scalable 4.2.1-6 Fontconfig 2.2.0-2 For some reason, the regular font is itallic, and the bold itallic font is just bold, as displayed by the KDE font configuration, GNOME2 font-config and Eclipse''s internal font configuration. Evolution 1.2.4 finds the correct fonts (id''ed as bitstream-courier), but they are not AA, and it uses a different font selection mechanism. The itallic and bold versions are just fine. I have checked the entries in the cache files and font.dir files, and nothing strange jumps out. I''ve also verified (using Konqueror''s built-in font previewing feature) that the files actually contain the appropriate fonts. How can I troubleshoot this problem? If fontconfig isn''t responsible for the mixup, do you have any ideas what would be? Thanks, Jonathan Fontpath: (from `xset q`) /home/jonathan/.gnome2/share/cursor-fonts, (MT) /usr/lib/X11/fonts/Type1, /usr/lib/X11/fonts/Speedo, /usr/lib/X11/fonts/misc, /usr/lib/X11/fonts/100dpi, /usr/lib/X11/fonts/75dpi, /usr/share/fonts/truetype, /usr/share/fonts/truetype/ttf-bitstream-vera, /usr/share/fonts/truetype/freefont, /home/jonathan/.gnome2/share/fonts (MT) Excerpt from /usr/lib/X11/fonts/Type1/fonts.dir: c0419bt_.pfb -bitstream-courier-medium-r-normal--0-0-0-0-m-0-iso8859-1 c0582bt_.pfb -bitstream-courier-medium-i-normal--0-0-0-0-m-0-iso8859-1 c0583bt_.pfb -bitstream-courier-bold-r-normal--0-0-0-0-m-0-iso8859-1 c0611bt_.pfb -bitstream-courier-bold-i-normal--0-0-0-0-m-0-iso8859-1 Excerpt from/usr/lib/X11/fonts/Type1/fonts.cache-1 (charset= and langhave been snipped): "c0419bt_.pfb" 0 "Courier 10 Pitch:style=Regular:slant=0:weight=80:spacing=100:foundry=bitsteam:index=0:outline=True:scalable=True::fontversion=0" "c0582bt_.pfb" 0 "Courier 10 Pitch:style=Italic:slant=0:weight=80:foundry=bitsteam:index=0:outline=True:scalable=True: "c0583bt_.pfb" 0 "Courier 10 Pitch:style=Bold:slant=0:weight=200:spacing=100:foundry=bitsteam:index=0:outline=True:scalable=True: "c0611bt_.pfb" 0 "Courier 10 Pitch:style=Bold Italic:slant=0:weight=200:spacing=100:foundry=bitsteam:index=0:outline=True:scalable=True: /usr/lib/X11/fonts/Type1/fonts.scale and fonts.alias do not contain referances to these fonts.
Around 19 o''clock on May 24, Jonathan Brandmeyer wrote:> I am > having trouble with the "Courier 10 Pitch" font that is in the > xfonts-scalable package. The following packages are installed: > > XFree86 4.2.1-6 > xfonts-scalable 4.2.1-6 > Fontconfig 2.2.0-2 > > For some reason, the regular font is itallic, and the bold itallic font > is just bold, as displayed by the KDE font configuration, GNOME2 > font-config and Eclipse''s internal font configuration.Fontconfig may have extracted inaccurate information about this font; you can check that with the ''fc-list'' program: $ fc-list ''Courier 10 Pitch'' family style weight slant The output should be: Courier 10 Pitch:style=Bold Italic:slant=100:weight=200 Courier 10 Pitch:style=Italic:slant=100:weight=80 Courier 10 Pitch:style=Regular:slant=0:weight=80 Courier 10 Pitch:style=Bold:slant=0:weight=200 If you aren''t seeing ''slant=100'' for the italic versions, then fontconfig is misdetecting these fonts. Fontconfig had problems correctly identifying Type1 fonts which have been fixed in current CVS (at least, that''s what generated the output above). -keith
Around 14 o''clock on May 26, Jonathan Brandmeyer wrote:> I''m going to file a bug with the debian maintainer to see if a patch can > be backported. What would point him in the best direction to find it in > CVS? (eg files/directories affected, etc.)Any problems are almost certainly in fontconfig/src/fcfreetype.c. There is a 2.2 branch which the debian maintainer can commit to in fontconfig CVS; we can do a fontconfig 2.2 release when we manage to figure out the problem. -keith
On Mon, 2003-05-26 at 14:49, Jonathan Brandmeyer wrote:> and that made all of the fonts non-itallic. That was enough for now, > since I don''t use the itallic versions. Running fc-list as above shows > that the slants are all zero.Just to clarify, I meant all of the Courier 10 Pitch fonts are non-itallic. I haven''t noticed problems with any others. -Jonathan
On Mon, 2003-05-26 at 13:54, Keith Packard wrote:> $ fc-list ''Courier 10 Pitch'' family style weight slant > > The output should be: > > Courier 10 Pitch:style=Bold Italic:slant=100:weight=200 > Courier 10 Pitch:style=Italic:slant=100:weight=80 > Courier 10 Pitch:style=Regular:slant=0:weight=80 > Courier 10 Pitch:style=Bold:slant=0:weight=200 > > If you aren''t seeing ''slant=100'' for the italic versions, then fontconfig > is misdetecting these fonts. Fontconfig had problems correctly > identifying Type1 fonts which have been fixed in current CVS (at least, > that''s what generated the output above).That seems to be the problem here. I ran `dpkg-reconfigure fontconfig` and that made all of the fonts non-itallic. That was enough for now, since I don''t use the itallic versions. Running fc-list as above shows that the slants are all zero. I''m going to file a bug with the debian maintainer to see if a patch can be backported. What would point him in the best direction to find it in CVS? (eg files/directories affected, etc.) Thanks, Jonathan
Around 22 o''clock on Jun 28, Dmitry Karasik wrote:> How one would prevent ''polygon request too large'' > Xlib error? Is Xft capable of breaking the glyph in > smaller polygons, or probably there are X extensions > that allow large X requests?You need an updated version of the Xrender library -- there were bugs in that caused it to fail with larger glyphs. The Xrender library and headers are available as packages at fontconfig.org in the release directory. -keith
On Mon, 26 May 2003 15:05:39 -0400, Jonathan Brandmeyer Combobulated:> On Mon, 2003-05-26 at 14:49, Jonathan Brandmeyer wrote: > >> and that made all of the fonts non-itallic. That was enough for now, >> since I don''t use the itallic versions. Running fc-list as above shows >> that the slants are all zero. > > Just to clarify, I meant all of the Courier 10 Pitch fonts are > non-itallic. I haven''t noticed problems with any others.Running latest sid here too. I have noticed problems with several fonts so far - the Couriers, Nimbus family, the list goes on. Some are italic and shouldn''t be. Some are regular and should be italic, etc. Fontconfig is all messed up in Debian sid right now. -- Ciao, CRH 8^)>
On Mon, Jun 23, 2003 at 08:33:08AM -0500, CRH wrote:> Running latest sid here too. I have noticed problems with > several fonts so far - the Couriers, Nimbus family, the list > goes on. > > Some are italic and shouldn''t be. Some are regular and should > be italic, etc. > > Fontconfig is all messed up in Debian sid right now.Are these Type 1 fonts or TrueType fonts? I notice that fontconfig/Freetype2 produces lots of font mixups for Type 1, some of these I can figure out to be at the Freetype level. But I don''t know enough to figure out all of them. Is there good a way to check whether fontconfig or Freetype2 produces a particular font mixup? Regards, -- Ambrose LI Cheuk-Wing <a.c.li@ieee.org> http://ada.dhs.org/~acli/
On Mon, 26 May 2003 15:05:39 -0400, Jonathan Brandmeyer Combobulated:> On Mon, 2003-05-26 at 14:49, Jonathan Brandmeyer wrote: > >> and that made all of the fonts non-itallic. That was enough for now, >> since I don''t use the itallic versions. Running fc-list as above shows >> that the slants are all zero. > > Just to clarify, I meant all of the Courier 10 Pitch fonts are > non-itallic. I haven''t noticed problems with any others.Running latest sid here too. I have noticed problems with several fonts so far - the Couriers, Nimbus family, the list goes on. Some are italic and shouldn''t be. Some are regular and should be italic, etc. Fontconfig is all messed up in Debian sid right now. -- Ciao, CRH 8^)>
On Mon, 26 May 2003 15:05:39 -0400, Jonathan Brandmeyer Combobulated:> On Mon, 2003-05-26 at 14:49, Jonathan Brandmeyer wrote: > >> and that made all of the fonts non-itallic. That was enough for now, >> since I don''t use the itallic versions. Running fc-list as above shows >> that the slants are all zero. > > Just to clarify, I meant all of the Courier 10 Pitch fonts are > non-itallic. I haven''t noticed problems with any others.Running latest sid here too. I have noticed problems with several fonts so far - the Couriers, Nimbus family, the list goes on. Some are italic and shouldn''t be. Some are regular and should be italic, etc. Fontconfig is all messed up in Debian sid right now. -- Ciao, CRH 8^)>
Hello,
How one would prevent ''polygon request too large''
Xlib error? Is Xft capable of breaking the glyph in
smaller polygons, or probably there are X extensions
that allow large X requests?
This happens when I output font with pixel size larger than
~500x500 pixels.
Another question, which can serve as a safe fallback
for the said problem: how I would ask Xft to create
a bitmap glyph for me, for local use, without sending
it back and forth to the X server?
Yet another question: how to output Xft text with
logical raster operations? Agree, xor-ing antialiased
text has little use, but it is not so for the non-antialiased.
--
Sincerely,
Dmitry
--- www.karasik.eu.org ---
Life ain''t fair, but the root password helps.
- BOFH
Around 16 o''clock on Jun 28, Ambrose Li wrote:> I notice that fontconfig/Freetype2 produces lots of font mixups > for Type 1, some of these I can figure out to be at the Freetype > level. But I don''t know enough to figure out all of them.Figuring out font characteristics for Type1 fonts is a mixture of art and science; the specs are rather vague and contradictory. Fontconfig has been slowly improving in this area; you might try using a build from CVS to see if that makes any difference. If not, please submit a bug report referencing the approprite broken fonts and we''ll get them to work somehow. -keith