From: Sergei Pokrovsky <pok@none.nowhere.invalid>
Subject: Re: cannot see utf-8 file
Date: 22 Mar 2002 16:14:40 +0600 [thread overview]
Message-ID: <uuk7s49aen.fsf@nbsp.nsk.su> (raw)
In-Reply-To: <s93g02t53ok.fsf@cheusov.scnsoft.com>
>>>>> "Aleksey" == Aleksey Cheusov <cheusov@scnsoft.com> writes:
[...]
Aleksey> There is something really strange with oc-unicode.
Aleksey> 1. it doesn't want to process utf-8 with russian characters
Works for me :)
Aleksey> 2. emacs+gnus using it always crashes on utf-8 messages
Aleksey> So, I deinstall it and install MULE-UCS and then
Aleksey> everything (GNUS too) works just fine.
Hm, maybe you had MULE-UCS _and_ oc-unicode both installed? Actually
oc-unicode contains its own version of MULE-UCS, much younger than the
current one, and it well may happen that they are in conflict.
Aleksey> The only question remained is 'why things are so complex?'
Because Emacs and Mule are older than Unicode. Hopefully some day
Emacs shall support Unicode internally.
Aleksey> Thank you all answering my questions
You are welcome.
--
Sergei
parent reply other threads:[~2002-03-22 10:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <s93g02t53ok.fsf@cheusov.scnsoft.com>]
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=uuk7s49aen.fsf@nbsp.nsk.su \
--to=pok@none.nowhere.invalid \
/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 NNTP newsgroup(s).