From: Michael Livshin <usenet@cmm.kakpryg.net>
Subject: Re: getting Mule, Unicode & X selection to play together
Date: Wed, 18 Dec 2002 12:44:16 +0200 [thread overview]
Message-ID: <s3znr3ehdr.fsf@cmm.kakpryg.net.cmm> (raw)
In-Reply-To: mailman.369.1040190440.19936.help-gnu-emacs@gnu.org
Eli Zaretskii <eliz@is.elta.co.il> writes:
>> not forgetting to explicitly map the "cyrillic-iso8859-5" encoding
>> to an iso8859-5 font in the fontset (no sir, Emacs *won't* grok it
>> by itself, how could it?)
>
> I'm surprised this is so, but if it is, it sounds like a bug, so please
> report it (with a precise test case to reproduce) to
> emacs-pretest-bug@gnu.org. Thanks.
well, let me clarify. Emacs *did* find an appropriately-encoded font,
the problem was that it took the iso8859-5 font from the "standard"
fontset and not from my fontset, even though there surely *it* a
matching font in my fontset (and it works great once I map
"cyrillic-iso8859-5" to it explicitly).
perhaps it's a kind of feature?
it would be nice to simply be able to tell Emacs to forget the
standard fontset altogether, or at least to completely ignore it.
> Btw, cyrillic-iso8859-5 is not an encoding, it's a character set.
> But that's nitpicking.
it's kind of subtle, so it's certainly worth pointing out. thank you.
--
Incrementally extended heuristic algorithms tend inexorably toward the
incomprehensible.
next parent reply other threads:[~2002-12-18 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.369.1040190440.19936.help-gnu-emacs@gnu.org>
2002-12-18 10:44 ` Michael Livshin [this message]
2002-12-18 10:56 ` getting Mule, Unicode & X selection to play together Eli Zaretskii
[not found] <mailman.224.1039932883.19936.help-gnu-emacs@gnu.org>
2002-12-17 23:02 ` Michael Livshin
2002-12-18 5:47 ` Eli Zaretskii
2002-12-15 0:09 Michael Livshin
2002-12-15 6:14 ` Eli Zaretskii
2002-12-15 21:33 ` Tatsuya Kinoshita
2002-12-16 9:30 ` Roman Belenov
2002-12-16 11:21 ` Tatsuya Kinoshita
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=s3znr3ehdr.fsf@cmm.kakpryg.net.cmm \
--to=usenet@cmm.kakpryg.net \
/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).