[Top][All Lists]

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

Re: Emacs localization (Re: Why emacs have not native language menu)

From: Jean-Christophe Helary
Subject: Re: Emacs localization (Re: Why emacs have not native language menu)
Date: Tue, 24 Jul 2007 20:19:44 +0900

On 24 juil. 07, at 16:48, Jason Rumney wrote:

On 24 Jul, 02:00, Jean-Christophe Helary <address@hidden>
On 24 juil. 07, at 09:36, Nick Roberts wrote:

Yes. I could see that myself. Indeed, all the strings are in the
code. All the functions are documented in English in their code and
to get a proper localization of that, or at least of a basic core
features (like functions that available from the UI for a start)
would require to remove all strings and put them in locale separated
files that emacs would load based on the environment. Is that correct ?

Locale specific files is the conventional way of dealing with
localization, but Emacs is extensible, which means that  we need to
come up with a design that is also extensible. Very few applications
have dynamic menus the way that Emacs does, mostly they are static and
defined in resource files where such conventional localization is

What is the technical difference with the extensibility of emacs and version upgrades or plugins in other apps ?

I don't see any. And the common issue is that localizers have to keep up with the dynamic in both cases.

Jean-Christophe Helary

reply via email to

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