From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: improper display of multibyte characters
Date: Sat, 07 Nov 2009 19:20:19 +0200 [thread overview]
Message-ID: <83r5sa9rqk.fsf@gnu.org> (raw)
In-Reply-To: <3cbd659b-1873-4949-ad23-90583c90c1b3@o13g2000vbl.googlegroups.com>
> From: "Ron Peterson (012ED25E)" <peterson.ron@gmail.com>
> Date: Sat, 7 Nov 2009 05:16:30 -0800 (PST)
>
> Thanks! That's it. I had LC_ALL set to en_US.utf8 on the system that
> wasn't working, whereas it was set to C everywhere else. Now the
> question is: how much do I care about why using unicode interferes
> with the display of multibyte characters?
It shouldn't, at least not with the latest Emacs.
next prev parent reply other threads:[~2009-11-07 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 1:56 improper display of multibyte characters Ron Peterson (012ED25E)
2009-11-07 11:23 ` Eli Zaretskii
[not found] ` <mailman.10214.1257593196.2239.help-gnu-emacs@gnu.org>
2009-11-07 13:16 ` Ron Peterson (012ED25E)
2009-11-07 17:20 ` Eli Zaretskii [this message]
[not found] ` <mailman.10228.1257614562.2239.help-gnu-emacs@gnu.org>
2009-11-07 18:06 ` Ron Peterson (012ED25E)
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=83r5sa9rqk.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.
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).