Re: !GNU_GETTEXT ==> LANGUAGE_STATIC

[Bruno H. <br...@cl...>]

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>