Re: Character problems

Re: Character problems

[Richard Stallman]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]

    I entered Emacs version 21.1 with the -q option over a simple telnet.  I then
    evaluate (in succession):

	 (setq junk '(("Ê" . "\\^{E}") ("Ë" . "\\\"{E}")))
	  --> (("Ê" . "\\^{E}") ("Ë" . "\\\"{E}"))

What do you do to enter the character that appears here as Ê?
Likewise for Ë?

And how did you enter the \201?  Or did you?  I wonder if the internal
Emacs multibyte representation is somehow leaking out.


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: Character problems

[Andreas Schwab]

Richard Stallman <rms@gnu.org> writes:

|>     I entered Emacs version 21.1 with the -q option over a simple telnet.  I then
|>     evaluate (in succession):
|> 
|> 	 (setq junk '(("Ê" . "\\^{E}") ("Ë" . "\\\"{E}")))
|> 	  --> (("Ê" . "\\^{E}") ("Ë" . "\\\"{E}"))
|> 
|> What do you do to enter the character that appears here as Ê?
|> Likewise for Ë?
|> 
|> And how did you enter the \201?

I do not see \201 anywhere, that must be a problem on your side.  The raw
mail as I received it does not contain any \201 characters.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: Character problems

[Richard Stallman]

    I do not see \201 anywhere, that must be a problem on your side.  The raw
    mail as I received it does not contain any \201 characters.

The 201's were visible in my buffer when I received that message.  But
perhaps neither of us can tell for certain what was in the file he
sent, because of the encoding and decoding that goes on.  The only way
we can really be sure is if Reingold saves that region using emacs-mule
encoding, uuencodes the file, and sends that.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: Character problems

[Stefan Monnier]

>     I do not see \201 anywhere, that must be a problem on your side.  The raw
>     mail as I received it does not contain any \201 characters.
> 
> The 201's were visible in my buffer when I received that message.  But
> perhaps neither of us can tell for certain what was in the file he
> sent, because of the encoding and decoding that goes on.  The only way
> we can really be sure is if Reingold saves that region using emacs-mule
> encoding, uuencodes the file, and sends that.

I'm pretty sure it wasn't in the email I received since it did not get
near any kind of Emacs process on its way from the network to my
screen and yet there were no \201 chars to be seen.


	Stefan "who still hasn't switched to an Emacs-based MUA"


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: Character problems

[Eli Zaretskii]

On Tue, 26 Mar 2002, Stefan Monnier wrote:

> I'm pretty sure it wasn't in the email I received since it did not get
> near any kind of Emacs process on its way from the network to my
> screen and yet there were no \201 chars to be seen.
> 
> 
> 	Stefan "who still hasn't switched to an Emacs-based MUA"

FWIW, I read my mail with RMAIL, and I didn't see \201 in the buffer, 
either.

But I agree with Richard that sending the text as an encoded binary 
attachment is much more reliable.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel