WordPress 2.0, Unicode and Safari

I have found a solu­tion to prob­lem with Word­Press 2.0 doing con­vert­ing uni­code such as > into >. It is turn off the rich text editor and the auto­mat­ic­ally cor­rect­ing HTML options in the pro­file sec­tion and make sure you select apply. Unfor­tu­nately 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 turn­ing off does make a big dif­fer­ence, you can actu­ally write uni­code such as ’ and it stays ’ it is not con­ver­ted into ’ the first time you save the document.

So this week­end, if not earlier I will be mov­ing up to Word­Press 2.0 for this blog and it should be a short pain­less exper­i­ence (much like get­ting your eye­brow pierced).

Comments are closed.

Affiliates

Google
text advertising by
Powered by Reseller Zoom