Mercurial > hg > xemacs-beta
comparison lisp/x-init.el @ 3475:c3175ca37443
[xemacs-hg @ 2006-06-25 17:27:28 by aidan]
Stop complaining about unknown Unicode keysyms.
| author | aidan |
|---|---|
| date | Sun, 25 Jun 2006 17:27:29 +0000 |
| parents | d1754e7f0cea |
| children | aa22980554d9 |
comparison
equal
deleted
inserted
replaced
| 3474:94903620d912 | 3475:c3175ca37443 |
|---|---|
| 232 (string-equal "X Consortium" vendor)) | 232 (string-equal "X Consortium" vendor)) |
| 233 ;; Ok, we think this could be a Sun keyboard. Run the Sun code. | 233 ;; Ok, we think this could be a Sun keyboard. Run the Sun code. |
| 234 (x-win-init-sun)) | 234 (x-win-init-sun)) |
| 235 ((string-match "XFree86" vendor) | 235 ((string-match "XFree86" vendor) |
| 236 ;; Those XFree86 people do some weird keysym stuff, too. | 236 ;; Those XFree86 people do some weird keysym stuff, too. |
| 237 (x-win-init-xfree86)))) | 237 (x-win-init-xfree86))))) |
| 238 ;; Perhaps tell people that some keys won't work. | |
| 239 ;; | |
| 240 ;; If they remap while XEmacs is running and this problem arises, they | |
| 241 ;; won't see the messages. Which should be okay, assuming the length of | |
| 242 ;; time before we get a Unicode-compatible internal encoding is relatively | |
| 243 ;; short. | |
| 244 (let (unknown-code-points sym-string) | |
| 245 (dolist (x-keysym (hash-table-key-list (x-keysym-hash-table))) | |
| 246 (setq sym-string (if (stringp x-keysym) x-keysym (symbol-name x-keysym))) | |
| 247 (when (and (not (get (intern sym-string) 'character-of-keysym)) | |
| 248 (string-match "^U[0-9A-F]+$" sym-string)) | |
| 249 (pushnew (concat sym-string " ") unknown-code-points :test 'equal))) | |
| 250 (when (and (featurep 'mule) unknown-code-points) | |
| 251 (lwarn 'key-mapping 'info | |
| 252 "Undefined Unicode key mappings. | |
| 253 Your keyboard has, among many others, the following keysyms defined: | |
| 254 | |
| 255 %s | |
| 256 The standards say that applications should interpret these keysyms as | |
| 257 representing the corresponding Unicode code points (e.g. U2720 should | |
| 258 represent MALTESE CROSS), but unfortunately the current version of XEmacs | |
| 259 has no support for many of those characters in its internal encoding, and | |
| 260 when it encounters the keysyms corresponding to those characters, they | |
| 261 remain unbound. | |
| 262 | |
| 263 See the documentation for `unicode-to-char' for one technique if you have an | |
| 264 urgent need for support for one of those characters--you probably don't, | |
| 265 most of the widely-used characters have mappings in the internal XEmacs | |
| 266 encoding--otherwise, wait until we ship a version with an internal encoding | |
| 267 based on Unicode. " | |
| 268 (with-string-as-buffer-contents (apply 'concat " " | |
| 269 unknown-code-points) | |
| 270 (setq fill-prefix " ") | |
| 271 (fill-paragraph nil)))))) | |
| 272 | |
| 273 | 238 |
| 274 ;; Moved from x-toolbar.el, since InfoDock doesn't dump x-toolbar.el. | 239 ;; Moved from x-toolbar.el, since InfoDock doesn't dump x-toolbar.el. |
| 275 (defun x-init-toolbar-from-resources (locale) | 240 (defun x-init-toolbar-from-resources (locale) |
| 276 (loop for (specifier . resname) in | 241 (loop for (specifier . resname) in |
| 277 `(( ,top-toolbar-height . "topToolBarHeight") | 242 `(( ,top-toolbar-height . "topToolBarHeight") |