From: Bruno H. <br...@cl...> - 2011-05-18 23:50:32
|
Hi Sam, > it appears that clisp can have !LANGUAGE_STATIC && !GNU_GETTEXT. > i.e., no gettext but the language is dynamic. > what does it mean? whats the point? A long time ago, the English and German strings were coded in the .d and .lisp files, and clisp could be compiled in 3 ways: - LANGUAGE_STATIC: the language is hardcoded (2 possible choices). - !LANGUAGE_STATIC && !GNU_GETTEXT: the language is settable at runtime (2 possible choices). - !LANGUAGE_STATIC && GNU_GETTEXT: the language is settable at runtime (more than 2 possible choices). Then, the German strings were moved out to .po files, and the situation is: - LANGUAGE_STATIC: the language is hardcoded (1 possible choice). - !LANGUAGE_STATIC && !GNU_GETTEXT: the language is settable at runtime (1 possible choice). - !LANGUAGE_STATIC && GNU_GETTEXT: the language is settable at runtime (more than 1 possible choice). The first and second ways were kept distinct, because I thought there could be one more change in i18n methodology. But GNU gettext and separate PO files are pretty well established by now; it's unlikely to change again. Therefore you can drop the first or second way, and drop the LANGUAGE_STATIC macro in the process. Bruno -- In memoriam Eli Cohen <http://en.wikipedia.org/wiki/Eli_Cohen> |
From: Sam S. <sd...@gn...> - 2011-05-19 14:03:57
|
Hi Bruno, > * Bruno Haible <oe...@py...t> [2011-05-19 01:50:21 +0200]: > > you can drop the LANGUAGE_STATIC macro. thanks. now, what about HAVE_ENVIRONMENT? can this be dropped as well? presumably yes... -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 11.0.60900031 http://ffii.org http://thereligionofpeace.com http://mideasttruth.com http://honestreporting.com http://dhimmi.com http://www.memritv.org Only adults have difficulty with child-proof caps. |
From: Sam S. <sd...@gn...> - 2011-05-19 14:32:35
|
Hi Bruno, > now, what about HAVE_ENVIRONMENT? > can this be dropped as well? > presumably yes... there are quite a few other "options" which are always defined but which are unlikely to be ever turned off: MACHINE_KNOWN LOGICAL_PATHNAMES HAVE_SHELL (but not GENERIC_STREAMS). How about removing them too? -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 11.0.60900031 http://iris.org.il http://ffii.org http://truepeace.org http://jihadwatch.org http://memri.org http://camera.org http://pmw.org.il Good: you CAN configure everything. Bad: you WILL configure everything. |
From: Sam S. <sd...@gn...> - 2011-05-19 19:59:36
|
Hi Bruno, Do you know of any system (existing or planned or imagined) for which it would make sense to define PATHNAME_EXT and undefine PATHNAME_NOEXT? -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 11.0.60900031 http://mideasttruth.com http://www.memritv.org http://palestinefacts.org http://openvotingconsortium.org http://memri.org Takeoffs are optional. Landings are mandatory. |