1 |
This file describes various problems that have been encountered |
This file describes various problems that have been encountered |
2 |
in compiling, installing and running GNU Emacs. |
in compiling, installing and running GNU Emacs. |
3 |
|
|
4 |
|
* Mule-UCS loads very slowly. |
5 |
|
|
6 |
|
Changes to Emacs internals interact badly with Mule-UCS's `un-define' |
7 |
|
library, which is the usual interface to Mule-UCS. Apply the |
8 |
|
following patch to Mule-UCS 0.84 and rebuild it. That will help, |
9 |
|
though loading will still be slower than in Emacs 20. (Some |
10 |
|
distributions, such as Debian, may already have applied such a patch.) |
11 |
|
|
12 |
|
--- lisp/un-define.el 6 Mar 2001 22:41:38 -0000 1.30 |
13 |
|
+++ lisp/un-define.el 19 Apr 2002 18:34:26 -0000 |
14 |
|
@@ -610,13 +624,21 @@ by calling post-read-conversion and pre- |
15 |
|
|
16 |
|
(mapcar |
17 |
|
(lambda (x) |
18 |
|
- (mapcar |
19 |
|
- (lambda (y) |
20 |
|
- (mucs-define-coding-system |
21 |
|
- (nth 0 y) (nth 1 y) (nth 2 y) |
22 |
|
- (nth 3 y) (nth 4 y) (nth 5 y) (nth 6 y)) |
23 |
|
- (coding-system-put (car y) 'alias-coding-systems (list (car x)))) |
24 |
|
- (cdr x))) |
25 |
|
+ (if (fboundp 'register-char-codings) |
26 |
|
+ ;; Mule 5, where we don't need the eol-type specified and |
27 |
|
+ ;; register-char-codings may be very slow for these coding |
28 |
|
+ ;; system definitions. |
29 |
|
+ (let ((y (cadr x))) |
30 |
|
+ (mucs-define-coding-system |
31 |
|
+ (car x) (nth 1 y) (nth 2 y) |
32 |
|
+ (nth 3 y) (nth 4 y) (nth 5 y))) |
33 |
|
+ (mapcar |
34 |
|
+ (lambda (y) |
35 |
|
+ (mucs-define-coding-system |
36 |
|
+ (nth 0 y) (nth 1 y) (nth 2 y) |
37 |
|
+ (nth 3 y) (nth 4 y) (nth 5 y) (nth 6 y)) |
38 |
|
+ (coding-system-put (car y) 'alias-coding-systems (list (car x))))) |
39 |
|
+ (cdr x))) |
40 |
|
`((utf-8 |
41 |
|
(utf-8-unix |
42 |
|
?u "UTF-8 coding system" |
43 |
|
|
44 |
|
Note that Emacs 21 has native support for (non-CJK) Unicode, so you |
45 |
|
may not need Mule-UCS to edit Western utf-8 text, for instance. There |
46 |
|
are various enhancements at <URL:ftp://dlpx1.dl.ac.uk/fx/emacs/Mule> |
47 |
|
which improve Emacs 21's handling of non-ASCII text including dealing |
48 |
|
with CJK Unicode. |
49 |
|
|
50 |
* Building Emacs with GCC 2.9x fails in the `src' directory. |
* Building Emacs with GCC 2.9x fails in the `src' directory. |
51 |
|
|
52 |
This may happen if you use a development version of GNU `cpp' from one |
This may happen if you use a development version of GNU `cpp' from one |
430 |
appropriate keyboard encoding automatically, but it doesn't do that |
appropriate keyboard encoding automatically, but it doesn't do that |
431 |
yet.) |
yet.) |
432 |
|
|
433 |
Multilingual text put into the Windows clipboard by other Windows |
Windows uses UTF-16 encoding to deal with multilingual text (text not |
434 |
applications cannot be safely pasted into Emacs (as of v21.2). This |
encodable in the `system codepage') in the clipboard. To deal with |
435 |
is because Windows uses Unicode to represent multilingual text, but |
this, load the library `utf-16' and use `set-selection-coding-system' |
436 |
Emacs does not yet support Unicode well enough to decode it. This |
to set the clipboard coding system to `utf-16-le-dos'. This won't |
437 |
means that Emacs can only interchange non-ASCII text with other |
cope with Far Eastern (`CJK') text; if necessary, install the Mule-UCS |
438 |
Windows programs if the characters are in the system codepage. |
package, whose `utf-16-le-dos' coding system does encode a lot of CJK |
439 |
Reportedly, a partial solution is to install the Mule-UCS package and |
characters. |
|
set selection-coding-system to utf-16-le-dos. |
|
440 |
|
|
441 |
The %h format specifier for format-time-string does not work on Windows. |
The %h format specifier for format-time-string does not work on Windows. |
442 |
The %b format specifier does not produce abbreviated month names with |
The %b format specifier does not produce abbreviated month names with |
928 |
|
|
929 |
To work around this, install some add-on package such as Mule-UCS. |
To work around this, install some add-on package such as Mule-UCS. |
930 |
|
|
|
* Problems when using Emacs with UTF-8 locales |
|
|
|
|
|
Some systems, including recent versions of GNU/Linux, have terminals |
|
|
or X11 subsystems that can be configured to provide Unicode/UTF-8 |
|
|
input and display. Normally, such a system sets environment variables |
|
|
such as LANG, LC_CTYPE, or LC_ALL to a string which ends with a |
|
|
`.UTF-8'. For example, a system like this in a French locale might |
|
|
use `fr_FR.UTF-8' as the value of LANG. |
|
|
|
|
|
Since Unicode support in Emacs, as of v21.2, is not yet complete (see |
|
|
the previous entry in this file), UTF-8 support is not enabled by |
|
|
default, even in UTF-8 locales. Thus, some Emacs features, such as |
|
|
non-ASCII keyboard input, might appear to be broken in these locales. |
|
|
To solve these problems, you need to turn on some options in your |
|
|
`.emacs' file. Specifically, the following customizations should make |
|
|
Emacs work correctly with UTF-8 input and text: |
|
|
|
|
|
(setq locale-coding-system 'utf-8) |
|
|
(set-terminal-coding-system 'utf-8) |
|
|
(set-keyboard-coding-system 'utf-8) |
|
|
(set-selection-coding-system 'utf-8) |
|
|
(prefer-coding-system 'utf-8) |
|
|
|
|
931 |
* The `oc-unicode' package doesn't work with Emacs 21. |
* The `oc-unicode' package doesn't work with Emacs 21. |
932 |
|
|
933 |
This package tries to define more private charsets than there are free |
This package tries to define more private charsets than there are free |