I see a few problems with what you are suggesting.
For one, the syntax and spacing are sometimes are core part of the language definition. You can't say, for example, "I don't want to see curly braces in C#" because the braces are an integral part of the language and perform an important function. You just can't use the language without them. Other languages, like Python, are very specific about spacing and indentation. In that case, it's also not a matter of personal preference.
Now, the question is, "why are those things required in a language?" And I think part of the answer is that parsing a language's grammar can be non-trivial. It gets more and more complex the more you relax the rules of the language's syntax. And even the more natural languages still have "marker" keywords that denote start or end of blocks if code and such.
Another consideration is being able to communicate with other developers. If you were able to define your own "view" onto the code, how would you talk about it with other people who are potentially looking at something completely different?
Machine-based translation is also not at the point where it'd be reliable. How would you decide which parts to translate? Just the keywords? Keywords and literal strings? Would you input new code in your local language and expect it to be accurately translated into a common base language?
There are some IDE plugins (such as ReSharper for Visual Studio) that will help enforce a coding style, but that style has to be maintained across the entire dev team that works on the code and, like you say, that style often has to be discussed. I don't see that as a bad thing. A team that can't agree on something as simple as a coding style is likely having bigger issues than that.