unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: anhnmncb <anhnmncb@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs could not show this symbol.
Date: Thu, 28 Feb 2008 11:12:33 +0100	[thread overview]
Message-ID: <9D6D3945-FBA2-4DD3-A3FB-26361DC31A33@Web.DE> (raw)
In-Reply-To: <86pruhyk48.fsf@freebsd.hasee.cpu>


Am 28.02.2008 um 01:56 schrieb anhnmncb:

> Now I find another symbol emac couldn't recognize:
>
>         character: ✺ (10042, #o23472, #x273a)

It's from the dingbats block: SIXTEEN POINTED ASTERISK. Zapf Dingbats  
has it, the Lucida Sans fonts in Java have it, Code2000, FreeSerif ...

I think there is no way to use fc-list.


The name of the character can be output when you customise what is  
printed by C-u C-x =. There is particularly one variable name:  
describe-char-unicodedata-file in GNU Emacs 22 ... 23.0.50 and  
unicodedata-file in GNU Emacs 23.0.60:

	'(describe-char-unicodedata-file "/Applications/UnicodeChecker.app/ 
Contents/Resources/Unicode Data/UnicodeData.txt")
	'(unicodedata-file "/sw/lib/clisp-2.43/data/UnicodeDataFull.txt")

The file UnicodeData.txt comes with Kermit, Perl, xindy, XeTeX – and  
GNU Emacs 23.x.
The file UnicodeDataFull.txt comes with CLisp or xindy.

The output then can be:

         character: ✺ (10042, #o23472, #x273a)
preferred charset: gb18030 (GB18030)
        code point: 0x8137C136
            syntax: w 	which means: word
       buffer code: #xE2 #x9C #xBA
         file code: #xE2 #x9C #xBA (encoded by coding system utf-8-unix)
           display: by this font (glyph code)
      -monotype-arial unicode ms-medium-r-normal--10-98-74-74-p-99- 
gb18030.2000-0 (#xC136)

Character code properties: customize what to show
   name: SIXTEEN POINTED ASTERISK
   general-category: So (Symbol, Other)
   canonical-combining-class: 0 (Spacing, split, enclosing,  
reordrant, and Tibetan subjoined)


--
Greetings

   Pete

Government is actually the worst failure of civilized man. There has  
never been a really good one, and even those that are most tolerable  
are arbitrary, cruel, grasping and unintelligent.
				– H. L. Mencken







  reply	other threads:[~2008-02-28 10:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26  1:11 emacs could not show this symbol anhnmncb
2008-02-26  4:05 ` anhnmncb
2008-02-26  6:33   ` David Hansen
     [not found]   ` <mailman.7947.1204007911.18990.help-gnu-emacs@gnu.org>
2008-02-26 11:00     ` anhnmncb
2008-02-27 12:09       ` Peter Dyballa
     [not found]       ` <mailman.7995.1204114181.18990.help-gnu-emacs@gnu.org>
2008-02-28  0:10         ` anhnmncb
2008-02-28  0:56           ` anhnmncb
2008-02-28 10:12             ` Peter Dyballa [this message]
2008-02-28  9:49           ` Peter Dyballa
     [not found]           ` <mailman.8026.1204192187.18990.help-gnu-emacs@gnu.org>
2008-02-28 12:47             ` anhnmncb
2008-02-28 15:01               ` Peter Dyballa
     [not found]               ` <mailman.8038.1204210929.18990.help-gnu-emacs@gnu.org>
2008-02-29  0:25                 ` anhnmncb
2008-02-29 11:15                   ` Peter Dyballa
2008-02-26 11:35 ` Peter Dyballa
2008-02-26 11:46   ` anhnmncb

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=9D6D3945-FBA2-4DD3-A3FB-26361DC31A33@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=anhnmncb@gmail.com \
    --cc=help-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.
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).