unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 7956@debbugs.gnu.org
Subject: bug#7956: 24.0.50; xft:-B&H-LucidaTypewriter-normal-normal-normal-Sans-10-*-*-*-m-60-iso10646-1 rendered to presumingly 1 pt
Date: Thu, 3 Feb 2011 00:56:10 +0100	[thread overview]
Message-ID: <E8F672FD-1BE7-44E7-A5A5-6437EAAF424A@Freenet.DE> (raw)
In-Reply-To: <4D49B384.5030403@swipnet.se>


Am 02.02.2011 um 20:41 schrieb Jan Djärv:

> Hard to say.  What happens for xfd -fn '-B&H-LucidaTypewriter-normal- 
> normal-normal-Sans-10-*-*-*-m-60-iso10646-1' ?

	xfd -fn '-B&H-LucidaTypewriter-normal-normal-normal-Sans-10-*-*-*- 
m-60-iso10646-1'
	Warning: Cannot convert string "-B&H-LucidaTypewriter-normal-normal- 
normal-Sans-10-*-*-*-m-60-iso10646-1" to type FontStruct
	xfd:  no font to display
	Exit 1

When I select the font manually in xfontsel it works as:

	xfd -fn '-b&h-lucidatypewriter-medium-r-normal-sans-10-*-*-*-m-60- 
iso10646-1' &
	[2] 18394


> Does
> % emacs -fn sans-10
>
> give better results?

Partially! As long as GNU Emacs is loading the desktop and the session  
saved I can see clearly the text. When this has finished, the fonts  
become invisible. Invoking GNU Emacs with -q or -Q keeps the initial  
image and the correct size of "xft:-bitstream-Bitstream Vera Sans- 
normal-normal-normal-*-12-*-*-*-*-0-iso10646-1". So there can as well  
be something in my init file. When I invoke

	emacs -q -fn '-b&h-lucidatypewriter-medium-r-normal-sans-10-*-*-*- 
m-60-iso10646-1' &

I never see that font normally, only the introductory page with the  
"GNU Emacs" logo and hyper-link to some documentation appears OK in  
Bitstream Vera Sans and Monospace.

>  It seems your X server or Emacs or a combination has problems with  
> old style fonts.

I'd think it has to do with TT fonts (the Lucida Sans Typewriter is  
such one, from Java). Jeremy Huddleston mentions that he is using an  
elder version of FreeType because the recent one shows some bugs in  
Snow Leopard, Mac OS X 10.6. Maybe Mac OS X is buggy...


Later, after sleep, I can try to determine which statement in my init  
file is causing the "disappearance" of the sans font!

--
Greetings

   Pete

The day Microsoft makes something that doesn't suck is the day they  
start selling vacuum cleaners.
				– Ernest Jan Plugge






  reply	other threads:[~2011-02-02 23:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 20:39 bug#7956: 24.0.50; xft:-B&H-LucidaTypewriter-normal-normal-normal-Sans-10-*-*-*-m-60-iso10646-1 rendered to presumingly 1 pt Peter Dyballa
2011-02-02 19:41 ` Jan Djärv
2011-02-02 23:56   ` Peter Dyballa [this message]
2011-02-04  0:00   ` Peter Dyballa
2011-03-31 17:09 ` Peter Dyballa
2011-04-04  9:35   ` Jan D.

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=E8F672FD-1BE7-44E7-A5A5-6437EAAF424A@Freenet.DE \
    --to=peter_dyballa@freenet.de \
    --cc=7956@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).