Re: Dired doesn't decode UTF-8 file names

[David Kastrup <dak@gnu.org>]

Peter Dyballa <Peter_Dyballa@Web.DE> writes:

> Am 28.08.2006 um 22:52 schrieb Kevin Rodgers:
>
>> Peter Dyballa wrote:
>>> Am 28.08.2006 um 17:02 schrieb Kevin Rodgers:
>>>> >     (("\\*shell\\*\\'" utf-8 . utf-8)
>>>> >      ("\\*.* output\\*\\'" iso-8859-15-unix . iso-8859-15-unix))
>>>> >
>>>> > The second line is meant for AUCTeX output buffers (although
>>>> not really
>>>> > working, probably I have to find some hook). Is there really
>>>> more needed?
>>>>
>>>> That doesn't look right at all.  According to its doc string, the
>>>> car of
>>>> the alist elements should be a regexp that matches a program name,
>>>> whereas your patterns look like they match buffer names.
>>> OK. So I'll try to use
>>>     (("[bt][ac]sh\\'" utf-8 . utf-8)
>>>      (".*tex\\'" iso-8859-15-unix . iso-8859-15-unix))
>>
>> That should fix your *shell* buffers, and Dired buffers for wildcard
>> file names.  But non-wildcard Dired buffers invoke ls directly (not
>> via a shell).
>
> I was thinking of the *shell* buffer and the *output whatsoever*
> buffer from AUCTeX, which did not always work correctly, the latter
> kept using incorrect and inappropriate ISO 8859-1 encoding.

You are confused.  Multibyte buffers in Emacs are always in Emacs
encoding, never anything else.  There are various encodings for I/O
however: process I/O, file I/O, X cutbuffer and so on.  Those are
independent.

> The *shell* buffer does not show in mode-line any encoding – I have
> no idea whether this is good or bad, I would like to know which
> 'mood' it is in and how to interpret the buffer's contents.

Emacs buffer contents are characters in Emacs' encoding (MULE for
Emacs 22, an UTF-8 variant for Emacs 23).

> Do I really need to set encodings for each UNIX and GNU UNIX
> command?  Can't GNU Emacs learn from the LC_CTYPE environment
> variable?

Emacs uses the LC_CTYPE information unless you explicitly override it.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum