all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Alex Speed Kjeldsen <alex.kjeldsen@gmail.com>
Cc: bug-gnu-emacs@gnu.org, 656@emacsbugs.donarmstrong.com
Subject: bug#656: Glyphs in Private Use Area not displayed in Emacs CVS
Date: Sun, 04 Jan 2009 00:03:21 +0800	[thread overview]
Message-ID: <495F8C49.9090306@gnu.org> (raw)
In-Reply-To: <f085eaff0810070957o1b4f4e4cvcedc885f9d055b6c@mail.gmail.com>

Alex Speed Kjeldsen wrote:
> I have no special code in the .emacs file apart from the specification 
> of which font to use. Today on a fresh arch GNU/linux install where I 
> installed the package "emacs-cvs" (23.0.60) and didn't have an .emacs 
> file, the problem was still there, when I started emacs this way:
>
>       emacs --font 
> "FONT_WHICH_INCLUDES_THE_GLYPHS_AND_WORKS_IN_DEC_2007_VERSION-FONTSIZE"
>
> The glyphs in PUA just show up as boxes

Looking at what you wrote above again, I think the problem is that Emacs 
now looks in greater detail at which unicode characters fonts have, 
rather than blindly using any iso10646-1 font for all unicode 
characters. For characters in PUA you will need to explicitly tell Emacs 
how to display them as follows, since Emacs cannot automatically 
recognize which fonts contain the characters you want:

(set-fontset-font "fontset-default"  '(#xe000 . #xf8ff) FONT-SPEC)








  reply	other threads:[~2009-01-03 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49A3F9A3.5090304@gnu.org>
2008-08-06  7:19 ` bug#656: Glyphs in Private Use Area not displayed in Emacs CVS Alex Speed Kjeldsen
2008-08-17 12:10   ` Jason Rumney
2008-10-07 16:57     ` Alex Speed Kjeldsen
2009-01-03 16:03       ` Jason Rumney [this message]
2009-02-24 13:50   ` bug#656: marked as done (Glyphs in Private Use Area not displayed in Emacs CVS) Emacs bug Tracking System

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=495F8C49.9090306@gnu.org \
    --to=jasonr@gnu.org \
    --cc=656@emacsbugs.donarmstrong.com \
    --cc=alex.kjeldsen@gmail.com \
    --cc=bug-gnu-emacs@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.