public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: TTF-font rendering not working anymore
Date: Mon, 17 Nov 2003 03:22:00 -0000	[thread overview]
Message-ID: <3FB83EDE.3000208@msu.edu> (raw)
In-Reply-To: <Pine.WNT.4.56.0311152112290.168@t00lp1.desy.de>

Fridger,

I don't know enough about this to comment.  Thus, no comment.

I don't know what is wrong.  You already know more than me because you 
have a test case.  I can't say that I have time to look into this right 
now.  If someone else has time, I would appreciate it.

Harold

Fridger Schrempp wrote:
>>After the recent XFree86-freetype2-fontconfig upgrade of Oct 29, the
>>rendering of TTF fonts does not work anymore for me. My TTF fonts are
>>still listed correctly e.g. with 'xlsfonts' but /not/ displayed on
>>screen anymore e.g. with 'xfontsel', 'xfd'...
> 
> 
>>Also xterm continues to work fine, e.g. 'xterm -fa "Luxi Mono" -fs 16'
>>produces correct anti-aliased fonts.
> 
> 
>>My Cygwin (XFree86) installation is up-to-date.
> 
> 
>>Fridger
> 
> 
> Since nobody has responded yet to my message of Nov. 10 and (an analogous
> one from a second user), I wonder whether TTF font rendering in
> X-applications  works for everyone but me with the latest updates?! Also
> the X-fontserver 'xfs' still appears to be broken...
> 
> Fridger
> 
> 


  reply	other threads:[~2003-11-17  3:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15 20:17 Fridger Schrempp
2003-11-17  3:22 ` Harold L Hunt II [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-21  7:34 Lev Bishop
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-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=3FB83EDE.3000208@msu.edu \
    --to=huntharo@msu.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).