view etc/unicode/mule-ucs/README @ 3724:1fe680cefdb7

[xemacs-hg @ 2006-12-06 21:28:47 by aidan] lisp/ChangeLog addition: 2006-12-04 Aidan Kehoe <kehoea@parhasard.net> * simple.el (what-cursor-position): For non-ASCII characters, give details on what a character maps to in Unicode, and its Mule charsets and codes, instead of simply its integer code point in this XEmacs. src/ChangeLog addition: 2006-12-04 Aidan Kehoe <kehoea@parhasard.net> * text.c (Fsplit_char): Make split-char available on non-Mule builds, taking out a superfluous call to get-charset to make that possible.
author aidan
date Wed, 06 Dec 2006 21:28:54 +0000
parents a29c4eef8f00
children
line wrap: on
line source

The files in this directory were converted from data in the mule-ucs
package (mule-ucs/lisp/reldata/*), using this code:

(defun convert-mule-ucs-file (start end)
  (interactive "r")
  (with-output-to-temp-buffer "*mule-ucs-convert*"
    (save-excursion
      (goto-char start)
      (while (re-search-forward "(\\?\\(.\\) \\. \"\\(.*\\)\") ;+ \\(.*\\)$"
				end t)
	(let ((ch (string-to-char (match-string 1)))
	      (codepoint (match-string 2))
	      (name (match-string 3)))
	  (if (= 1 (charset-dimension (char-charset ch)))
	      (princ (format "0x%x   %s  #   %s\n" (char-octet ch) codepoint name))
	    (princ (format "0x%x%x   %s  #   %s\n" (char-octet ch 0) (char-octet ch 1) codepoint name))))))))

Each file is named after the XEmacs charset it represents.  The CNS files
contain more codepoints than those in unicode-consortium/ because they list
codepoints above 0xFFFF, those handled by surrogates (supported starting in
Windows 2000, I think, but not yet by XEmacs).