From: Paul Pogonyshev <pogonyshev@gmx.net>
Cc: Andreas Schwab <schwab@suse.de>
Subject: Re: Russian letters
Date: Thu, 6 Jul 2006 01:21:26 +0300 [thread overview]
Message-ID: <200607060121.26289.pogonyshev@gmx.net> (raw)
In-Reply-To: <jeejwzn1r9.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Paul Pogonyshev <pogonyshev@gmx.net> writes:
>
> > Andreas Schwab wrote:
> >> Paul Pogonyshev <pogonyshev@gmx.net> writes:
> >>
> >> > Russian letters loaded from file and newly typed are different
> >> > character no matter if `unify-8859-on-...-mode's are active or
> >> > not.
> >>
> >> What's your language environment?
> >
> > I'm not sure I understand your question.
>
> C-h L (describe-language-environment)
UTF-8 language environment
Input methods (default rfc1345):
rfc1345 ("m" in mode line)
TeX ("\" in mode line)
sgml ("&" in mode line)
ucs ("U+" in mode line)
Character sets:
nothing specific to UTF-8
Coding systems:
mule-utf-8 (`u' in mode line):
UTF-8 encoding for Emacs-supported Unicode characters.
It supports Unicode characters of these ranges:
U+0000..U+33FF, U+E000..U+FFFF.
They correspond to these Emacs character sets:
ascii, latin-iso8859-1, mule-unicode-0100-24ff,
mule-unicode-2500-33ff, mule-unicode-e000-ffff
On decoding (e.g. reading a file), Unicode characters not in the above
ranges are decoded into sequences of eight-bit-control and
eight-bit-graphic characters to preserve their byte sequences. The
byte sequence is preserved on i/o for valid utf-8, but not necessarily
for invalid utf-8.
On encoding (e.g. writing a file), Emacs characters not belonging to
any of the character sets listed above are encoded into the UTF-8 byte
sequence representing U+FFFD (REPLACEMENT CHARACTER).
(alias: mule-utf-8 utf-8)
> Anyway, as documented, unify-8859-on-decoding-mode can only map to
> `iso-latin-1' and `mule-unicode-0100-24ff'.
That's fine, but if the same characters read from file and typed from
keyboard are different in a buffer, that's nothing else than a bug.
Tell the average user about language environments. Ideally, Emacs
should work in this case as installed, without any configuration or
lines in `.emacs'.
Paul
next prev parent reply other threads:[~2006-07-05 22:21 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 [this message]
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
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=200607060121.26289.pogonyshev@gmx.net \
--to=pogonyshev@gmx.net \
--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).