Description Greg Watson 2011-05-20 08:43:20 EDT

(Copied from bug 331485)

I have encountered another issue that corrupts the plugin.xml. It appears that
the escaping of certain special characters does not work properly. 

I don't have a test case, but you can try it out by creating an extension point
that has a string field. Try creating and extension and entering some text in
the field that contains special characters such as ", ', ;, etc. The initial
conversion seems to work ok, but if you subsequently edit the string (remove a
special character, add new ones, etc.) the field is eventually corrupted. Just
play around a bit and you should see it.

It seems particularly vulnerable when adding/inserting a semicolon in the
string if it already contains escaped characters. So if a string contains 'foo'
(including the single quotes), then adding a semicolon to the end seems to
corrupt it.