Most programming code, I imagine is designed in British. But I am curious how individuals are handling the problem of naming herein. Lots of programming is performed within some bussiness domain, usually with well-established terms for several methods, products.

I am from Denmark for example, then one Sometimes a great deal with includes a term known as "indblikskode", which kind of means "insight code". So, will i make use of the line "string indblikskode = ..." within the C# code for many web service associated with this? Or will i use a translation, for example "insightcode"? The bussiness I am in is not even consistent in the language, for example while using term "organisatorisk enhed" (organizatorical unit), and frequently while using abbreviation "OU", that is clearly abbreviated in the British.

How can others handle this naming problem, and keep consistent, and sane (in from simple variable names inside your code, to database tables, to server names)?

Replicates:

I'm able to only speak personally, however i always translate terms into British when naming classes and variables, and it is our unwritten best coding practices to do this too. Who knows when you will need to hands off development to cheaper work abroad or even the expert expat consultant around.

The issue with non-British naming of classes and processes is, that you simply almost always likely to finish track of macaronic pidgin. Key phrases have been in British, naming conventions (like for instance getters/setters) will also be British, same for standard names for design designs.

You are likely to finish track of things like:

OrganisatoriskEnhedFactory::getInstance()->getIndblikskode()

Getting labored in Europe (German side ie Zurich) and resided in Germany for some time I will tell you that I have yet to determine an atmosphere in which the code is not in British. Sure the applying may be in German (however, many professional environemtns are British-speaking anyway) however the code (I have seen) is virtually all British.

It's difficult to create code in other languages. To begin with, the APIs are (nearly) all in British. Java uses JavaBeans naming for instance so you've to make use of set and obtain anyway and "getGeburtstag" just does not have quite exactly the same ring into it as "getDateOfBirth".

Other nations can vary with this continues to be my experience in the Germanic nations.

We are usually using established British terms (our business domain usually has British terms), but when I can not determine any appropriate term, I possibly could too use Finnish. Heck, even our comments in code have been in mixed languages...

Obviously the sensible approach is dependent largely on if the source code is ever going to be utilized outdoors your building. In a tiny shop it isn't this type of large deal.

I am your company in Austria (so we are speaking German) and that we are programming in British (variable names, domain objects, GUIs). Causes it to be a little more cumbersome, because are looking for the British translations and you've got to translate the GUI before delivering this program. I am not necessarily confident that all of the names are actually correct.

In comparison within the former company I had been employed by designed strictly in German. It was pretty nice (altough German words are usually more than British words). After a little years the organization desired to make use of the same program in the united states, so British-speaking programers needed to make use of the same codebase. following this everything got pretty sporadic- variables, database fields.. both in languages (the British speaking team people did not talk German).

My experience is it is simpler to deal with internationalization in early beginning (you have to get it done whenever you write this program in British) of the application, since it is no large fun localizing a 10000 LOC application. The benefit of writing in another language is you see instantly what's localized and what's not - altough it's work you need to consume account for your.

Towards the untranslatable words: we had not expierienced that yet - altough it had been some work locating the British phrase for "intra-community shipping" (that's an EU factor). But when that will happen I am confident we'd make use of the German word.