From: Eli Zaretskii <eliz@gnu.org>
Cc: schwab@suse.de, emacs-devel@gnu.org
Subject: Re: Russian letters
Date: Thu, 06 Jul 2006 23:11:11 +0300 [thread overview]
Message-ID: <uslleqysg.fsf@gnu.org> (raw)
In-Reply-To: <200607062117.25013.pogonyshev@gmx.net> (message from Paul Pogonyshev on Thu, 6 Jul 2006 21:17:24 +0300)
> From: Paul Pogonyshev <pogonyshev@gmx.net>
> Date: Thu, 6 Jul 2006 21:17:24 +0300
> Cc: Andreas Schwab <schwab@suse.de>
>
> Andreas Schwab wrote:
> > Paul Pogonyshev <pogonyshev@gmx.net> writes:
> >
> > > The file is UTF-8 and mentions its coding in `Local variables'. Again,
> > > the file is read just fine. The problems begin when I type new
> > > characters into the buffer: they are treated differently than the same
> > > characters read from the file.
> >
> > I can't reproduce that here. Whenever I read a file with russian letters
> > that is encoded in utf-8 the letters are decoded into
> > mule-unicode-0100-24ff.
>
> I said many times that the problems begin when I _type_ characters, not
> when they are read from file.
No, you said, and I quote:
Russian letters loaded from file and newly typed are different
character no matter if `unify-8859-on-...-mode's are active or
not.
Characters loaded from file:
character: a (3664, #o7120, #xe50, U+0430)
charset: cyrillic-iso8859-5 (Right-Hand Part of Latin/Cyrillic Alphabet (ISO/IEC 8859-5): ISO-IR-144.)
code point: #x50
syntax: w which means: word
category: y:Cyrillic
buffer code: #x8C #xD0
file code: #xD0 #xB0 (encoded by coding system mule-utf-8-unix)
display: by this font (glyph code)
-cronyx-Fixed-Medium-R-Normal--18-120-100-100-C-90-ISO8859-5 (#xD0)
Newly typed characters:
character: a (332880, #o1212120, #x51450, U+0430)
charset: mule-unicode-0100-24ff (Unicode characters of the range U+0100..U+24FF.)
code point: #x28 #x50
syntax: w which means: word
category: y:Cyrillic
buffer code: #x9C #xF4 #xA8 #xD0
file code: #xD0 #xB0 (encoded by coding system mule-utf-8-unix)
display: by this font (glyph code)
-Adobe-Courier-Medium-R-Normal--17-120-100-100-M-100-ISO10646-1 (#x430)
That is, you said that characters read from a file are decoded into
cyrillic-iso8859-5, while characters you type are decoded into
mule-unicode-0100-24ff. Now it sounds like it's the other way around,
especially since you say that the file is encoded in UTF-8 (which is
_always_ decoded into mule-unicode-0100-24ff, AFAIR).
Please clarify which one is it.
Also, please try the same file and keyboard keys in "emacs -Q",
perhaps something in your .emacs has unpleasant side effects.
next prev parent reply other threads:[~2006-07-06 20:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 18:10 Russian letters Paul Pogonyshev
2006-07-05 18:19 ` Andreas Schwab
2006-07-05 21:43 ` Paul Pogonyshev
2006-07-05 22:08 ` Andreas Schwab
2006-07-05 22:21 ` Paul Pogonyshev
2006-07-05 22:55 ` Andreas Schwab
2006-07-06 15:59 ` Paul Pogonyshev
2006-07-06 16:39 ` Andreas Schwab
2006-07-06 18:17 ` Paul Pogonyshev
2006-07-06 20:11 ` Eli Zaretskii [this message]
2006-07-06 3:41 ` Eli Zaretskii
2006-07-06 15:56 ` Paul Pogonyshev
2006-07-06 20:12 ` Eli Zaretskii
2006-07-06 20:27 ` Paul Pogonyshev
2006-07-06 20:38 ` Paul Pogonyshev
2006-07-07 8:41 ` Eli Zaretskii
2006-07-06 21:14 ` Eli Zaretskii
2006-07-06 21:48 ` Paul Pogonyshev
2006-07-07 8:46 ` Eli Zaretskii
2006-07-07 19:59 ` Paul Pogonyshev
2006-07-08 12:35 ` Eli Zaretskii
2006-07-08 15:30 ` Paul Pogonyshev
2006-07-08 16:06 ` Eli Zaretskii
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=uslleqysg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).