Summary: | Kwrite doesn't show mallformed xml | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Kristjan Ugrin <kristjan.ugrin> |
Component: | kwrite | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | andresbajotierra, ivo |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | I get this (Kwrite OK) |
Description
Kristjan Ugrin
2008-07-21 14:39:58 UTC
I can confirm this too, on kwrite/kde 4.1 . On kde 4.0 it works correctly. Using KDE 4.1.00 (KDE 4.1.0) (KDEmod) in ArchLinux i686: I can open that file with KWrite. Is the XML file OK now ?. Even if I modify it (to make it invalid) and save it to another XML file, this new file will be opened OK in kwrite (and it's displayed). Should I notice another thing ? You don't get this? http://files.myopera.com/kriko/files/kwrite_xml_broken.png Created attachment 26549 [details] I get this (Kwrite OK) Opening http://files.myopera.com/kriko/files/path.xml with KWrite in KDE4.1 final No, you are doing it wrong! :) unfortunately if you wget that page you'll get a html - you need either to visit it and then right-click on download. You might try directly saving this link: http://files.myopera.com/kriko/files/path.xml?1217598498 Ups, sorry, I didn't notice the Opera warning before getting the original file :$ Using KDE 4.1.00 (KDE 4.1.0) (KDEmod) in ArchLinux i686: I can confirm this bug With this XML: ------------ <?xml version="1.0" encoding="UTF-8"?><graphml xmlns="http://graphml.graphdrawing.org/xmlns"><graph edgedefault="undirected"><!-- data schema --><key id="name" for="node" attr.name="name" attr.type="string"/><key id="relation" for="edge" attr.name="relation" attr.type="string"/><!-- nodes --> ------------- I've noticed that I can paste this XML in another KWrite, save it as a xml file and see its highlighting OK. However, reopening this file will result in this bug. Same with Kate. I've noticed another important thing: If there's a line break ("\n") in the file, it can be loaded normally. So I now suppose that this bug is a duplicate of bug 167767 (as it matches its definition), and it isn't related to malformed xml. Excellent eye! Fixed in /trunk, but no idea, which change did make that :( Yes, it is actually the same problem. *** This bug has been marked as a duplicate of 167767 *** |