unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Piet van Oostrum <piet@cs.uu.nl>
Subject: Re: Patch for Mac OS X Text Drawing
Date: Tue, 18 Jan 2005 16:40:24 +0100	[thread overview]
Message-ID: <wzzmz6iw47.fsf@ordesa.local> (raw)
In-Reply-To: <0F0CEC8B-6757-11D9-9ECE-000D93B67DC4@mac.com> (Steven Tamm's message of "Sat, 15 Jan 2005 16:39:19 -0800")

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

>>>>> Steven Tamm <steventamm@mac.com> (ST) wrote:

ST> I've checked in a change that allows for anti-aliasing, but makes it
ST> optional (personally I only use it for large fonts).  I added the variable:

ST> mac-allow-anti-aliasing

ST> This is defaulted to nil, meaning don't use core graphics to render text.
ST> When set to non-nil, (setq mac-use-core-graphics t), it will enable the
Of course here you mean mac-allow-anti-alias
ST> core graphics rendering flag and will anti-alias text if that is enabled on
ST> your computer for the font you are trying to display.  I'm not a big fan of
ST> the name, because there is some basic anti-aliasing done in the operating
ST> system: but calling it mac-enable-core-graphics was too technical.

It took a few hours for me to get used to it, but now I am starting to like
it. 

I had hoped that this would solve the MacOSX bug where if you have some
italic text in a window which later is overwritten with spaces (like
happens in gnus summaries for me), small parts of the righthand side of
characters (those that stick out of the rectangular box) are not properly
erased. Also some characters are cutoff at the right. See the screen dump


[-- Attachment #2: screendump --]
[-- Type: image/png, Size: 16971 bytes --]

[-- Attachment #3: Type: text/plain, Size: 110 bytes --]


-- 
Piet van Oostrum <piet@cs.uu.nl>
URL: http://www.cs.uu.nl/~piet [PGP]
Private email: piet@vanoostrum.net

[-- Attachment #4: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  parent reply	other threads:[~2005-01-18 15:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 20:39 Patch for Mac OS X Text Drawing Arthur G.P. Schuster
2005-01-16  0:39 ` Steven Tamm
2005-01-16  8:04   ` Arthur G.P. Schuster
2005-01-17  3:18   ` YAMAMOTO Mitsuharu
2005-01-17  5:31     ` Steven Tamm
2005-01-17 11:21       ` YAMAMOTO Mitsuharu
2005-01-18 15:40   ` Piet van Oostrum [this message]
2005-01-19 11:48     ` YAMAMOTO Mitsuharu
2005-01-21  7:57       ` YAMAMOTO Mitsuharu
2005-01-22  2:52         ` Richard Stallman
2005-01-22  3:47           ` YAMAMOTO Mitsuharu
2005-01-22  4:55             ` Kenichi Handa
2005-01-22  5:49               ` YAMAMOTO Mitsuharu
     [not found]         ` <200501210353.j0L3rbj16707@church.math.s.chiba-u.ac.jp>
2005-01-24  9:36           ` YAMAMOTO Mitsuharu
2005-01-24 10:08             ` Kim F. Storm
2005-01-24 11:15               ` YAMAMOTO Mitsuharu
2005-01-24 18:00                 ` Steven Tamm

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=wzzmz6iw47.fsf@ordesa.local \
    --to=piet@cs.uu.nl \
    /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).