Re: Summary (Re: A system for localizing documentation strings)

[David Kastrup]

Jean-Christophe Helary <address@hidden> writes:

> On 27 juil. 07, at 20:59, Jason Rumney wrote:
>
>> Jean-Christophe Helary wrote:
>>> I'd say that it would be much more straightforward to use an elisp
>>> system to do that than to externalize the tasks to gettext.
>>
>> I wouldn't completely dismiss using gettext in Emacs. There are
>> several
>> sources of strings that should be translated in Emacs. Some of these
>> (documentation, menu names, tooltips) we can already reliably identify
>> and extract for translation without changing anything in the code,
>> so it
>> doesn't make sense to change our code to fit in with gettext 's way of
>> doing things for these.
>
> I am not dismissing gettext.
>
> I am saying that an elisp system to localize the elisp "part" of
> emacs will also be useful for the localization of other elisp
> systems. What needs to be done with gettext (the primitives parts)
> should be done with gettext.

Other elisp systems?  Reminds me of the story of a linguist
researching some island dialect, who had to wrap up his work before
the single person still speaking it was gone.  And one nagging doubt
was that he suspected his sole study subject to speak the language
incorrectly.

Are there any other systems speaking Elisp?

-- 
David Kastrup