Let’s say you’re a native English speaker. Let’s say you’re writing a library which is going to be used by Czech speakers, like our submitter Jan Krynický. You’ve been told to make sure the code is usuable by them, so you decided to use C#’s annotations to provide Czech documentation of various fields.

There’s just one problem: you don’t know Czech. You know enough to know that the Czech equivalent of “-ed”, as in “uploaded” is “-ováno”, so “uploadováno” seems perfectly reasonable to you. Czech documentation, done. It might not be the best choice, but they'll get the point.

There’s just one problem:

    public enum FeedProcessDirection  
    {
        [Description("Uploadováno")]  
        Downloaded = 1,

        [Description("Downloadováno")]  
        Uploaded = 2  
    }

The “offending person”, in Jan’s words, is no longer working with the organization, but Jan still thinks about ways in which to get revenge.

[Advertisement] Ensure your software is built only once and then deployed consistently across environments, by packaging your applications and components. Learn how today!