From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: david.reitter@gmail.com
Cc: aquamacs-bugs@lists.sourceforge.net, whenney@gmail.com,
5886@debbugs.gnu.org
Subject: bug#5886: [Aquamacs-bugs] Re: incorrect fontification of non-ascii chars on Mac OS X 10.4
Date: Thu, 30 Jun 2005 01:36:33 +0900 (JST) [thread overview]
Message-ID: <20050630.013633.55126241.mituharu__1752.48945965922$1270746177$gmane$org@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <A6AF94A4-60BD-4929-8A4F-F7D17FDAE469@gmail.com>
>>>>> On Wed, 29 Jun 2005 17:03:34 +0100, David Reitter <david.reitter@gmail.com> said:
> Well, create-fontset-from-mac-roman seems to create fontsets with
> fonts only drawn from the 'roman' type.
Could you give me a concrete example?
> So I second Will in saying that it'd be good if create-fontset-from-
> fontset-spec could be fixed.
As for the "tons of wrong glyphs" problem, I think that's due to a
misuse of the function, rather than a bug. The function
create-fontset-from-fontset-spec is suitable only for the case that
all the characters in a single charset are displayed with a single
font. But that's not the case for fonts in Mac encodings.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2005-06-29 16:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F6BCBF6F-FF15-4D11-9AE1-ECBDCA0A0417@gmail.com>
2005-06-29 11:15 ` bug#5885: [Aquamacs-bugs] Re: incorrect fontification of non-ascii chars on Mac OS X 10.4 YAMAMOTO Mitsuharu
[not found] ` <wl7jgdjtxc.wl%mituharu@math.s.chiba-u.ac.jp>
2005-06-29 15:54 ` bug#5901: " William Henney
[not found] ` <BC82FC11-C906-429F-9546-F9EE3E9D1B4B@gmail.com>
2005-06-29 16:03 ` bug#5888: " David Reitter
[not found] ` <A6AF94A4-60BD-4929-8A4F-F7D17FDAE469@gmail.com>
2005-06-29 16:36 ` YAMAMOTO Mitsuharu [this message]
[not found] ` <20050630.013633.55126241.mituharu@math.s.chiba-u.ac.jp>
2005-06-29 16:59 ` bug#5892: " David Reitter
[not found] ` <7A52A2B4-ADD0-44A0-B8C9-A1F8F4CCDE75@gmail.com>
2005-06-30 3:34 ` bug#5869: " YAMAMOTO Mitsuharu
[not found] ` <wlirzwmsa4.wl%mituharu@math.s.chiba-u.ac.jp>
2005-06-30 6:52 ` bug#5868: " David Reitter
[not found] ` <04238FA2-2D02-41F0-9FDC-F843D518985F@gmail.com>
2005-06-30 10:40 ` bug#5870: " YAMAMOTO Mitsuharu
2005-06-30 17:56 ` bug#5880: " Stefan Monnier
[not found] ` <jwvmzp7bujm.fsf-monnier+emacs@gnu.org>
2005-07-01 7:21 ` bug#5884: " YAMAMOTO Mitsuharu
[not found] ` <wl4qbfxa8h.wl%mituharu@math.s.chiba-u.ac.jp>
2005-07-01 15:15 ` bug#5875: " Stefan Monnier
[not found] ` <87u0jea7gy.fsf-monnier+emacs@gnu.org>
2005-07-01 16:32 ` bug#5899: " William Henney
[not found] ` <F862FCDC-4751-462D-A6A5-C2099EC31794@gmail.com>
2005-07-01 16:41 ` bug#5874: " David Reitter
2005-07-01 17:05 ` bug#5879: " Stefan Monnier
2005-07-02 4:01 ` bug#5883: " YAMAMOTO Mitsuharu
2005-07-02 5:04 ` bug#5873: " YAMAMOTO Mitsuharu
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='20050630.013633.55126241.mituharu__1752.48945965922$1270746177$gmane$org@math.s.chiba-u.ac.jp' \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=5886@debbugs.gnu.org \
--cc=aquamacs-bugs@lists.sourceforge.net \
--cc=david.reitter@gmail.com \
--cc=whenney@gmail.com \
/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).