From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: emacs-devel@gnu.org
Subject: Re: Special Characters on Mac Emacs
Date: Fri, 25 Mar 2005 15:48:19 +0900 [thread overview]
Message-ID: <wlll8c8bm4.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <m2ll8dus1x.fsf@seki.fr>
>>>>> On Thu, 24 Mar 2005 13:50:02 +0100, Sébastien Kirche <sebastien.kirche.no@spam.free.fr.invalid> said:
> - following your example M-: (set-frame-font
> (create-fontset-from-mac-roman-font
> "-apple-monaco-medium-r-normal--9-90-75-75-m-90-mac-roman"))
> I can see that the frame briefly flashes then it redisplays with the
> etl font.
I couldn't reproduce (even after installing ETL fonts from
http://members.shaw.ca/akochoi-emacs/stories/resources.html). If you
tried without -Q option, could you try again with it? Also, could you
show the result of (describe-font-set "fontset-mac_roman_9") ?
> I also added the custom-set-variables for
> face-font-registry-alternatives as you advised.
No, no. I didn't recommend that. What I wanted to say is:
- The create-fontset-from-fontset-spec example introduces wrong
glyph.
- There is an easier way to do without messing up
create-fontset-from-fontset-spec entries *if you don't care about
wrong glyph*.
> I have noticed formerly that some characters displays correctly
> (euro, eastern Europe languages) but many fail in the range
> 2500-33ff and display instead some Cyrillic.
I suppose no characters in mule-unicode-2500-33ff is accessible from
QuickDraw Text API that Carbon Emacs is currently using for drawing
text, at least when using with bundled fonts.
> Could you give an example of a full fontset definition ?
I'm not quite sure what you mean by "a full fontset definition".
Anyway, the font setting in my ~/.emacs is as follows.
(when (eq window-system 'mac)
(add-to-list 'default-frame-alist
`(font . ,(create-fontset-from-mac-roman-font "-apple-lucida sans typewriter-medium-r-normal--10-100-75-75-m-100-mac-roman")))
(setq face-font-rescale-alist '(("^-apple-.*-jisx02" . 1.2)))
(set-fontset-font "fontset-default" 'japanese-jisx0208
'("ヒラギノ角ゴ*" . "jisx0208.*"))
(set-fontset-font "fontset-default" 'katakana-jisx0201
'("ヒラギノ角ゴ*" . "jisx0201.*")))
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2005-03-25 6:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 16:18 Special Characters on Mac Emacs Ulrich Hobelmann
2005-03-23 11:20 ` YAMAMOTO Mitsuharu
2005-03-23 15:49 ` Sébastien Kirche
2005-03-24 3:00 ` YAMAMOTO Mitsuharu
2005-03-24 12:50 ` Sébastien Kirche
2005-03-25 6:48 ` YAMAMOTO Mitsuharu [this message]
2005-03-25 9:50 ` YAMAMOTO Mitsuharu
2005-03-25 15:34 ` Sébastien Kirche
2005-03-26 5:00 ` YAMAMOTO Mitsuharu
2005-03-31 3:43 ` Steven Tamm
2005-03-31 11:20 ` Sébastien Kirche
2005-03-29 10:03 ` Sébastien Kirche
2005-04-01 11:02 ` YAMAMOTO Mitsuharu
2005-04-01 11:56 ` Sébastien Kirche
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=wlll8c8bm4.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--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).