unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V. Raman" <tv.raman.tv@gmail.com>
To: emacs-devel@gnu.org, raman@google.com
Subject: Unicode Char Names: describe-char-unicode-data vs get-char-code-property
Date: Fri, 27 Dec 2013 13:05:49 -0800	[thread overview]
Message-ID: <CADkJX2gz8kk1SsvYhJnq0EUSiLoD2bKNbNMxS5smQymMXjDmBQ@mail.gmail.com> (raw)
In-Reply-To: <CADkJX2hZM0EfQzoeXdt8WP5k=R4dqtwMuhZ5vM5tkKKZ9JdCmw@mail.gmail.com>

Following-up to myself and Eli:

I moved out my .emacs.d/elpa directory and the problem goes away
--- it's going to be a lot harder to identify the offending elpa
installed package:-)
-- 

-- 


On 12/27/13, T.V. Raman <tv.raman.tv@gmail.com> wrote:
> I use describe-char-unicode-data to speak unicode chars in
> emacspeak when navigating by character.
>
> That function claims to be semi-obsolete -- and recommends
> get-char-code-property instead; however the answers are not
> consistent in the two solutions.
>
> Try non-breaking space \240 (octal)
>
> (setq char ? )
> 160 (#o240, #xa0, ? )
> (describe-char-unicode-data char) returns
> (("Name" "NO-BREAK SPACE") ("Category" "Separator, Space")
> ("Combining class" "Zs") ("Bidi category" "Zs") ("Decomposition"
> "noBreak ") ("Decimal digit value" nil) ("Digit value" nil)
> ("Numeric value" nil) ("Mirrored" nil) ("Old name" "NON-BREAKING
> SPACE") ("ISO 10646 comment" nil) ("Uppercase" nil) ...)
> whereas
> (get-char-code-property char 'name) returns
> "COMMA NO-SHE IOTA ARABIC DIAERESIS"
> also looking up char in ucs-names yields something different
> (car (rassoc char (ucs-names))) returns
> "NON-NEITHER UNDER CM COMMA"
> Note that all of the above is with the unicdoedata file present
> and correctly found by emacs.
>
>
> Also, and perhaps related:
>
> C-x 8 spc inserts non-breaking space correctly; however when you
> use C-x 8 ret, non-breaking space doesn't show up in the
> available completions -- either using it's "name" or "old-name"
> --
>



  parent reply	other threads:[~2013-12-27 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27 20:09 Unicode Char Names: describe-char-unicode-data vs get-char-code-property T.V. Raman
2013-12-27 20:31 ` Eli Zaretskii
2013-12-27 20:46   ` T.V. Raman
2013-12-27 21:05 ` T.V. Raman [this message]
2013-12-27 21:32   ` Eli Zaretskii

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=CADkJX2gz8kk1SsvYhJnq0EUSiLoD2bKNbNMxS5smQymMXjDmBQ@mail.gmail.com \
    --to=tv.raman.tv@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    /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 public inbox

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

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).