* gerard robin -- Wednesday 21 November 2007: > AND, the recommendation to use "English" is less easy when we are > not "English speaking" , this will be an add on of work for the developer.
I didn't say that filenames/comments/function-names shall be in perfect English, nor in English better than you are able to speak. But they should *be* in English. I could start to write everything in German, with German comments, function names etc. Maybe some Austrian dialect. You'd quickly be lost! CVS isn't a dumping ground for secrets. Everything there should be open. And being open also means to be understandable by as big an audience as possible. I'm just not able to learn Greek, Chinese, Swahili, ... We all hate English, but it's the lowest common denominator. ;-) But again: these are *my* policies. It's not in the "official policies" document (because no such exists, and nobody would enforce it, and even if, some would ignore it). > To translate them, in order to have it acceptable with FG 0.9.11 will take > more time than to build fully it again (was the case with Catalina). My policies do also not mean that there couldn't be exceptions. If there's a plausible reason why some condition *can't* be met (with reasonable effort), then I can certainly live with that. But people making a new aircraft should know what they are expected to consider. m. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
