bug#639: marked as done (23.0.60; tab bars use bizarre characters now)

[Emacs bug Tracking System]

Your message dated Sun, 23 Nov 2008 23:22:27 +0800
with message-id <49297533.3040505@f2s.com>
and subject line Re: bug#642: 23.0.60;garbled text (wrong font?) in About GNU 
Emacs screen
has caused the Emacs bug report #642,
regarding 23.0.60; tab bars use bizarre characters now
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact don@donarmstrong.com
immediately.)


-- 
642: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=642
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems

--- Begin Message --- Subject: 23.0.60; tab bars use bizarre characters now Date: Fri, 1 Aug 2008 07:42:51 -0700

emacs -Q

Load David Ponce's tabbar.el. I'm using this revision, which
AFAIK is the latest:
;; Revision: $Id: tabbar.el,v 1.20 2003/06/05 08:15:49 ponced Exp $
(defconst tabbar-version "1.3")

M-x tabbar-mode
 
The characters in the tabs are bad now. See attached images - the good
one is from a build of 2008-07-26; the bad one is from a build of
2008-08-01.
 

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-08-01 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
 

throw-good-tab-chars.png
Description: PNG image

throw-bad-tab-chars.PNG
Description: PNG image

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#642: 23.0.60;garbled text (wrong font?) in About GNU Emacs screen
>
>
>
>
> Date: 
>
> Sun, 23 Nov 2008 23:22:27 +0800
>
>
>
>
> User-agent: 
>
> Thunderbird 2.0.0.18 (Windows/20081105)
>
>
>
>
> Drew Adams wrote:
> > Here is some more info about this.
> >   
>
> > The display shows problems with font families Times and Helvetica. I use the
> > standard Times and Helvetica Type1 fonts on Windows XP. E.g., the Times Roman
> > font file is named TIR_____.PFM; the Helvetica file is HV_____.PFM.
> >   
>
>
> Thanks for your extra information.  I think this is related to the fact 
> that the Uniscribe font backend can only use opentype and truetype 
> fonts, but Windows by default defines font substitutions for Helvetica 
> and Times to map to the Truetype fonts "Arial" and "Times New Roman". So 
> the uniscribe backend picks these substitutes up, but somehow things get 
> confused so the Type-1 fonts end up being loaded. I've added some code 
> to specifically reject these substitutes, which are detected by 
> comparing the font's "full name" with the name used to load it. 
> Unfortunately this also catches many legitimate fonts, so I've had to 
> pick out these two specific problematic substitutions. If there are any 
> other specific fonts that cause this problem, then we will need to add 
> rules for them too.
>
>
>
>
>
> --- End Message ---