From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Russian letters
Date: Fri, 07 Jul 2006 11:46:29 +0300 [thread overview]
Message-ID: <uejwxree2.fsf@gnu.org> (raw)
In-Reply-To: <200607070048.15559.pogonyshev@gmx.net> (message from Paul Pogonyshev on Fri, 7 Jul 2006 00:48:15 +0300)
> From: Paul Pogonyshev <pogonyshev@gmx.net>
> Date: Fri, 7 Jul 2006 00:48:15 +0300
>
> $ emacs -Q
> M-x customize-variable RET utf-fragment-on-decoding RET
> [set to t, set for current session]
> C-x C-f test.text RET
>
> Now, the characters from the file are decoded into `cyrillic-iso8859-5',
> while new, typed characters are in `mule-unicode-0100-24ff'.
This is exactly what is expected. Here's the doc string of
utf-fragment-on-decoding:
utf-fragment-on-decoding's value is nil
Whether or not to decode some chars in UTF-8/16 text into iso8859 charsets.
Setting this means that the relevant Cyrillic and Greek characters are
decoded into the iso8859 charsets rather than into
mule-unicode-0100-24ff. The iso8859 charsets take half as much space
in the buffer, but using them may affect how the buffer can be re-encoded
and may require a different input method to search for them, for instance.
See `unify-8859-on-decoding-mode' and `unify-8859-on-encoding-mode'
for mechanisms to make this largely transparent.
The reason why the default value is nil is precisely that most users
will not want the fragmentation, they will want the characters to
belong to a single character set.
Did you set this variable to a non-nil value in your .emacs? If so,
how about removing that customization? If the reason is that you
don't have Unicode fonts installed, I think installing them is a
better solution.
next prev parent reply other threads:[~2006-07-07 8:46 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
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 [this message]
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=uejwxree2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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 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).