I'm not sure what to do with the following:We take data from an external tool within our own tool. This data is written in Dutch. We are writing our Java code in English. Should we then translate this Dutch to English or keep it Dutch? For example, we have 2 departments: Bouw (Construction in English) & Onderhoud (Maintenance in English).Would it then be logical to create:public enum Department { BOUW, ONDERHOUD }or:public enum Department { CONSTRUCTION, MAINTENANCE }or even:public enum Afdeling { BOUW, ONDERHOUD }(afdeling is Department in Dutch)
Translating external data to the language you're programming in
naming;translate
In this scenario, I would leave the enum values in Dutch:public enum Department { BOUW, ONDERHOUD }Because, the program logic using these constants will be matching against data with the same value. In other words, the input might be bouw and the code might look like:if (Department.BOUW == input.toUpper())I'd find it much easier to debug when the words match (even if I don't know what the words mean) than having to translate.Nevertheless, you can just comment the code if it helps others understand the context of the data:public enum Department {     BOUW, /* build */    ONDERHOUD /* maintenance */}