Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Welsh Duggan <md5i@cs.cmu.edu>
Subject: Re: Mule Emacs 20.3 w/enable-multibyte-characters set to nil
Date: Fri, 09 Jul 1999 19:57:45 GMT	[thread overview]
Message-ID: <v1t673tr3yh.fsf@peoria.mt.cs.cmu.edu> (raw)
In-Reply-To: <m34sjdd6ft.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Bill White <billw@wolfram.com> writes:
> 
> >   lmi> (insert (prin1-to-string "høa"))
> >   lmi> => "h\370a"
> > 
> > I get exactly that with "GNU Emacs 20.3.11.1 (i586-pc-linux-gnu, X
> > toolkit)" in *scratch* after M-x toggle-enable-multibyte-characters.
> 
> Darn.  Then I guess it's supposed to be that way.  Er...  Are there no
> Emacs-MULE people on this mailing list?

This is normal.

Here is the situation:

"høa" has a internal multibyte representation of "\201\370".

When inserting in the unibyte buffer, it correctly uses \370 instead
of \201\370 to represent the character `ø'.

However, the display-table is still set to display `\370' instead of
`ø'.  In order to set up the display table properly, you will need to
do something similar to what `standard-display-european-internal'
does.  Depending on your situation, you may want to do it to the
buffer's display-table rather than the standard-display-table.

-- 
Michael Duggan
(md5i@cs.cmu.edu)


  reply	other threads:[~1999-07-09 19:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-09 16:05 Lars Magne Ingebrigtsen
1999-07-09 16:21 ` Didier Verna
1999-07-09 20:55   ` Lars Magne Ingebrigtsen
1999-07-09 17:20 ` Bill White
1999-07-09 18:27   ` Lars Magne Ingebrigtsen
1999-07-09 19:57     ` Michael Welsh Duggan [this message]
1999-07-09 20:56       ` Lars Magne Ingebrigtsen
1999-07-11 22:50       ` Dave Love
1999-07-12 15:53         ` Michael Welsh Duggan
1999-07-14 19:20           ` Dave Love
1999-07-15  4:53             ` Michael Welsh Duggan

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v1t673tr3yh.fsf@peoria.mt.cs.cmu.edu \
    --to=md5i@cs.cmu.edu \
    /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 NNTP newsgroup(s).