unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Patch: overstrike/bold in Windows build
Date: Fri, 27 Oct 2006 16:02:58 +0200	[thread overview]
Message-ID: <f7ccd24b0610270702x6a2267f8rce68a3d0e986a23e@mail.gmail.com> (raw)
In-Reply-To: <1161950628.4541f5a41d35a@imp.hosting365.ie>

On 10/27/06, Ben North <ben@redfrontdoor.org> wrote:

> One idea: Is the 2-* set made with a BDF font?

No. As I said, I used some long-forgotten font editor to open a font I
liked, I pasted the euro sign from a similar font at the right
codepoint, and I've been using it happily ever after. (I think all
this is not strictly illegal, as it is a personal use of the font and
I've never distributed it, but who knows...)

> Perhaps there's some
> interaction with what antialiasing and/or ClearText (on laptops?)

ClearText was inactive.

Hmm. Very interesting. The font I'm using already has Bold, Oblique
and Bold Oblique variants. So I think what's happening is that, when I
set the font to bold, Emacs uses the bold variant... and then somehow
thinks it doesn't support bold and tries to synthesize it. If I remove
the variants from \Windows\fonts and leave just the normal font, your
code works right.

-- 
                    /L/e/k/t/u

  reply	other threads:[~2006-10-27 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26 14:30 Patch: overstrike/bold in Windows build Ben North
2006-10-27  8:44 ` Juanma Barranquero
2006-10-27  8:58   ` Ben North
2006-10-27 10:46     ` Juanma Barranquero
2006-10-27 12:03       ` Ben North
2006-10-27 14:02         ` Juanma Barranquero [this message]
2006-10-27 14:38           ` Ben North
2006-10-27 15:01             ` Juanma Barranquero
2006-10-27 16:59               ` Ben North
2006-10-27 17:15                 ` Juanma Barranquero

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=f7ccd24b0610270702x6a2267f8rce68a3d0e986a23e@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@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).