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: Charset problem
Date: Thu, 13 Sep 2007 01:05:19 +0200	[thread overview]
Message-ID: <fc9rbd$6og$1@online.de> (raw)

Hi newgroup!
I have a question regarding character encoding which might be an Emacs 
problem or maybe a PuTTY problem or even a general linux problem. If you 
think my problem is not Emacs related, please let me know.
My problem is as follows: I log into my SuSE 10.2 linux server from my 
Windows box using PuTTY. I then use GNU Emacs (in text mode) to edit 
files on the linux box.
I have some old files which are encoded in ISO-8859-1. When I open these 
files in Emacs the german umlauts are displayed as question marks. I 
have tried to set PuTTY's translation to both UTF-8 and ISO-8859-1, but 
this doesn't change anything. When I set PuTTY's translation to 
ISO-8859-1 and *type* an umlaut, I see this umlaut only if it is 
lower-case, but it is followed by a blank. When I save the file and look 
at it using a hex editor the caracter is encoded in UTF-8. When I type 
an upper-case umlaut I see a question mark in Emacs and the hex editor 
shows a 0xC3 byte. When I set PuTTY's translation to UTF-8 and type an 
umlaut, I see a question mark, then some graphical character and a 
blank. In the hex editor I see a 3-byte sequence.
PuTTY seems to send an ISO-8859-1 encoded character when I set the 
translation to ISO-8859-1. At least it does in raw mode -- I have 
verified this using a network packet sniffer; unfortunately, I cannot 
look inside the SSH packets during the regular communication with the 
server.
So which way do my characters take before they get into the file? How 
many translation steps are done, and by whom? Are there any Emacs 
variables that must be set?

Thanks for any help!

Regards,
	Christian

             reply	other threads:[~2007-09-12 23:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 23:05 Christian Schröder [this message]
2007-09-13  7:10 ` Charset problem 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
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='fc9rbd$6og$1@online.de' \
    --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).