Closed Gitoffthelawn closed 3 years ago
Hi,
The error you encountered is sent by the SimpleXml formater engine whose I'm not the developer. You can avoid this error by using another formating engine : go in XMLTools Options and select "QuickXml" or "StringXml" as formating engine.
Now, this will not magically make your xml valid and the syntax errors present in your
Thanks. I will give your recommendation a try. Since SimpleXml generates an error on syntactically invalid XML, I wonder if either QuickXml or StringXml would be a better default for your plug-in. What's your thought on that?
BTW, if you can briefly summarize the key differences between the 3 engines, I'm interested in reading what you write.
The options dialog already gives some infos about these 3 engines. Briefly:
<p>some <b>bold</b> <i>italic</i> text</p>
, it might change the xml structure; therefore QuickXml will not format xml when it causes a change in structure)Thanks! What do you mean by "change the structure"? I imagine you agree that changing the actual XML would not be good! :)
I'm fixing a large commercial website, and as part of the debugging process, I'm validating some of the server responses. I've isolated an error where their servers are responding with erroneous data.
I was trying to look at some of that data in Notepad++ with your helpful extension. Unfortunately, when using the extension to format the data, the extension causes Notepad++ to issue this error:
So here I am, getting in touched with you as requested! :)
Here is a tiny fragment of data that will always cause this error to appear when using both the
Pretty print
andLinearize
functions in XMLTools:Of course, this data has serious issues (which is why their website has issues), but I don't think XMLTools should be abending when it encounters erroneous code.