emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Jean-Christophe Helary
Subject: Re: Summary (Re: A system for localizing documentation strings)
Date: Sat, 28 Jul 2007 11:57:46 +0900


On 28 juil. 07, at 01:11, Andreas Schwab wrote:

Jean-Christophe Helary <address@hidden> writes:

On 28 juil. 07, at 00:07, Jan Djärv wrote:

Jean-Christophe Helary skrev:
On 27 juil. 07, at 17:03, Jan Djärv wrote:
gettext has nothing to do with emacs. emacs code, as elisp, is data and
must be considered as such by specific elisp functions  created for
localization.

Why?  AFAIK, gettext works with other interpreted languages also.

This is besides the point.

gettext offer tools to extract the strings, deliver PO(T) files, merge the
strings, compile the PO

This is the development part.

This could be easily handled with elisp code for all the elisp parts of emacs which would also contribute to provide a simple way to localize non emacs related elisp files. I.e. that could be an emacs extension for localizing elisp code.

The emacs core parts in C should of course be handled in gettext.


Jean-Christophe Helary





reply via email to

[Prev in Thread] Current Thread [Next in Thread]