Mercurial > hg > xemacs-beta
comparison lib-src/make-msgfile.lex @ 2367:ecf1ebac70d8
[xemacs-hg @ 2004-11-04 23:05:23 by ben]
commit mega-patch
configure.in: Turn off -Winline and -Wchar-subscripts.
Use the right set of cflags when compiling modules.
Rewrite ldap configuration to separate the inclusion of lber
(needed in recent Cygwin) from the basic checks for the
needed libraries.
add a function for MAKE_JUNK_C; initially code was added to
generate xemacs.def using this, but it will need to be rewritten.
add an rm -f for junk.c to avoid weird Cygwin bug with cp -f onto
an existing file.
Sort list of auto-detected functions and eliminate unused checks for
stpcpy, setlocale and getwd.
Add autodetection of Cygwin scanf problems
BETA: Rewrite section on configure to indicate what flags are important
and what not.
digest-doc.c, make-dump-id.c, profile.c, sorted-doc.c: Add proper decls for main().
make-msgfile.c: Document that this is old junk.
Move proposal to text.c.
make-msgfile.lex: Move proposal to text.c.
make-mswin-unicode.pl: Convert error-generating code so that the entire message will
be seen as a single unrecognized token.
mule/mule-ccl.el: Update docs.
lispref/mule.texi: Update CCL docs.
ldap/eldap.c: Mule-ize.
Use EXTERNAL_LIST_LOOP_2 instead of deleted EXTERNAL_LIST_LOOP.
* XEmacs 21.5.18 "chestnut" is released.
---------------------------------------------------------------
MULE-RELATED WORK:
---------------------------------------------------------------
---------------------------
byte-char conversion
---------------------------
buffer.c, buffer.h, insdel.c, text.c: Port FSF algorithm for byte-char conversion, replacing broken
previous version. Track the char position of the gap. Add
functions to do char-byte conversion downwards as well as upwards.
Move comments about algorithm workings to internals manual.
---------------------------
work on types
---------------------------
alloc.c, console-x-impl.h, dump-data.c, dump-data.h, dumper.c, dialog-msw.c, dired-msw.c, doc.c, editfns.c, esd.c, event-gtk.h, event-msw.c, events.c, file-coding.c, file-coding.h, fns.c, glyphs-eimage.c, glyphs-gtk.c, glyphs-msw.c, glyphs-shared.c, glyphs-x.c, glyphs.c, glyphs.h, gui.c, hpplay.c, imgproc.c, intl-win32.c, lrecord.h, lstream.c, keymap.c, lisp.h, libsst.c, linuxplay.c, miscplay.c, miscplay.h, mule-coding.c, nas.c, nt.c, ntheap.c, ntplay.c, objects-msw.c, objects-tty.c, objects-x.c, print.c, process-nt.c, process.c, redisplay.h, select-common.h, select-gtk.c, select-x.c, sgiplay.c, sound.c, sound.h, sunplay.c, sysfile.h, sysdep.c, syswindows.h, text.c, unexnt.c, win32.c, xgccache.c: Further work on types. This creates a full set of types for all
the basic semantics of `char' that I have so far identified, so that
its semantics can always be identified for the purposes of proper
Mule-safe code, and the raw use of `char' always avoided.
(1) More type renaming, for consistency of naming.
Char_ASCII -> Ascbyte
UChar_ASCII -> UAscbyte
Char_Binary -> CBinbyte
UChar_Binary -> Binbyte
SChar_Binary -> SBinbyte
(2) Introduce Rawbyte, CRawbyte, Boolbyte, Chbyte, UChbyte, and
Bitbyte and use them.
(3) New types Itext, Wexttext and Textcount for separating out
the concepts of bytes and textual units (different under UTF-16
and UTF-32, which are potential internal encodings).
(4) qxestr*_c -> qxestr*_ascii.
lisp.h: New; goes with other qxe() functions. #### Maybe goes in a
different section.
lisp.h: Group generic int-type defs together with EMACS_INT defs.
lisp.h: * lisp.h (WEXTTEXT_IS_WIDE)
New defns.
lisp.h: New type to replace places where int occurs as a boolean.
It's signed because occasionally people may want to use -1 as
an error value, and because unsigned ints are viral -- see comments
in the internals manual against using them.
dynarr.c: int -> Bytecount.
---------------------------
Mule-izing
---------------------------
device-x.c: Partially Mule-ize.
dumper.c, dumper.h: Mule-ize. Use Rawbyte. Use stderr_out not printf. Use wext_*().
sysdep.c, syswindows.h, text.c: New Wexttext API for manipulation of external text that may be
Unicode (e.g. startup code under Windows).
emacs.c: Mule-ize. Properly deal with argv in external encoding.
Use wext_*() and Wexttext. Use Rawbyte.
#if 0 some old junk on SCO that is unlikely to be correct.
Rewrite allocation code in run-temacs.
emacs.c, symsinit.h, win32.c: Rename win32 init function and call it even earlier, to
initialize mswindows_9x_p even earlier, for use in startup code
(XEUNICODE_P).
process.c: Use _wenviron not environ under Windows, to get Unicode environment
variables.
event-Xt.c: Mule-ize drag-n-drop related stuff.
dragdrop.c, dragdrop.h, frame-x.c: Mule-ize.
text.h: Add some more stand-in defines for particular kinds of conversion;
use in Mule-ization work in frame-x.c etc.
---------------------------
Freshening
---------------------------
intl-auto-encap-win32.c, intl-auto-encap-win32.h: Regenerate.
---------------------------
Unicode-work
---------------------------
intl-win32.c, syswindows.h: Factor out common options to MultiByteToWideChar and
WideCharToMultiByte. Add convert_unicode_to_multibyte_malloc()
and convert_unicode_to_multibyte_dynarr() and use. Add stuff for
alloca() conversion of multibyte/unicode.
alloc.c: Use dfc_external_data_len() in case of unicode coding system.
alloc.c, mule-charset.c: Don't zero out and reinit charset Unicode tables. This fucks up
dump-time loading. Anyway, either we load them at dump time or
run time, never both.
unicode.c: Dump the blank tables as well.
---------------------------------------------------------------
DOCUMENTATION, MOSTLY MULE-RELATED:
---------------------------------------------------------------
EmacsFrame.c, emodules.c, event-Xt.c, fileio.c, input-method-xlib.c, mule-wnnfns.c, redisplay-gtk.c, redisplay-tty.c, redisplay-x.c, regex.c, sysdep.c: Add comment about Mule work needed.
text.h: Add more documentation describing why DFC routines were not written
to return their value. Add some other DFC documentation.
console-msw.c, console-msw.h: Add pointer to docs in win32.c.
emacs.c: Add comments on sources of doc info.
text.c, charset.h, unicode.c, intl-win32.c, intl-encap-win32.c, text.h, file-coding.c, mule-coding.c: Collect background comments and related to text matters and
internationalization, and proposals for work to be done, in text.c
or Internals manual, stuff related to specific textual API's in
text.h, and stuff related to internal implementation of Unicode
conversion in unicode.c. Put lots of pointers to the comments to
make them easier to find.
s/mingw32.h, s/win32-common.h, s/win32-native.h, s/windowsnt.h, win32.c: Add bunches of new documentation on the different kinds of
builds and environments under Windows and how they work.
Collect this info in win32.c. Add pointers to these docs in
the relevant s/* files.
emacs.c: Document places with long comments.
Remove comment about exiting, move to internals manual, put
in pointer.
event-stream.c: Move docs about event queues and focus to internals manual, put
in pointer.
events.h: Move docs about event stream callbacks to internals manual, put
in pointer.
profile.c, redisplay.c, signal.c: Move documentation to the Internals manual.
process-nt.c: Add pointer to comment in win32-native.el.
lisp.h: Add comments about some comment conventions.
lisp.h: Add comment about the second argument.
device-msw.c, redisplay-msw.c: @@#### comments are out-of-date.
---------------------------------------------------------------
PDUMP WORK (MOTIVATED BY UNICODE CHANGES)
---------------------------------------------------------------
alloc.c, buffer.c, bytecode.c, console-impl.h, console.c, device.c, dumper.c, lrecord.h, elhash.c, emodules.h, events.c, extents.c, frame.c, glyphs.c, glyphs.h, mule-charset.c, mule-coding.c, objects.c, profile.c, rangetab.c, redisplay.c, specifier.c, specifier.h, window.c, lstream.c, file-coding.h, file-coding.c: PDUMP:
Properly implement dump_add_root_block(), which never worked before,
and is necessary for dumping Unicode tables.
Pdump name changes for accuracy:
XD_STRUCT_PTR -> XD_BLOCK_PTR.
XD_STRUCT_ARRAY -> XD_BLOCK_ARRAY.
XD_C_STRING -> XD_ASCII_STRING.
*_structure_* -> *_block_*.
lrecord.h: some comments added about
dump_add_root_block() vs dump_add_root_block_ptr().
extents.c: remove incorrect comment about pdump problems with gap array.
---------------------------------------------------------------
ALLOCATION
---------------------------------------------------------------
abbrev.c, alloc.c, bytecode.c, casefiddle.c, device-msw.c, device-x.c, dired-msw.c, doc.c, doprnt.c, dragdrop.c, editfns.c, emodules.c, file-coding.c, fileio.c, filelock.c, fns.c, glyphs-eimage.c, glyphs-gtk.c, glyphs-msw.c, glyphs-x.c, gui-msw.c, gui-x.c, imgproc.c, intl-win32.c, lread.c, menubar-gtk.c, menubar.c, nt.c, objects-msw.c, objects-x.c, print.c, process-nt.c, process-unix.c, process.c, realpath.c, redisplay.c, search.c, select-common.c, symbols.c, sysdep.c, syswindows.h, text.c, text.h, ui-byhand.c: New macros {alloca,xnew}_{itext,{i,ext,raw,bin,asc}bytes} for
more convenient allocation of these commonly requested items.
Modify functions to use alloca_ibytes, alloca_array, alloca_extbytes,
xnew_ibytes, etc. also XREALLOC_ARRAY, xnew.
alloc.c: Rewrite the allocation functions to factor out repeated code.
Add assertions for freeing dumped data.
lisp.h: Moved down and consolidated with other allocation stuff.
lisp.h, dynarr.c: New functions for allocation that's very efficient when mostly in
LIFO order.
lisp.h, text.c, text.h: Factor out some stuff for general use by alloca()-conversion funs.
text.h, lisp.h: Fill out convenience routines for allocating various kinds of
bytes and put them in lisp.h. Use them in place of xmalloc(),
ALLOCA().
text.h: Fill out the convenience functions so the _MALLOC() kinds match
the alloca() kinds.
---------------------------------------------------------------
ERROR-CHECKING
---------------------------------------------------------------
text.h: Create ASSERT_ASCTEXT_ASCII() and ASSERT_ASCTEXT_ASCII_LEN()
from similar Eistring checkers and change the Eistring checkers to
use them instead.
---------------------------------------------------------------
MACROS IN LISP.H
---------------------------------------------------------------
lisp.h: Redo GCPRO declarations. Create a "base" set of functions that can
be used to generate any kind of gcpro sets -- regular, ngcpro,
nngcpro, private ones used in GC_EXTERNAL_LIST_LOOP_2.
buffer.c, callint.c, chartab.c, console-msw.c, device-x.c, dialog-msw.c, dired.c, extents.c, ui-gtk.c, rangetab.c, nt.c, mule-coding.c, minibuf.c, menubar-msw.c, menubar.c, menubar-gtk.c, lread.c, lisp.h, gutter.c, glyphs.c, glyphs-widget.c, fns.c, fileio.c, file-coding.c, specifier.c: Eliminate EXTERNAL_LIST_LOOP, which does not check for circularities.
Use EXTERNAL_LIST_LOOP_2 instead or EXTERNAL_LIST_LOOP_3
or EXTERNAL_PROPERTY_LIST_LOOP_3 or GC_EXTERNAL_LIST_LOOP_2
(new macro). Removed/redid comments on EXTERNAL_LIST_LOOP.
---------------------------------------------------------------
SPACING FIXES
---------------------------------------------------------------
callint.c, hftctl.c, number-gmp.c, process-unix.c: Spacing fixes.
---------------------------------------------------------------
FIX FOR GEOMETRY PROBLEM IN FIRST FRAME
---------------------------------------------------------------
unicode.c: Add workaround for newlib bug in sscanf() [should be fixed by
release 1.5.12 of Cygwin].
toolbar.c: bug fix for problem of initial frame being 77 chars wide on Windows.
will be overridden by my other ws.
---------------------------------------------------------------
FIX FOR LEAKING PROCESS HANDLES:
---------------------------------------------------------------
process-nt.c: Fixes for leaking handles. Inspired by work done by Adrian Aichner
<adrian@xemacs.org>.
---------------------------------------------------------------
FIX FOR CYGWIN BUG (Unicode-related):
---------------------------------------------------------------
unicode.c: Add workaround for newlib bug in sscanf() [should be fixed by
release 1.5.12 of Cygwin].
---------------------------------------------------------------
WARNING FIXES:
---------------------------------------------------------------
console-stream.c: `reinit' is unused.
compiler.h, event-msw.c, frame-msw.c, intl-encap-win32.c, text.h: Add stuff to deal with ANSI-aliasing warnings I got.
regex.c: Gather includes together to avoid warning.
---------------------------------------------------------------
CHANGES TO INITIALIZATION ROUTINES:
---------------------------------------------------------------
buffer.c, emacs.c, console.c, debug.c, device-x.c, device.c, dragdrop.c, emodules.c, eval.c, event-Xt.c, event-gtk.c, event-msw.c, event-stream.c, event-tty.c, events.c, extents.c, faces.c, file-coding.c, fileio.c, font-lock.c, frame-msw.c, glyphs-widget.c, glyphs.c, gui-x.c, insdel.c, lread.c, lstream.c, menubar-gtk.c, menubar-x.c, minibuf.c, mule-wnnfns.c, objects-msw.c, objects.c, print.c, scrollbar-x.c, search.c, select-x.c, text.c, undo.c, unicode.c, window.c, symsinit.h: Call reinit_*() functions directly from emacs.c, for clarity.
Factor out some redundant init code. Move disallowed stuff
that had crept into vars_of_glyphs() into complex_vars_of_glyphs().
Call init_eval_semi_early() from eval.c not in the middle of
vars_of_() in emacs.c since there should be no order dependency
in the latter calls.
---------------------------------------------------------------
ARMAGEDDON:
---------------------------------------------------------------
alloc.c, emacs.c, lisp.h, print.c: Rename inhibit_non_essential_printing_operations to
inhibit_non_essential_conversion_operations.
text.c: Assert on !inhibit_non_essential_conversion_operations.
console-msw.c, print.c: Don't do conversion in SetConsoleTitle or FindWindow to avoid
problems during armageddon. Put #errors for NON_ASCII_INTERNAL_FORMAT
in places where problems would arise.
---------------------------------------------------------------
CHANGES TO THE BUILD PROCEDURE:
---------------------------------------------------------------
config.h.in, s/cxux.h, s/usg5-4-2.h, m/powerpc.h: Add comment about correct ordering of this file.
Rearrange everything to follow this -- put all #undefs together
and before the s&m files. Add undefs for HAVE_ALLOCA, C_ALLOCA,
BROKEN_ALLOCA_IN_FUNCTION_CALLS, STACK_DIRECTION. Remove unused
HAVE_STPCPY, HAVE_GETWD, HAVE_SETLOCALE.
m/gec63.h: Deleted; totally broken, not used at all, not in FSF.
m/7300.h, m/acorn.h, m/alliant-2800.h, m/alliant.h, m/altos.h, m/amdahl.h, m/apollo.h, m/att3b.h, m/aviion.h, m/celerity.h, m/clipper.h, m/cnvrgnt.h, m/convex.h, m/cydra5.h, m/delta.h, m/delta88k.h, m/dpx2.h, m/elxsi.h, m/ews4800r.h, m/gould.h, m/hp300bsd.h, m/hp800.h, m/hp9000s300.h, m/i860.h, m/ibmps2-aix.h, m/ibmrs6000.h, m/ibmrt-aix.h, m/ibmrt.h, m/intel386.h, m/iris4d.h, m/iris5d.h, m/iris6d.h, m/irist.h, m/isi-ov.h, m/luna88k.h, m/m68k.h, m/masscomp.h, m/mg1.h, m/mips-nec.h, m/mips-siemens.h, m/mips.h, m/news.h, m/nh3000.h, m/nh4000.h, m/ns32000.h, m/orion105.h, m/pfa50.h, m/plexus.h, m/pmax.h, m/powerpc.h, m/pyrmips.h, m/sequent-ptx.h, m/sequent.h, m/sgi-challenge.h, m/symmetry.h, m/tad68k.h, m/tahoe.h, m/targon31.h, m/tekxd88.h, m/template.h, m/tower32.h, m/tower32v3.h, m/ustation.h, m/vax.h, m/wicat.h, m/xps100.h: Delete C_ALLOCA, HAVE_ALLOCA, STACK_DIRECTION,
BROKEN_ALLOCA_IN_FUNCTION_CALLS. All of this is auto-detected.
When in doubt, I followed recent FSF sources, which also have
these things deleted.
author | ben |
---|---|
date | Thu, 04 Nov 2004 23:08:28 +0000 |
parents | 8de8e3f6228a |
children | c50b0b3c7b8d |
comparison
equal
deleted
inserted
replaced
2366:2a392e0c390a | 2367:ecf1ebac70d8 |
---|---|
22 the Free Software Foundation, Inc., 59 Temple Place - Suite 330, | 22 the Free Software Foundation, Inc., 59 Temple Place - Suite 330, |
23 Boston, MA 02111-1307, USA. */ | 23 Boston, MA 02111-1307, USA. */ |
24 | 24 |
25 /* Written by Ben Wing, November 1994. Some code based on earlier | 25 /* Written by Ben Wing, November 1994. Some code based on earlier |
26 make-msgfile.c. */ | 26 make-msgfile.c. */ |
27 | |
28 /* See text.c for a proposal about how this whole system should work. */ | |
27 | 29 |
28 /* Note: there is still much work to be done on this. | 30 /* Note: there is still much work to be done on this. |
29 | 31 |
30 1) Definition of Arg below won't handle a generalized argument | 32 1) Definition of Arg below won't handle a generalized argument |
31 as might appear in a function call. This is fine for DEFUN | 33 as might appear in a function call. This is fine for DEFUN |
58 | 60 |
59 --ben | 61 --ben |
60 | 62 |
61 */ | 63 */ |
62 | 64 |
63 /* Long comment from jwz: | |
64 | |
65 (much of this comment is outdated, and a lot of it is actually | |
66 implemented) | |
67 | |
68 | |
69 PROPOSAL FOR HOW THIS ALL OUGHT TO WORK | |
70 this isn't implemented yet, but this is the plan-in-progress | |
71 | |
72 | |
73 In general, it's accepted that the best way to internationalize is for all | |
74 messages to be referred to by a symbolic name (or number) and come out of a | |
75 table or tables, which are easy to change. | |
76 | |
77 However, with Emacs, we've got the task of internationalizing a huge body | |
78 of existing code, which already contains messages internally. | |
79 | |
80 For the C code we've got two options: | |
81 | |
82 - Use a Sun-like gettext() form, which takes an "english" string which | |
83 appears literally in the source, and uses that as a hash key to find | |
84 a translated string; | |
85 - Rip all of the strings out and put them in a table. | |
86 | |
87 In this case, it's desirable to make as few changes as possible to the C | |
88 code, to make it easier to merge the code with the FSF version of emacs | |
89 which won't ever have these changes made to it. So we should go with the | |
90 former option. | |
91 | |
92 The way it has been done (between 19.8 and 19.9) was to use gettext(), but | |
93 *also* to make massive changes to the source code. The goal now is to use | |
94 gettext() at run-time and yet not require a textual change to every line | |
95 in the C code which contains a string constant. A possible way to do this | |
96 is described below. | |
97 | |
98 (gettext() can be implemented in terms of catgets() for non-Sun systems, so | |
99 that in itself isn't a problem.) | |
100 | |
101 For the Lisp code, we've got basically the same options: put everything in | |
102 a table, or translate things implicitly. | |
103 | |
104 Another kink that lisp code introduces is that there are thousands of third- | |
105 party packages, so changing the source for all of those is simply not an | |
106 option. | |
107 | |
108 Is it a goal that if some third party package displays a message which is | |
109 one we know how to translate, then we translate it? I think this is a | |
110 worthy goal. It remains to be seen how well it will work in practice. | |
111 | |
112 So, we should endeavor to minimize the impact on the lisp code. Certain | |
113 primitive lisp routines (the stuff in lisp/prim/, and especially in | |
114 cmdloop.el and minibuf.el) may need to be changed to know about translation, | |
115 but that's an ideologically clean thing to do because those are considered | |
116 a part of the emacs substrate. | |
117 | |
118 However, if we find ourselves wanting to make changes to, say, RMAIL, then | |
119 something has gone wrong. (Except to do things like remove assumptions | |
120 about the order of words within a sentence, or how pluralization works.) | |
121 | |
122 There are two parts to the task of displaying translated strings to the | |
123 user: the first is to extract the strings which need to be translated from | |
124 the sources; and the second is to make some call which will translate those | |
125 strings before they are presented to the user. | |
126 | |
127 The old way was to use the same form to do both, that is, GETTEXT() was both | |
128 the tag that we searched for to build a catalog, and was the form which did | |
129 the translation. The new plan is to separate these two things more: the | |
130 tags that we search for to build the catalog will be stuff that was in there | |
131 already, and the translation will get done in some more centralized, lower | |
132 level place. | |
133 | |
134 This program (make-msgfile.c) addresses the first part, extracting the | |
135 strings. | |
136 | |
137 For the emacs C code, we need to recognize the following patterns: | |
138 | |
139 message ("string" ... ) | |
140 error ("string") | |
141 report_file_error ("string" ... ) | |
142 signal_simple_error ("string" ... ) | |
143 signal_simple_error_2 ("string" ... ) | |
144 | |
145 build_translated_string ("string") | |
146 #### add this and use it instead of build_string() in some places. | |
147 | |
148 yes_or_no_p ("string" ... ) | |
149 #### add this instead of funcalling Qyes_or_no_p directly. | |
150 | |
151 barf_or_query_if_file_exists #### restructure this | |
152 check all callers of Fsignal #### restructure these | |
153 signal_error (Qerror ... ) #### change all of these to error() | |
154 | |
155 And we also parse out the `interactive' prompts from DEFUN() forms. | |
156 | |
157 #### When we've got a string which is a candidate for translation, we | |
158 should ignore it if it contains only format directives, that is, if | |
159 there are no alphabetic characters in it that are not a part of a `%' | |
160 directive. (Careful not to translate either "%s%s" or "%s: ".) | |
161 | |
162 For the emacs Lisp code, we need to recognize the following patterns: | |
163 | |
164 (message "string" ... ) | |
165 (error "string" ... ) | |
166 (format "string" ... ) | |
167 (read-from-minibuffer "string" ... ) | |
168 (read-shell-command "string" ... ) | |
169 (y-or-n-p "string" ... ) | |
170 (yes-or-no-p "string" ... ) | |
171 (read-file-name "string" ... ) | |
172 (temp-minibuffer-message "string") | |
173 (query-replace-read-args "string" ... ) | |
174 | |
175 I expect there will be a lot like the above; basically, any function which | |
176 is a commonly used wrapper around an eventual call to `message' or | |
177 `read-from-minibuffer' needs to be recognized by this program. | |
178 | |
179 | |
180 (dgettext "domain-name" "string") #### do we still need this? | |
181 | |
182 things that should probably be restructured: | |
183 `princ' in cmdloop.el | |
184 `insert' in debug.el | |
185 face-interactive | |
186 help.el, syntax.el all messed up | |
187 | |
188 BPW: (format) is a tricky case. If I use format to create a string | |
189 that I then send to a file, I probably don't want the string translated. | |
190 On the other hand, If the string gets used as an argument to (y-or-n-p) | |
191 or some such function, I do want it translated, and it needs to be | |
192 translated before the %s and such are replaced. The proper solution | |
193 here is for (format) and other functions that call gettext but don't | |
194 immediately output the string to the user to add the translated (and | |
195 formatted) string as a string property of the object, and have | |
196 functions that output potentially translated strings look for a | |
197 "translated string" property. Of course, this will fail if someone | |
198 does something like | |
199 | |
200 (y-or-n-p (concat (if you-p "Do you " "Does he ") | |
201 (format "want to delete %s? " filename)))) | |
202 | |
203 But you shouldn't be doing things like this anyway. | |
204 | |
205 BPW: Also, to avoid excessive translating, strings should be marked | |
206 as translated once they get translated, and further calls to gettext | |
207 don't do any more translating. Otherwise, a call like | |
208 | |
209 (y-or-n-p (format "Delete %s? " filename)) | |
210 | |
211 would cause translation on both the pre-formatted and post-formatted | |
212 strings, which could lead to weird results in some cases (y-or-n-p | |
213 has to translate its argument because someone could pass a string to | |
214 it directly). Note that the "translating too much" solution outlined | |
215 below could be implemented by just marking all strings that don't | |
216 come from a .el or .elc file as already translated. | |
217 | |
218 Menu descriptors: one way to extract the strings in menu labels would be | |
219 to teach this program about "^(defvar .*menu\n" forms; that's probably | |
220 kind of hard, though, so perhaps a better approach would be to make this | |
221 program recognize lines of the form | |
222 | |
223 "string" ... ;###translate | |
224 | |
225 where the magic token ";###translate" on a line means that the string | |
226 constant on this line should go into the message catalog. This is analogous | |
227 to the magic ";###autoload" comments, and to the magic comments used in the | |
228 EPSF structuring conventions. | |
229 | |
230 ----- | |
231 So this program manages to build up a catalog of strings to be translated. | |
232 To address the second part of the problem, of actually looking up the | |
233 translations, there are hooks in a small number of low level places in | |
234 emacs. | |
235 | |
236 Assume the existence of a C function gettext(str) which returns the | |
237 translation of `str' if there is one, otherwise returns `str'. | |
238 | |
239 - message() takes a char* as its argument, and always filters it through | |
240 gettext() before displaying it. | |
241 | |
242 - errors are printed by running the lisp function `display-error' which | |
243 doesn't call `message' directly (it princ's to streams), so it must be | |
244 carefully coded to translate its arguments. This is only a few lines | |
245 of code. | |
246 | |
247 - Fread_minibuffer_internal() is the lowest level interface to all minibuf | |
248 interactions, so it is responsible for translating the value that will go | |
249 into Vminibuf_prompt. | |
250 | |
251 - Fpopup_menu filters the menu titles through gettext(). | |
252 | |
253 The above take care of 99% of all messages the user ever sees. | |
254 | |
255 - The lisp function temp-minibuffer-message translates its arg. | |
256 | |
257 - query-replace-read-args is funny; it does | |
258 (setq from (read-from-minibuffer (format "%s: " string) ... )) | |
259 (setq to (read-from-minibuffer (format "%s %s with: " string from) ... )) | |
260 | |
261 What should we do about this? We could hack query-replace-read-args to | |
262 translate its args, but might this be a more general problem? I don't | |
263 think we ought to translate all calls to format. We could just change | |
264 the calling sequence, since this is odd in that the first %s wants to be | |
265 translated but the second doesn't. | |
266 | |
267 | |
268 Solving the "translating too much" problem: | |
269 The concern has been raised that in this situation: | |
270 - "Help" is a string for which we know a translation; | |
271 - someone visits a file called Help, and someone does something | |
272 contrived like (error buffer-file-name) | |
273 then we would display the translation of Help, which would not be correct. | |
274 We can solve this by adding a bit to Lisp_String objects which identifies | |
275 them as having been read as literal constants from a .el or .elc file (as | |
276 opposed to having been constructed at run time as it would in the above | |
277 case.) To solve this: | |
278 | |
279 - Fmessage() takes a lisp string as its first argument. | |
280 If that string is a constant, that is, was read from a source file | |
281 as a literal, then it calls message() with it, which translates. | |
282 Otherwise, it calls message_no_translate(), which does not translate. | |
283 | |
284 - Ferror() (actually, Fsignal() when condition is Qerror) works similarly. | |
285 */ | |
286 | |
287 /* Some notes: | 65 /* Some notes: |
288 | 66 |
289 -- {Arg} below could get confused by commas inside of quotes. | 67 -- {Arg} below could get confused by commas inside of quotes. |
290 -- {LispToken} below can match some things that are not tokens (e.g. | 68 -- {LispToken} below can match some things that are not tokens (e.g. |
291 numbers) but for all practical purposes it should be fine. | 69 numbers) but for all practical purposes it should be fine. |