Re: Cyrillic vs UTF-8

[Simon Josefsson <jas@extundo.com>]

Simon Josefsson <jas@extundo.com> writes:

> I think there are two problems.  Opening the file the first time
> should guess it is a utf-8 file.  Secondly, emacs should be able to
> find a font that contains the characters -- I have all font packages
> from Debian installed.  The following works fine:
>
> -Misc-Fixed-Medium-R-Normal--18-120-100-100-C-90-ISO10646-1

It seems the second problem was documented in PROBLEMS (see below).
Sorry.

Still, I don't see similar behaviour with, e.g., Mozilla, so wouldn't
it be possible to check which characters exist within the font, and
perhaps change font as appropriate?

It would be nice if there were some more information how to set the
suggested fontset.  Reading the manual I get the impression that
'emacs -fn mule-unicode-...' should work, but it doesn't.  I also
tried setting the emacs.font X resource, but same problem.  Starting
emacs says:

No fonts match `mule-unicode-2500-33ff:-gnu-unifont-*-iso10646-1,mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1'

I do have GNU unifont (from Debian unstable) installed.

* Characters from the mule-unicode charsets aren't displayed under X.

XFree86 4 contains many fonts in iso10646-1 encoding which have
minimal character repertoires (whereas the encoding is meant to be a
reasonable indication of the repertoire).  Emacs may choose one of
these to display characters from the mule-unicode charsets and then
typically won't be able to find the glyphs to display many characters.
(Check with C-u C-x = .)  To avoid this, you may need to use a fontset
which sets the font for the mule-unicode sets explicitly.  E.g. to use
GNU unifont, include in the fontset spec:

mule-unicode-2500-33ff:-gnu-unifont-*-iso10646-1,\
mule-unicode-e000-ffff:-gnu-unifont-*-iso10646-1,\
mule-unicode-0100-24ff:-gnu-unifont-*-iso10646-1