From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jason Rumney'" <jasonr@f2s.com>
Cc: 642@emacsbugs.donarmstrong.com,
642-done@emacsbugs.donarmstrong.com,
'Miles Bader' <miles@gnu.org>
Subject: bug#642: 23.0.60; garbled text (wrong font?) in About GNU Emacs screen
Date: Sat, 29 Nov 2008 14:50:15 -0800 [thread overview]
Message-ID: <00fc01c95274$d8ebb620$0200a8c0@us.oracle.com> (raw)
In-Reply-To:
[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]
I was able to test this, to see the difference.
The bug is indeed fixed - thanks.
However, FWIW, the fonts used are less readable than in Emacs 22, so this is a
slight regression. See the attached screenshots. Notice both the text in the tab
bar and the text in the Info menu heading `Utilities'. Notice too that the
tab-bar text seems to be cut off at the top: you cannot tell the `f' in
"icicles-fn.el" from a `t'. You probably could not tell an `n' from an `h', and
so on: ascenders are chopped.
Dunno if anything can be done about this, but I hope the additional feedback
might help. It's a shame to see Emacs look a little worse instead of better.
Thx - Drew
> From: Drew Adams Sent: Sunday, November 23, 2008 9:20 AM
> > 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.
>
> Thanks for fixing this, Jason.
>
> I don't understand all that you wrote, but I probably don't
> need to. ;-)
>
> I think you're saying, along with the explanation of why,
> that I should no longer see garbled text after your fix. I
> might not see some particular fonts, but I will be able to
> read the text in some font. If so, that's fine.
>
> BTW, I the extra info helped, then it's thanks to Miles's
> list-fonts-display code. That enabled me to see the problem
> wrt specific fonts. Perhaps something like his code should be
> added to Emacs? (Dunno if there is already something that does that.)
>
> Thx.
[-- Attachment #2: throw-emacs-23-fonts.png --]
[-- Type: image/png, Size: 27780 bytes --]
[-- Attachment #3: throw-emacs-22-fonts.png --]
[-- Type: image/png, Size: 28980 bytes --]
next prev parent reply other threads:[~2008-11-29 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49297533.3040505@f2s.com>
2008-07-22 23:34 ` bug#597: 23.0.60; Corrupted display ofv
2008-07-23 0:01 ` Juanma Barranquero
2008-07-23 0:44 ` Óscar Fuentes
2008-07-23 7:53 ` Juanma Barranquero
2008-07-23 8:01 ` Jason Rumney
2008-07-23 13:06 ` ofv
2008-11-23 15:30 ` bug#597: marked as done (23.0.60; Corrupted display.) Emacs bug Tracking System
2008-08-01 14:42 ` bug#639: 23.0.60; tab bars use bizarre characters now Drew Adams
2008-11-23 15:30 ` bug#639: marked as done (23.0.60; tab bars use bizarre characters now) Emacs bug Tracking System
2008-08-02 20:23 ` bug#642: 23.0.60; garbled text (wrong font?) in About GNU Emacs screen Drew Adams
2008-08-02 21:05 ` Jason Rumney
2008-08-02 21:27 ` Drew Adams
2008-08-05 13:58 ` Drew Adams
2008-10-29 21:14 ` Drew Adams
2008-11-17 8:15 ` Drew Adams
2008-11-23 15:30 ` bug#642: marked as done (23.0.60; garbled text (wrong font?) in About GNU Emacs screen) Emacs bug Tracking System
2008-11-29 22:50 ` Drew Adams [this message]
2008-11-30 3:07 ` bug#642: 23.0.60; garbled text (wrong font?) in About GNU Emacs screen Jason Rumney
2008-12-22 21:30 ` Drew Adams
2008-08-02 20:50 Chong Yidong
2008-08-02 21:27 ` Drew Adams
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='00fc01c95274$d8ebb620$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=642-done@emacsbugs.donarmstrong.com \
--cc=642@emacsbugs.donarmstrong.com \
--cc=jasonr@f2s.com \
--cc=miles@gnu.org \
/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).