I think the capability to localize jEdit should be present, but actually localizing it is not necessary for the core jEdit team. Use ResourceBundles, it is usually easy to provide the ability to localize an application. It also make it easy to update strings in one place without having to read through Java.

Brant Langer Gurganus
Freshman, Computer Science
Rose-Hulman Institute of Technology

Localization is not needed for such a tool like jEdit. I do preffer localised interfaces in web-applications, e.g. phpMyAdmin, but don't actually see the need to have a localised jEdit. Just think about all the plugins, they - what - will also need to have a localised interface? I don't know.. Maybe I've just never seen a nice application translation to my native language, everything's more usable in English.
And you know why that's bad? It's just because jEdit developement team will waste the time on not-so-usable feature. I think there's much work to do in other areas..

Hi,

CjK wrote exactly what I am thinking about this. I'm german too but it's no problem for me to handle a software with an english interface.

Lars

I voted "indifferent" but close to "that would be bad". Since JEdit is a programmer's editor (or maybe it isn't?) one would expect the audience to be fluent in english. I for myself, even if a particular piece of software is also available in my native language (german), I rather go for the english interface, since I'm used to it. I know the commands and often find myself being puzzled when using localized applications.

Well, perhaps just my opinion. But the energy we could save by skipping language packs could be put into other areas of interest.

best,
CjK

I think it is a nice feature to incorporate. For me, I would not probably use laguage packs since English is my primary language. I think that it would help developer's productivity to allow them to use the program in their native language.

No, that'd be bad