unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "James H. Cloos Jr." <cloos@jhcloos.com>
Cc: emacs-devel@gnu.org
Subject: Re: describe-char and unicode data
Date: 10 May 2003 12:23:41 -0400	[thread overview]
Message-ID: <m3znlu6a9e.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <9743-Sat10May2003130608+0300-eliz@elta.co.il>

>>>>> "Eli" == Eli Zaretskii <eliz@elta.co.il> writes:

>> Would a patch that expands that to also show the relevant data from
>> UnicodeData.txt be accepted?

Eli> What data do you have in mind, specifically?  Can you show a
Eli> (ficticious) example of such output, so we could iscuss that
Eli> first?

A current example output is:
==================================================================
  character: ʻ (01211133, 332379, 0x5125b)
    charset: mule-unicode-0100-24ff (Unicode characters of the range U+0100..U+24FF.)
 code point: 36 91
     syntax: w 	which means: word
   category:
buffer code: 0x9C 0xF4 0xA4 0xDB
  file code: 0xCA 0xBB (encoded by coding system mule-utf-8)
    Unicode: 02BB
       font: -Misc-Fixed-Medium-R-Normal--18-120-100-100-C-90-ISO10646-1

There are text properties here:
  lazy-lock            t
==================================================================

I propose expanding the Unicode: line to look like (same character):

    Unicode: 02BB  MODIFIER LETTER TURNED COMMA

The alternate names, if any, should also appear on that line.

The rest of the data in UnicodeData.txt and its related files are
useful to have, especially things like bidi info, combining class,
normalization data, etc.  As the files do get updated, a script or
some elisp to convert each of the text files into elisp seems like
the way to go.  But if all of the data should be incorporated, I'm
not sure what data structure would be best.

-JimC

  reply	other threads:[~2003-05-10 16:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 18:31 describe-char and unicode data James H. Cloos Jr.
2003-05-10 10:06 ` Eli Zaretskii
2003-05-10 16:23   ` James H. Cloos Jr. [this message]
2003-05-10 16:23 ` Florian Weimer
2003-05-10 16:39   ` James H. Cloos Jr.
2003-05-11 12:56     ` Richard Stallman
2003-05-11 13:04       ` Florian Weimer
2003-05-10 18:52   ` Simon Josefsson
2003-05-11 13:05     ` Florian Weimer
2003-05-11 14:34       ` Simon Josefsson
2003-05-12  7:38     ` Richard Stallman
2003-05-12 11:24       ` Simon Josefsson
2003-05-13  6:07       ` Simon Josefsson
2003-05-15  4:54         ` Richard Stallman
2003-05-11 12:55 ` Richard Stallman
2003-05-11 17:24   ` Stephen J. Turnbull
2003-05-12 11:22   ` Kenichi Handa
2003-05-14 13:49     ` Richard Stallman
2003-05-21 21:52   ` James H. Cloos Jr.
2003-05-22 15:29     ` Kevin Rodgers
2003-05-22 19:25       ` James H. Cloos Jr.
2003-05-23 12:04     ` Richard Stallman

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=m3znlu6a9e.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=emacs-devel@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 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).