All the IDE is in English, so why mix environments ?
I think it will only be confusing, all the keyboard shortcuts will change,
and all the terms on the screen will change too, causing a "Babylon tower" situation when talking to other developers.
2. No, because 1 == NO
Noooooooo
Why screw-up a good thing?
Yes! Yes! Yes!
I personally would like every software to be in hebrew, except from windows (until they fix the bad graphical performance of explorer in the hebrew version, and many other things).
I think it can bring NUnit to young developers who don't understand the english version.
I'll be glad to help localize it.
HELL NO.
When you do your programming, you usually do so in English one way or another (be it because the syntax is close to English, a la Pascal, or because the class libraries are designed that way, as in .NET). Mixing native languages into the code is horrendous enough in itself, because it makes the code unreadable, difficult to maintain and obfuscated. Mixing native languages with your development tools an abomination - it makes everything that less consistent, and moreover it makes it extremely difficult to get support and assistance from non-native peers. Just think how hard it is to support your friends who use Hebrew-localized versions of Windows; now imagine how difficult it would be if the NUnit GUI were in Hebrew ("bdikat hayehida nechshela; nizreka harigat NullReferenceException...").
These arguments are five times more powerful when you mix languages that have different directionality contexts - bidi is hell in itself, but bidi in your development environment would probably be the single biggest nuisance ever.
My 2c.
1. No. I don't use much software in Hebrew, and usually I just try to figure out ways to remove the Hebrew features. However, many users and developers are not like me in that sense. Most of them, safe to say, probably don't read your blog, may want to use such program but can't speak up on it's behalf.
2. Yes. Could be fun. :)
Dito as the other guys, moving between languages is hard enough transition that it jar me from the Zone.
No... It's almost by definition that there's no point in an NLS verison of a unit testing framework. The linua franka of the programming world is Engish. The programming languages and environments are in English. I18N is a story that needs to be written to be implemented - the seminal language is English.
Do you *really* want to see NUnit menus and messages in Hebrew? What's the *Business Value*?
If I was to suggest that you invest your (our) time in distrubuting NUnit versus dealing with NLS - What would the world (including עברית speakers) prefer?
It sounds like this is not a big priority for most people here - although as someone pointed out, those who might like it may not be reading this list.
The point about support is a good one. It doesn't make sense to have a localized version unless there's a group of users willing to host a support forum in the language... I'll have to think about that.
Anyway, it's a fairly low priority for the NUnit team, but since localization is a different kind of activity from adding features, we can still move ahead with it wherever somebody wants to do the work. Right now, you can localize the gui readily, but we haven't dealt with i18n of the internal message generation - "Expected... but was...." for example. We probably won't get to that for month or two.
In spite of the potential negatives, those who may be interested can get a copy of the current Localization Kit by sending me an email.