I was going to respond to Halirutan's thoughtful answer, but I think this deserves more than a comment.
I am among the most ardent supporters of re-formatting code for readability. First, the code should not require the user to side scroll, it interrupts the flow and often it is just one very, very long line. Second, the indentation should be set up in such a way to easily understand where the beginnings and endings of functions and lists are and the structure is clarified. This helps in making the code more comprehensible, quickly. Third, remove all Mathematica mark-up if possible. For the Greek letters, I will often replace the mark-up with the unicode version which is still understandable by Mathematica, and now human readable.
The last point requires caution in application. On at least one occasion, my fixes to the mark-up have fixed the OPs problem, so on more complex transformations, you may have to re-run the code to ensure the problem remains. Also, the more extensive mark-up, e.g.
\!\(
\*UnderoverscriptBox[\(\[Sum]\), \(i = 1\), \(5\)]
\*FractionBox[\(1\),
SqrtBox[\(i\)]]\)
can actually conflict with the escape sequences in the displayed form. So, when converting the above to a usable form
Sum[1/Sqrt[i], {i, 1, 5}]
you should copy the text from the edit window, not the result window. Lastly, when a user posts such a mess, I leave a note asking them to first convert their input to InputForm
using either the context menu (right click) or the Cell menu before posting next time.