unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: fontset/font change
Date: Fri, 13 Mar 2009 14:18:09 +0900	[thread overview]
Message-ID: <E1Lhzmb-0004Lo-Rt@etlken> (raw)
In-Reply-To: <49B90BD9.6060309@gnu.org> (message from Jason Rumney on Thu, 12 Mar 2009 21:19:21 +0800)

In article <49B90BD9.6060309@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:

> > Note that U+203E is the only non_ASCII character in
> > latin-jisx0201.
> >   

> I didn't know about that one (is it intended to be a combining macron?), 

No, the unicode name is "OVERLINE", and it's not a combining mark.

> but isn't ¥ also in latin-jisx0201 (at code point 92)?

Ah, right, I've forgotten about that.

> > But, why do we have that kind of setting in term/w32-win.el
> > only for Japanese? 

> Because only Japanese uses SJIS on Windows.

> > What does the registry "JISX0208-SJIS" exactly mean?

> A JISX0208 font that is available in SJIS encoding. Is there a more 
> standard way of writing that?

> >   Why doesn't the default setting work?
> >   

> It seems it does now.

That's good.

> I have removed those lines from w32-win.el.

Thank you.

---
Kenichi Handa
handa@m17n.org




  reply	other threads:[~2009-03-13  5:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 13:50 fontset/font change Miles Bader
2009-03-11 14:05 ` Jason Rumney
2009-03-11 14:36   ` Miles Bader
2009-03-12  1:16   ` Kenichi Handa
2009-03-12 13:19     ` Jason Rumney
2009-03-13  5:18       ` Kenichi Handa [this message]
2009-03-12  0:57 ` Kenichi Handa
2009-03-12  1:05   ` Miles Bader
2009-03-12  2:53     ` Kenichi Handa
2009-03-12  4:01       ` Miles Bader
2009-03-12  4:10       ` Chong Yidong
2009-03-12  6:40         ` Kenichi Handa
2009-03-12 13:39           ` Chong Yidong
2009-03-13  5:10             ` Kenichi Handa

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=E1Lhzmb-0004Lo-Rt@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --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).