unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Christian Schröder" <chschroe@math.uni-goettingen.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Charset problem
Date: Sat, 15 Sep 2007 17:03:43 +0200	[thread overview]
Message-ID: <fcgs71$8cg$02$1@news.t-online.com> (raw)
In-Reply-To: <mailman.875.1189785660.18990.help-gnu-emacs@gnu.org>

Eli Zaretskii wrote:
> You mean, even with "C-x RET c latin-1 C-x C-f" Emacs still claims
> that the umlauts are eight-bit-graphic characters?  That is soooo
> strange!

Ok, it just became even more strange ...
I did not mention (sorry!) that I was in a "screen" session when I did 
all the tests. When I realized that this might be the reason for my 
problems I tried to simply log into the server and start Emacs directly 
and ... tadaa ... all the umlauts were there.
Ok, so screen seemed to be the culprit. To verify this suspicion I 
started screen and then Emacs ... and it still worked. So something 
seems to be wrong with the "screen" session I used for all my tests, but 
I have no idea what it could be. I dumped the whole environment to a 
file and sourced this file into a fresh shell, but it still worked, so 
the environment doesn't seem to have anything to do with my problem.
Is it worth to further investigate this issue? At least I can start to 
work now, but it would still be interesting what's wrong with the screen 
session ...

> What version of Emacs is that?  What does "M-x emacs-version RET" say?

If this information is still of any use:
GNU Emacs 21.3.1 (i586-suse-linux-gnu) of 2006-11-27 on tanajew

If I may ask one last question: I normally have my PuTTY translation set 
to UTF-8. Is it possible to make Emacs send me the ISO-8859-1 encoded 
umlauts as UTF-8 characters? Then I would not have to change the 
translation on my side.

Kind regards,
	Christian

  parent reply	other threads:[~2007-09-15 15:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 23:05 Charset problem Christian Schröder
2007-09-13  7:10 ` Eli Zaretskii
     [not found] ` <mailman.791.1189668733.18990.help-gnu-emacs@gnu.org>
2007-09-13 21:50   ` Christian Schröder
2007-09-14  7:46     ` Eli Zaretskii
2007-09-14  8:58     ` Peter Dyballa
     [not found]     ` <mailman.846.1189756022.18990.help-gnu-emacs@gnu.org>
2007-09-14 12:41       ` Christian Schröder
2007-09-14 13:58         ` Eli Zaretskii
     [not found]         ` <mailman.869.1189778341.18990.help-gnu-emacs@gnu.org>
2007-09-14 15:06           ` Christian Schröder
2007-09-14 16:00             ` Eli Zaretskii
     [not found]             ` <mailman.875.1189785660.18990.help-gnu-emacs@gnu.org>
2007-09-15 15:03               ` Christian Schröder [this message]
2007-09-15 15:59                 ` Peter Dyballa
2007-09-15 18:07                 ` Eli Zaretskii
     [not found]                 ` <mailman.902.1189871990.18990.help-gnu-emacs@gnu.org>
2007-09-17 11:11                   ` Christian Schröder
2007-09-17 12:33                     ` Peter Dyballa
2007-09-15  3:43         ` Tim X
2007-09-16  0:21         ` Giorgos Keramidas

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='fcgs71$8cg$02$1@news.t-online.com' \
    --to=chschroe@math.uni-goettingen.de \
    --cc=help-gnu-emacs@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.
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).