unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: font problem persists
Date: Fri, 02 Dec 2005 21:21:27 -0500	[thread overview]
Message-ID: <87vey7gcdp.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 87d5kfl6tb.fsf_-_@mat.ucm.es

Stefan> So instead, you should only specify the font family, and
Stefan> size, while the charset is automatically selected by Emacs
Stefan> (which will use the iso10646-1 font for the Unicode chars,
Stefan> ...).

>>> emacs -font  "-adobe-courier-bold-o-normal--0-0-100-100-m-0-iso10646-1"

> Ok then I tried

>>> emacs -font
>    "-adobe-courier-bold-o-normal--0-0-100-100-m-0-*-*"

> And the behaviour is the  same, that is 
>  C-h h displays Hebrew and Greek correctly.
> However when I open a file, which I recently have edited with Greek
> and Hebrew symbols and saved as UTF-8, those symbols are displayed as
> empty boxes.

The internal representation of non-ascii chars in MULE (later inherited by
Emacs and XEmacs) is based on iso-2022 which, contrary to Unicode which
didn't really exist yet at that time, does not unify "identical" characters.

So what you're seeing is that the Hebrew and Greek chars used in C-h
H are not the same chars as the ones used in utf-8 files (try C-u C-x =
on each of those chars to see which charset they are part of).

The Hebrew chars you see in C-h H are displayed using a Hebrew font.
The Greek chars you see in C-h H are displayed using a Greek font.
The Hebrew and Greek chars you don't see in your utf-8 file are displayed
with a Unicode font.

With Emacs-CVS ("soon" to become Emacs-22), you can set
utf-fragment-on-decoding, which should help for some of those chars
(probably the Greek chars, maybe not the Hebrew).


        Stefan

  parent reply	other threads:[~2005-12-03  2:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 14:37 wikipedia and UTF8 coding (emacs21) Uwe Brauer
2005-11-03 15:49 ` Peter Dyballa
2005-11-03 16:33 ` Stefan Monnier
2005-11-03 18:45   ` Uwe Brauer
2005-11-03 19:04     ` Peter Dyballa
2005-11-03 19:09       ` Uwe Brauer
2005-11-03 19:43         ` Peter Dyballa
     [not found]         ` <mailman.13846.1131047004.20277.help-gnu-emacs@gnu.org>
2005-11-03 20:30           ` Uwe Brauer
2005-11-04 12:35           ` Reiner Steib
     [not found]       ` <mailman.13841.1131044962.20277.help-gnu-emacs@gnu.org>
2005-11-22 19:49         ` Stefan Monnier
2005-12-02 17:58           ` font problem persists (was: wikipedia and UTF8 coding (emacs21)) Uwe Brauer
2005-12-02 20:08             ` Peter Dyballa
2005-12-03  2:21             ` Stefan Monnier [this message]
2005-12-05 17:30               ` font problem persists Uwe Brauer
     [not found]             ` <mailman.17688.1133554097.20277.help-gnu-emacs@gnu.org>
2005-12-05 17:25               ` Uwe Brauer
2005-11-04 12:34     ` wikipedia and UTF8 coding (emacs21) Reiner Steib
2005-11-22 19:46     ` Stefan Monnier
2005-11-23 20:55       ` Reiner Steib
     [not found]       ` <mailman.16628.1132865580.20277.help-gnu-emacs@gnu.org>
2005-11-25  4:29         ` Stefan Monnier
2005-11-03 17:09 ` Denis H. G.
     [not found] ` <mailman.13812.1131033002.20277.help-gnu-emacs@gnu.org>
2005-11-03 18:32   ` Reiner Steib
2005-11-04 20:22     ` Uwe Brauer
2005-11-22 19:40       ` Stefan Monnier
2005-11-06 10:16     ` using emacs 21 (was: " Uwe Brauer
2005-11-06 10:48       ` Peter Dyballa
2005-11-06 10:59       ` Peter Dyballa
2005-11-04 14:05   ` Encodings in message (was: wikipedia and UTF8 coding (emacs21)) Marc Girod
2005-11-04 15:25     ` Encodings in message Reiner Steib

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=87vey7gcdp.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    /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).