Previous Next Tracker index See it online !

(62/211) 3441 - Plugin Set xml file - encoding failure

I just saved a plugin set from jEdit 4.3.2. When I try to open it with plugin manager of jEdit 4.3.2, reading fails because of malformed UTF-8 sequence (German Umlaut).

So, it seems that the file is written in a different encoding than it is read later....

Submitted	rschwenn - 2010-05-15 14:07:13	Assigned	ezust
Priority	5	Labels
Status	pending	Group	None
Resolution	fixed

Comments

2011-12-04 04:34:03 ezust	Is this a duplicate of 2953810 ?
2011-12-04 21:12:36 rschwenn	No, this here is an encoding problem, and the other one covers an issue about interoperability between different localized jEdit installations: When I create a plugin set file (having translated some plugin names) then it won't work for You.
2012-12-27 18:00:54 rschwenn	Just tested with jEdit 5.0.0 (Java 7, WinXP SP3): The PluginSet is written in ISO-8859-x or similar encoding, but seems to be read as UTF-8 which fails at line 54 of attached PluginSet50a.xml.
2012-12-27 21:16:35 kerik-sf	Per http://www.w3.org/TR/REC-xml/#NT-EncodingDecl, the XML file is parsed as UTF-8 if there is no declared encoding. ManagePanel.SaveButton.saveState should specify utf-8 when creating the OutputStreamWriter, line 840 instead of relying on the platform default.
2012-12-27 22:01:21 ezust	suggested patch? managepanel.diff (480B)
2012-12-27 22:01:54 ezust	ok here is a suggested patch. I don't know how to test it though.
2012-12-27 22:02:16 ezust	there is no pluginset.xml example attached to this ticket
2012-12-27 22:21:19 rschwenn	pluginset.xml example and activity logs PluginSet_EncodingBug.zip (6.4Kio)
2012-12-27 22:25:16 rschwenn	Oh sorry, somehow the upload has failed and I haven't noticed it. Now the sample is attached.
2012-12-28 02:20:44 ezust	Committed 22623. Let me know if this fixes your issue.
2012-12-28 02:22:43 ezust	- assigned_to: nobody --> ezust - status: open --> pending-fixed