all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Font Interaction
Date: Fri, 23 Apr 2010 11:59:58 +0300	[thread overview]
Message-ID: <83wrvy35o1.fsf@gnu.org> (raw)
In-Reply-To: <95C75656-737C-4BDA-8388-B2555B07A91C@Web.DE>

> Cc: Eli Zaretskii <eliz@gnu.org>,
>  help-gnu-emacs@gnu.org
> From: Peter Dyballa <Peter_Dyballa@Web.DE>
> Date: Fri, 23 Apr 2010 10:27:06 +0200
> 
> So it might be worth to set an UTF-8 encoding only for some buffers or  
> processes, or, when the terminal is definitely set up for UTF-8 and  
> GNU Emacs is by default in UTF-8 mood (via environment variable  
> LC_CTYPE, LC_LANG, LC_ALL, or other means), then set these "screwed  
> up" processes/buffers into some 8- or 7-bit encoding.

What? why?

The way Emacs encodes terminal output on text terminals is entirely
independent of the buffer contents.  Characters in the buffer are held
in the internal Emacs representation, and Emacs explicitly encodes
them when it sends them to the screen.  So there's no dependency
whatsoever between the buffer contents and the terminal encodings that
could be used with it.  (Of course, some characters will be sent as
`?' if the terminal encoding cannot represent them, but UTF-8 can
represent all characters, and `?' on display is not the OP's problem
anyway.)

Also, "C-x RET t" overrides any settings determined by LC_* variables,
so that also should be irrelevant.

Am I missing something?




  reply	other threads:[~2010-04-23  8:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  7:35 Font Interaction Paulo J. Matos
2010-04-21 16:20 ` Eli Zaretskii
2010-04-22  9:04   ` pocmatos
2010-04-22  9:16     ` Juanma Barranquero
2010-04-23  7:07   ` Paulo J. Matos
2010-04-23  8:19     ` Eli Zaretskii
2010-04-23  8:27     ` Peter Dyballa
2010-04-23  8:59       ` Eli Zaretskii [this message]
2010-04-23 10:19         ` Peter Dyballa
2010-04-23 14:25           ` Eli Zaretskii
2010-04-23 19:01             ` Paulo J. Matos

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wrvy35o1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.