Problems in trying to implement coding standards

Coding standards sound like the best thing possible; they help in getting uniformity, they enable easy transition, they promote easy code review and preparation of documents such as SDK’s, and so on. So why would you not be able to get coding standards implemented across development teams ?
Mostly it is due to individuality. Most developers are used to writing code as they are most comfortable, and having to modify this approach to write to a common standard is hard.
A lot of developers start work in smaller places where there is less pressure to follow standards, and only then move to places that encourage standards. But by the time they are in a position to follow standards, they have already got a set style.
Trying to enforce a coding standard without explaining the reasons is bound to cause a lot of resentment and lead to a feeling that a ‘process’ decision has been taken by a manager. In fact, given the number of reasons in favor of having coding standards, it is far more effective to get the senior coders bought in first, and they will be easily able to drive adoption.
Trying to take an external style and enforcing it for the entire team may fail. It is better to let the team develop a standard that works for the entire team and use that standard.
In many cases, such as developers writing in Perl , there is a feeling that trying to enforce a standard crimps their style.