The specific terms are more understandable when they're in english. And its also good for those who dont know them very much

I'm against it, for a simple reason.

I'm german myself, BUT...as a programmer you have to understand english anyways. So language packs would just unnecessarily blow up everything.

My native langiage is Norwegian. As stated by other posters, jEdit is aimed at programmers, who generally speaks English. This is a very good point. Some claim that it will be good for new or novice programmers to have it in their native language. I would say, absolutely not! They should get used to using English when programming as well, otherwise they will stay novice. So if you want more novice users (which requre more support, in their language, and generally don't give much back), then go ahead!
Besides, since "all" programmers know at least basic English, they all understand this forum. Now what whould happen if you got sister forums in a couple of dozen other languages, and a blah-speaking (blah being a non-english language) user out there happened to ask some really useful questions that was actually answered, then all the 99% other people out there that would have needed the answer but don't understand blah, will not get the answer.

This is why I think programming tools should be kept in English.

I am native German speaking (from Austria). jEdit is clearly targeted for programmers, I suppose they all speak English.

I just started using jEdit, it is very complex. Everytime I thought something (used from other editors) is not possible, I found out it is possible nevertheless, when you install e.g. the right plug-in.

However, I needed a lot of searching in this forum. To make a language pack useful, it would also be necessary to translate the forum and of course also the complete documentation, which is, I think too much effort for a small group that would REALLY benefit.

It would be more useful to write a basic setup-guide. I am using jEdit for embedded C with a cross-compiler, I had to adapt language-files, commando-files, work-through the plug-ins, install ctags,... . While it is quite easy and very powerful when you once know it, it is very hard to get started. All I wanted to have is a compile-button

Regards,
Thomas

I would people rather have invest their time to get other features implemented or work on making some features work better instead of supporting all what is necessary for different languages. I am not a native English speaker myself, but I think that most users of Jedit will do fine with English dialogs.

Adding more features have both good and bad sides.
Advantage is having to do with spreading JEdit to non-native English speakers. More and more programs out there seems to be supporting langauge packs these days.

Disadvanage seems to be coming from bloating jedit a bit more and making jedit slower...(but oh hell, will anyone notice the difference in speed? say, from 0.05 to 0.1 loading time difference? i doubt it)

Of course, I know that jEdit is aimed to programmers who are mostly fluent in English but I want to promote and spread jEdit also for beginning programmers, web designers, newbies and regular intermediate users.

jEdit is too good to stay in minor use only by experienced programmers.

I think that a translation of jEdit isn't realy needed by many people.
But it is a good idea to translate the user docs in other languages,
and i could help.

Localization of jEdit and plugins would take many hours that would be better used on coding features and debugging. I used a French editor for early PHP work a couple of years ago and just learnt the commands without really needing to know French. The words on menus are not as important as the features working when selected!!! Help pages may be useful in major languages.

My first reaction would be to say that what is needed is a translation of the docs, especially for beginners. This is why I started to translate the jEdit User's guide on my own some time ago. However, I soon found out that I was actually translating jEdit since I had to translate menu entries when describing them. So far, I have translated parts of the Using jEdit section of the jEdit 4.1 User's Guide (including many menu entries and other interface elements). I'm ready to invest a lot of time and effort into a French version of jEdit but I need some help. I am a translator and only an amateur programmer, though I have some notions of java. I think people interested should start getting organized, but I do not know where to start. jEdit community is a big place.. Should I post a message in one the forums? which one (developper? general?) what about the wiki?
you can contact me at OlivierVasseurTrad@yahoo.com

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