public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Lev Bishop <lev.bishop@yale.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: TTF-font rendering not working anymore
Date: Fri, 21 Nov 2003 07:34:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0311210219470.27774-100000@argos.its.yale.edu> (raw)

Harold, you wanted a three-click test case:
$ xfontsel
wait for it to finish parsing all the fonts. Note that it displays the 
alphabet in some default font at the bottom of the window.
Click on family and choose a TTF from the list, eg. one of the Luxis.
Note that the alphabet is no longer displayed. 
Just one click, three is not needed.

There are programmes ttfmkfdir, mkfontscale, mkfontdir, which need to be 
run when adding new fonts or directories, but the files they create are 
already present and rerunning them doesn't change things. Anyway, the 
fonts show up in the xfontsel list, so I think the problem is with the 
rendering, not anything else. 

This is not a problem with the "new style" fonts stuff, fontconfig, etc,
as used by xterm, etc, which work very well for me with the recent
versions, much prettier than the older ones, and even somewhat better than
the version of the freetype2 library that I compiled a while ago for
myself. (So well done everyone for getting all that working!) However, I
expect it is related to the seperating out of the freetype stuff from the
X server. I believe the "old style" (server side) fonts rendering stuff 
uses hacked up parts of freetype1 and freetype2 for dealing with TTF so 
presumably in the seperation process something got broken.

Hope that's useful.

Lev


             reply	other threads:[~2003-11-21  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  7:34 Lev Bishop [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-20  6:56 Kirk Erickson
2003-11-20 15:28 ` Harold L Hunt II
2003-11-20 18:09   ` Frank-Michael Moser
2003-11-15 20:17 Fridger Schrempp
2003-11-17  3:22 ` Harold L Hunt II
2003-11-10 13:58 Fridger Schrempp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0311210219470.27774-100000@argos.its.yale.edu \
    --to=lev.bishop@yale.edu \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).