From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: Problem with UTF-8
Date: Wed, 03 Dec 2003 14:33:23 +0100 [thread overview]
Message-ID: <u7k1ekov0.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: mailman.974.1070458104.399.help-gnu-emacs@gnu.org
Konstantinos Efstathiou <cefstat@purple.univ-littoral.fr> writes:
> When writing the file:
>
> character: .[alpha] (05541, 2913, 0xb61, U+03B1).-A
> charset: greek-iso8859-7
[...]
> display: by this font (glyph code)
> -etl-fixed-medium-r-normal--14-140-75-75-m-140-iso8859-7 (0xE1)
>
> After saving and reopening the file:
>
> character: .[square] (01211661, 332721, 0x513b1, U+03B1).-A
> charset: mule-unicode-0100-24ff
[...]
> display: no font avairable
I see. It is a font problem. You need to create a fontset in order to
solve it. Look for an appropriate ISO 10646-1 font and set Emacs up to
use it for the charset mule-unicode-0100-24ff. For example this should
work on GNU/Linux:
(create-fontset-from-fontset-spec "\
-b&h-lucidatypewriter-medium-r-*-*-14-*-*-*-*-*-fontset-konstantinos,\
latin-iso8859-15:-b&h-lucidatypewriter-medium-r-*-*-14-*-*-*-*-*-iso8859-1,\
mule-unicode-0100-24ff:-*-fixed-medium-r-*-*-14-*-*-*-*-*-iso10646-1")
(set-face-font 'default "fontset-konstantinos")
Maybe there is a ISO 10646 variant of the ETL font that you are using?
Some people prefer to do it via X-ressources, but I don't use that and
I am too lazy to look the syntax up in the manual.
What is happening? Emacs internal encoding (emacs-mule) is divided
into several so-called "charsets". Every character in a buffer belongs
to a charset and some charsets contain the same (abstract)
characters. The Greek input method you use obviously inserts chars
from `greek-iso8859-7'. (Some or all (?) of the input methods for
classical Greek, for example, use `mule-unicode-0100-24ff'.) Font
resolving and similar things depend on those charsets. When you save
the file as UTF-8, then Emacs knows how to generate the appropriate
UTF-8 octets for the charset `greek-iso8859-7'. But when you visit it
again, then Emacs does not decode those UTF-8 octets to characters
belonging to `greek-iso8859-7', but to chars from
`mule-unicode-0100-24ff'. This is actually a good thing. It's just a
font issue that you don't see the right glyphs for those characters.
Oliver
--
13 Frimaire an 212 de la Révolution
Liberté, Egalité, Fraternité!
next parent reply other threads:[~2003-12-03 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.974.1070458104.399.help-gnu-emacs@gnu.org>
2003-12-03 13:33 ` Oliver Scholz [this message]
[not found] <mailman.1028.1070539813.399.help-gnu-emacs@gnu.org>
2003-12-05 6:12 ` Problem with UTF-8 Oliver Scholz
2003-12-04 10:14 Konstantinos Efstathiou
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 12:24 Konstantinos Efstathiou
[not found] <mailman.849.1070325841.399.help-gnu-emacs@gnu.org>
2003-12-02 9:20 ` Oliver Scholz
2003-12-02 15:49 ` Johan Bockgård
2003-12-02 17:15 ` Jeffery B. Rancier
2003-12-02 19:48 ` Eli Zaretskii
[not found] ` <mailman.923.1070389157.399.help-gnu-emacs@gnu.org>
2003-12-02 20:01 ` Oliver Scholz
2003-12-01 18:14 Konstantinos Efstathiou
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=u7k1ekov0.fsf@ID-87814.user.dfncis.de \
--to=alkibiades@gmx.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.
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).