I have found a solution to problem with WordPress 2.0 doing converting unicode such as > into >. It is turn off the rich text editor and the automatically correcting HTML options in the profile section and make sure you select apply. Unfortunately with Safari 1.3 you get no visual clues as to whether the rich text editor is on or off. So check with another browser. But turning off does make a big difference, you can actually write unicode such as ’ and it stays ’ it is not converted into ’ the first time you save the document.
So this weekend, if not earlier I will be moving up to WordPress 2.0 for this blog and it should be a short painless experience (much like getting your eyebrow pierced).