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 11:31:47 +0100	[thread overview]
Message-ID: <799DF208-743C-11D9-8B7E-000D932A32C4@Web.DE> (raw)
In-Reply-To: <ctmj6u$hl3$00$1@news.t-online.com>


Am 01.02.2005 um 01:41 schrieb Hendrik Sattler:

> Peter Dyballa wrote:
>> ;       (set-language-environment               'UTF-8)
>>          (set-default-coding-systems             'utf-8)
>>          (setq file-name-coding-system           'utf-8)
>>          (setq default-buffer-file-coding-system 'utf-8)
>>          (setq coding-system-for-write           'utf-8)
>> ;       (set-keyboard-coding-system             'utf-8)
>>          (set-terminal-coding-system             'utf-8)
>> ;;      (set-clipboard-coding-system            'utf-8)
>> ;;      (set-selection-coding-system            'utf-8)
>> ;       (set-language-environment               'German)
>
> I don't understand why emacs should need all that. There are locales 
> and
> they define a system charset, emacs should use that as default.

These setting show how complicated it is to translate between the many 
systems GNU Emacs supports. It's not only Latin scripts! Have a look at 
the HELLO page: C-h H. And particularly two settings can become import 
when you're interacting with a window system: clipboard-coding-system 
and selection-coding-system. There is in the Help menu a very excessive 
entry: Describe -> Show all of Mule Status. Or simply M-x mule-diag. 
It'll give you pointers to stay for a few weeks in info-mode ...

>
>> It's always helpful to check what Emacs actually receives: C-h k and 
>> then
>> you type the umlaut.
>
> It gets M-| for the 'ü', '|' is 0x7C and 'ü' ist 0xFC, so the 8th bit 
> is
> ignored.
> Does emacs care for readline settings?

I don't think so. readline would be used in shell-mode or eshell-mode, 
if at all. Are you running Emacs freely as an X11 client or is it 
no-windows inside a terminal emulation? In the second case you're a bit 
dependant of what the terminal emulation is doing. It might convert 
8bit to 7bit. In both cases you have to set an appropriate 
input-method, as mule-diag will reveal.

Do you have test files à la 'char-representation = oct dec hex its 
description (to help you recognize what Emacs is doing to that glyph)', 
for example "ü = 374 = 252 = FC = U+00FC : LATIN SMALL LETTER U WITH 
DIAERESIS"? In any case it would be very helpful (for Emacs) to give a 
hint like "-*- mode: Text; coding: iso-8859-15; -*-" in the file's 
header to help it choose the right character set.

I do hope that others on this list have made more progress than both of 
us and add some to this thread! For example I would like to have shell 
and dired-buffers display in UTF-8 because the file names in Mac OS X 
are of that kind. In shell it works with ls when I let Emacs run in 
Apple's Terminal (emulation).

I hope that GNU Emacs 25 solves all problems.


> I really want to get that guy that said that ASCII and thus 7bit is a 
> useful
> default :-(((((

Oh no, why has the world to be so stubborn and keep writing in so my 
scripts? Why is a comic's use of script not sufficient?

--
Mit friedvollen Grüßen

   Pete      <\
              _\     O  _
             |o \  _\\_/-\='
_____________(_)|-(_)  (_)___________________________________

  reply	other threads:[~2005-02-01 10:31 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 [this message]
     [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
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=799DF208-743C-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).