unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: MULE shows gibberish; now what?
Date: Sat, 28 Sep 2002 14:20:23 +0200	[thread overview]
Message-ID: <vaf3crul308.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: an3ksh$27f2$1@agate.berkeley.edu

Ilya Zakharevich <nospam-abuse@ilyaz.org> writes:

> [A complimentary Cc of this posting was sent to
> Kai
>  =?iso-8859-15?q?Gro=DFjohann?=
> <Kai.Grossjohann@CS.Uni-Dortmund.DE>], who wrote in article <vafelbfw4cc.fsf@lucy.cs.uni-dortmund.de>:
>
>> In my understanding, telling Emacs "use the foo font to display
>> gb2312 encoded characters" amounts to pretty much the same thing as
>> telling Emacs "the foo font is in gb2312 encoding".
>
> Well, this is not enough.  A font in gb2312 encoding *has* cyrillic
> glyphs.  Will Emacs use them if they are present?

At the moment, the functionality is lacking indeed.  There is a file
latin1-disp.el which allows you to display some latin-2 characters
using their latin-1 equivalents, and vice versa.  But I think this
doesn't work with other fonts.

Note that for Emacs, a Cyrillic character in GB2312 and a Cyrillic
character in KOI-R (and so on) are all different characters, even
though they might look the same.  I don't know how much of this will
change in Emacs 22, but at the moment, that's the way it is.  And
because Emacs considers them to be different characters, Emacs
doesn't use glyphs for one character to display another.  And
latin1-disp.el is the exception from that rule...

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)

  parent reply	other threads:[~2002-09-28 12:20 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24  5:30 MULE shows gibberish; now what? Ilya Zakharevich
2002-09-24  8:42 ` Kai Großjohann
2002-09-24 15:59   ` Peter J. Acklam
2002-09-24 20:05     ` Kai Großjohann
2002-09-28 11:09       ` Peter J. Acklam
2002-09-28 12:22         ` Kai Großjohann
     [not found]           ` <k7l61bjc.fsf@online.no>
2002-09-28 15:58             ` Kai Großjohann
2002-09-28 16:32               ` Peter J. Acklam
2002-09-28 17:12                 ` Kai Großjohann
2002-09-29  9:27                   ` Peter J. Acklam
2002-09-29 15:45                     ` Kai Großjohann
2002-09-29 16:27                       ` Peter J. Acklam
2002-09-29 20:27                         ` Kai Großjohann
2002-10-01  7:59                           ` Peter J. Acklam
2002-09-29 20:13                     ` Stefan Monnier <foo@acm.com>
2002-09-30  1:22                       ` Miles Bader
     [not found]                       ` <mailman.1033349070.28368.help-gnu-emacs@gnu.org>
2002-09-30 14:03                         ` Stefan Monnier <foo@acm.com>
2002-09-29 20:27                     ` Kai Großjohann
2002-09-29  0:03               ` Clemens Fischer
2002-09-29 15:44                 ` Kai Großjohann
     [not found]   ` <amr0cn$2lvo$1@agate.berkeley.edu>
2002-09-25 14:11     ` Kai Großjohann
     [not found]       ` <amu08m$i97$1@agate.berkeley.edu>
2002-09-26  8:23         ` Kai Großjohann
     [not found]           ` <amvppk$10v4$1@agate.berkeley.edu>
2002-09-26 23:09             ` Oliver Scholz
2002-09-27 11:51             ` Kai Großjohann
     [not found]               ` <an2dcr$1phl$1@agate.berkeley.edu>
2002-09-27 20:43                 ` Kai Großjohann
     [not found]                   ` <an3ksh$27f2$1@agate.berkeley.edu>
2002-09-28 12:20                     ` Kai Großjohann [this message]
     [not found]                       ` <an7n4r$8dh$1@agate.berkeley.edu>
2002-09-30 20:49                         ` Jason Rumney
2002-09-30 21:22                           ` Ilya Zakharevich
2002-10-01 22:10                             ` Jason Rumney
2002-10-02  1:30                               ` Ilya Zakharevich
2002-10-02 13:10                                 ` Stefan Monnier <foo@acm.com>
2002-10-02 19:50                                 ` Jason Rumney
2002-09-29 12:28                     ` Jason Rumney
     [not found]           ` <an0bd9$1832$1@agate.berkeley.edu>
2002-09-27 11:54             ` Kai Großjohann
     [not found]               ` <an2dig$1pi4$1@agate.berkeley.edu>
2002-09-27 20:37                 ` Stefan Monnier <foo@acm.com>
2002-09-28  7:15                   ` Ilya Zakharevich
2002-10-02 23:48                   ` Ilya Zakharevich
2002-10-03 16:12                     ` Stefan Monnier <foo@acm.com>
2002-10-05 10:00                       ` Ilya Zakharevich
2002-10-05 16:07                         ` Stefan Monnier <foo@acm.com>
2002-10-06  0:43                           ` Ilya Zakharevich
2002-10-07 20:19                             ` Stefan Monnier <foo@acm.com>
2002-10-08  0:39                               ` Ilya Zakharevich
2002-10-08 13:33                                 ` Stefan Monnier <foo@acm.com>
2002-10-08 18:52                                   ` Ilya Zakharevich
2002-10-08 19:02                       ` MULE shows gibberish; RAWIN-R vs iso8859-5 Ilya Zakharevich
2002-09-27 20:44                 ` MULE shows gibberish; now what? Kai Großjohann
2002-09-27 22:30                 ` Oliver Scholz
2002-09-27 22:42                   ` Oliver Scholz
2002-09-27  7:29 ` Luis O. Silva
2002-09-27  7:28   ` Ilya Zakharevich
2002-10-09  6:14 ` Ilya Zakharevich
2002-10-31  0:48   ` Ilya Zakharevich

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=vaf3crul308.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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.
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).