Mercurial > hg > xemacs-beta
annotate etc/InstallGuide @ 4690:257b468bf2ca
Move the #'query-coding-region implementation to C.
This is necessary because there is no reasonable way to access the
corresponding mswindows-multibyte functionality from Lisp, and we need such
functionality if we're going to have a reliable and portable
#'query-coding-region implementation. However, this change doesn't yet
provide #'query-coding-region for the mswindow-multibyte coding systems,
there should be no functional differences between an XEmacs with this change
and one without it.
src/ChangeLog addition:
2009-09-19 Aidan Kehoe <kehoea@parhasard.net>
Move the #'query-coding-region implementation to C.
This is necessary because there is no reasonable way to access the
corresponding mswindows-multibyte functionality from Lisp, and we
need such functionality if we're going to have a reliable and
portable #'query-coding-region implementation. However, this
change doesn't yet provide #'query-coding-region for the
mswindow-multibyte coding systems, there should be no functional
differences between an XEmacs with this change and one without it.
* mule-coding.c (struct fixed_width_coding_system):
Add a new coding system type, fixed_width, and implement it. It
uses the CCL infrastructure but has a much simpler creation API,
and its own query_method, formerly in lisp/mule/mule-coding.el.
* unicode.c:
Move the Unicode query method implementation here from
unicode.el.
* lisp.h: Declare Fmake_coding_system_internal, Fcopy_range_table
here.
* intl-win32.c (complex_vars_of_intl_win32):
Use Fmake_coding_system_internal, not Fmake_coding_system.
* general-slots.h: Add Qsucceeded, Qunencodable, Qinvalid_sequence
here.
* file-coding.h (enum coding_system_variant):
Add fixed_width_coding_system here.
(struct coding_system_methods):
Add query_method and query_lstream_method to the coding system
methods.
Provide flags for the query methods.
Declare the default query method; initialise it correctly in
INITIALIZE_CODING_SYSTEM_TYPE.
* file-coding.c (default_query_method):
New function, the default query method for coding systems that do
not set it. Moved from coding.el.
(make_coding_system_1):
Accept new elements in PROPS in #'make-coding-system; aliases, a
list of aliases; safe-chars and safe-charsets (these were
previously accepted but not saved); and category.
(Fmake_coding_system_internal):
New function, what used to be #'make-coding-system--on Mule
builds, we've now moved some of the functionality of this to
Lisp.
(Fcoding_system_canonical_name_p):
Move this earlier in the file, since it's now called from within
make_coding_system_1.
(Fquery_coding_region):
Move the implementation of this here, from coding.el.
(complex_vars_of_file_coding):
Call Fmake_coding_system_internal, not Fmake_coding_system;
specify safe-charsets properties when we're a mule build.
* extents.h (mouse_highlight_priority, Fset_extent_priority,
Fset_extent_face, Fmap_extents):
Make these available to other C files.
lisp/ChangeLog addition:
2009-09-19 Aidan Kehoe <kehoea@parhasard.net>
Move the #'query-coding-region implementation to C.
* coding.el:
Consolidate code that depends on the presence or absence of Mule
at the end of this file.
(default-query-coding-region, query-coding-region):
Move these functions to C.
(default-query-coding-region-safe-charset-skip-chars-map):
Remove this variable, the corresponding C variable is
Vdefault_query_coding_region_chartab_cache in file-coding.c.
(query-coding-string): Update docstring to reflect actual multiple
values, be more careful about not modifying a range table that
we're currently mapping over.
(encode-coding-char): Make the implementation of this simpler.
(featurep 'mule): Autoload #'make-coding-system from
mule/make-coding-system.el if we're a mule build; provide an
appropriate compiler macro.
Do various non-mule compatibility things if we're not a mule
build.
* update-elc.el (additional-dump-dependencies):
Add mule/make-coding-system as a dump time dependency if we're a
mule build.
* unicode.el (ccl-encode-to-ucs-2):
(decode-char):
(encode-char):
Move these earlier in the file, for the sake of some byte compile
warnings.
(unicode-query-coding-region):
Move this to unicode.c
* mule/make-coding-system.el:
New file, not dumped. Contains the functionality to rework the
arguments necessary for fixed-width coding systems, and contains
the implementation of #'make-coding-system, which now calls
#'make-coding-system-internal.
* mule/vietnamese.el (viscii):
* mule/latin.el (iso-8859-2):
(windows-1250):
(iso-8859-3):
(iso-8859-4):
(iso-8859-14):
(iso-8859-15):
(iso-8859-16):
(iso-8859-9):
(macintosh):
(windows-1252):
* mule/hebrew.el (iso-8859-8):
* mule/greek.el (iso-8859-7):
(windows-1253):
* mule/cyrillic.el (iso-8859-5):
(koi8-r):
(koi8-u):
(windows-1251):
(alternativnyj):
(koi8-ru):
(koi8-t):
(koi8-c):
(koi8-o):
* mule/arabic.el (iso-8859-6):
(windows-1256):
Move all these coding systems to being of type fixed-width, not of
type CCL. This allows the distinct query-coding-region for them to
be in C, something which will eventually allow us to implement
query-coding-region for the mswindows-multibyte coding systems.
* mule/general-late.el (posix-charset-to-coding-system-hash):
Document why we're pre-emptively persuading the byte compiler that
the ELC for this file needs to be written using escape-quoted.
Call #'set-unicode-query-skip-chars-args, now the Unicode
query-coding-region implementation is in C.
* mule/thai-xtis.el (tis-620):
Don't bother checking whether we're XEmacs or not here.
* mule/mule-coding.el:
Move the eight bit fixed-width functionality from this file to
make-coding-system.el.
tests/ChangeLog addition:
2009-09-19 Aidan Kehoe <kehoea@parhasard.net>
* automated/mule-tests.el:
Check a coding system's type, not an 8-bit-fixed property, for
whether that coding system should be treated as a fixed-width
coding system.
* automated/query-coding-tests.el:
Don't test the query coding functionality for mswindows-multibyte
coding systems, it's not yet implemented.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sat, 19 Sep 2009 22:53:13 +0100 |
parents | 9ad43877534d |
children |
rev | line source |
---|---|
179 | 1 Introduction |
2 | |
3 Thank you for downloading XEmacs. We of the XEmacs development team | |
4 believe user satisfaction is our number one priority, and we hope that | |
5 you will be pleased with the power of our editor. Please follow all | |
6 of the instructions in order to enjoy a quick and easy installation. | |
7 | |
8 | |
9 Getting Started | |
10 | |
11 In this guide, information which you will need to supply will be enclosed in | |
12 angle brackets, <like this>. Commands which you will have to enter will be | |
13 indented, | |
14 | |
15 like this. | |
16 | |
17 You will need to provide a loading directory, in which to load the | |
18 material from tape (/tmp/xemacs is recommended), and a permanent | |
19 installation directory (/usr/local/xemacs is recommended). | |
20 | |
21 | |
22 Loading From Tape | |
23 | |
24 First create and change directory to the loading directory: | |
25 | |
26 mkdir <working directory> | |
27 cd <working directory> | |
28 | |
29 Now you are ready to load the software from tape. | |
30 | |
31 The specific device name needed to load the tape varies with hardware vendors, | |
32 and may be found in Appendix A, "Vendors and Device Names". | |
33 | |
34 Load the software from tape: | |
35 | |
36 tar xvf /dev/<device name> | |
37 | |
38 You have now loaded all of the software from tape, and are ready to compile and | |
39 install the XEmacs Text Editor. | |
40 | |
41 | |
42 Compiling and Installing the XEmacs Editor | |
43 | |
44 Compiling and installing the libraries is handled by a user-friendly shell | |
45 script. You will need to provide some information to the script, such as your | |
46 organization name and registration number. To run the script, type | |
47 | |
48 /bin/sh xemacs/xemacs.install -d <installation directory> | |
49 | |
50 Follow the script's directions, and provide the information which it prompts | |
51 for. | |
52 | |
53 When the script prompts you for the directory in which the distribution files | |
54 are located, you will find that you are unable to provide it with any directory | |
55 which the script will deem satisfactory. That is because it is necessary to | |
56 order the following additional parts which are necessary to continue with the | |
57 installation: | |
58 | |
59 Part Number Qty Name Price | |
60 | |
61 GM-96-3026 1 Goat, male 1000.00 | |
62 CB-13-2395 1 Candle, black 50.00 | |
63 CG-63-6376 1 Chalk dust container 10.00 | |
64 IB-89-3335 5 Incense sticks 5.00 | |
65 DE-44-8846 1 Dagger, ebon, curved 500.00 | |
66 AS-87-2319 1 Altar, silver 10000.00 | |
67 | |
68 Wait until the additional parts arrive; you will be ready to continue the | |
69 installation the next Friday the 13th at midnight. | |
70 | |
71 | |
72 Ritual for Successfully Completing Installation | |
73 | |
74 Stand in front of the computer. Pour out the chalk dust in an inscribed | |
75 pentagram around you; be sure that it is without breaks. Set an incense stick | |
76 at each of the five corners, the altar in front of the computer, and the candle | |
77 in front of the altar. | |
78 | |
79 Light each of the incense sticks and the candles, chanting in a low voice: | |
80 | |
81 Daemons and spirits of the netherworld | |
82 Forces of all that is chaotic and mysterious | |
83 Essence of Netscape and MicroSoft | |
84 | |
85 I am coming here to appease you | |
86 I offer you this goat | |
87 That my software may work | |
88 | |
89 I bind you here | |
90 Do not make my system crash | |
91 Let the software install as advertised | |
92 | |
93 Place the goat on the altar, and slaughter it with the dagger. | |
94 | |
95 May this goat feed you | |
96 Sate your lust for blood | |
97 Into it may your mischief fly | |
98 Not my computer | |
99 Make the software work | |
100 For this is the only way | |
101 | |
102 Then spit into the computer's ventilation slots. This will complete different | |
103 circuits inside the computer, causing its motherboard and cards to function in | |
104 ways that the engineers never intended, thereby making your system compatible | |
105 with our libraries. | |
106 | |
107 Reboot your computer. The installation is now complete. | |
108 | |
109 [This has undergone a minor rewrite for XEmacs. It originally | |
110 appeared on rec.humor.funny courtesy of jonathan seth hayward | |
111 <jhayward@students.uiuc.edu>, and is included by permission of the | |
112 author]. |