unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: umlauts (8bit characters) input
Date: Tue, 1 Feb 2005 16:21:26 +0100	[thread overview]
Message-ID: <F04BA380-7464-11D9-8B7E-000D932A32C4@Web.DE> (raw)
In-Reply-To: <ctnpl5$pk$02$1@news.t-online.com>


Am 01.02.2005 um 12:37 schrieb Hendrik Sattler:

> Konsole does not strip of the 8th bit, as
> EVERYTHING els is working just fine (bash, mcedit, even VI!). The 
> absolutly
> only exception is emacs.

Hmm, that's very interesting ... to me things behave completely 
different: in Apple's Terminal.app vi (actually vim) cannot display any 
8bit chars, I have to use GNU Emacs 21.3.50 to see them. When I launch 
the same as an X client or as a Carbon Application I can see and type 
these same umlauts, except that shell und dired-mode refuse to show me 
file names containing these umlauts.

I think terminal-coding-system can be an issue.

--
Mit friedvollen Grüßen

   Pete

Linux bietet Lösungen für Probleme unter Windows, die mit Mac OS X gar 
nicht erst auftreten.

  parent reply	other threads:[~2005-02-01 15:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 16:44 umlauts (8bit characters) input Hendrik Sattler
2005-01-31 21:52 ` Peter Dyballa
     [not found] ` <mailman.226.1107211155.2841.help-gnu-emacs@gnu.org>
2005-01-31 22:44   ` Hendrik Sattler
2005-01-31 23:47     ` Peter Dyballa
     [not found]     ` <mailman.238.1107216437.2841.help-gnu-emacs@gnu.org>
2005-02-01  0:41       ` Hendrik Sattler
2005-02-01 10:31         ` Peter Dyballa
     [not found]         ` <mailman.279.1107254715.2841.help-gnu-emacs@gnu.org>
2005-02-01 11:37           ` Hendrik Sattler
2005-02-01 12:36             ` David Kastrup
2005-02-01 13:37               ` Hendrik Sattler
2005-02-01 15:25                 ` Peter Dyballa
2005-02-02 10:27               ` Peter Dyballa
     [not found]               ` <mailman.463.1107343604.2841.help-gnu-emacs@gnu.org>
2005-02-02 12:38                 ` David Kastrup
2005-02-02 13:12                   ` Peter Dyballa
     [not found]                   ` <mailman.482.1107350962.2841.help-gnu-emacs@gnu.org>
2005-02-02 14:10                     ` David Kastrup
2005-02-02 14:59                       ` Ismael Valladolid Torres
2005-02-02 18:21                         ` Peter Dyballa
2005-02-02 18:17                       ` Peter Dyballa
2005-02-02 15:19                 ` Stefan Monnier
2005-02-02 19:37                   ` Peter Dyballa
     [not found]                   ` <mailman.578.1107374620.2841.help-gnu-emacs@gnu.org>
2005-02-03  4:09                     ` Stefan Monnier
2005-02-01 13:07             ` Reiner Steib
2005-02-01 13:47               ` Hendrik Sattler
2005-02-01 15:21             ` Peter Dyballa [this message]
2005-02-01 15:50 ` Hendrik Sattler
2005-02-01 16:05   ` David Kastrup
2005-02-01 16:08     ` Hendrik Sattler

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=F04BA380-7464-11D9-8B7E-000D932A32C4@Web.DE \
    --to=peter_dyballa@web.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).