From: Owen D. <ow...@ba...> - 2004-08-30 22:06:58
|
I wrote a few days ago about an xml problem, attached. I just upgraded to 4.2 final to see if the problem went away. It didn't. Is anyone else on the list having difficulty with the xml plugin and jtidy getting errors? I appear to get this with all xml files, not just build.xml ant files. I think the problem is that the xml plugin uses the mode files and functions fine, but jtidy needs a dtd. Is that right? It looks like the xml-indent plugin works fine, by the way, it apparently doesn't need any semantic info, just xml systax. Here's a new image where a simple build.xml file not only gets errors but also gets a beanshell dump: http://backspaces.net/files/jEdit003.jpg Owen > I"m sure I"m doing a dumb thing, but ... I"ve got the xml plugin which > works great for xhtml editing. I"ve just loaded a downloaded ant > build.xml file, however, and there are lots of errors noted. > > The error list shows <project>, <target>, ... and the other ant xml > keywords as being not recognized. But the xml insert side panel shows > these as being just fine. I believe this means the ant dtd/catalog is > known by the plugin. Here"s a picture: > http://backspaces.net/files/jEdit001.jpg > > I"ve found this in other contexts as well. When I start looking at > jedit mode files or the catalog file, for example, I get errors of a > similar nature: > http://backspaces.net/files/jEdit002.jpg > > Sounds like the xml editor does fine by using the mode files but jtidy > needs a dtd? > > So what dumb thing am I doing wrong?! > > Thanks... > > Owen |
From: Slava P. <sl...@je...> - 2004-08-30 22:29:39
|
There are two buggy plugins here -- XML and JTidy. A new release of XML is long overdue, and I'll get to it soon. Owen Densmore wrote: > I wrote a few days ago about an xml problem, attached. > > I just upgraded to 4.2 final to see if the problem went away. It didn't. > > Is anyone else on the list having difficulty with the xml plugin and > jtidy getting errors? I appear to get this with all xml files, not just > build.xml ant files. > > I think the problem is that the xml plugin uses the mode files and > functions fine, but jtidy needs a dtd. Is that right? > > It looks like the xml-indent plugin works fine, by the way, it > apparently doesn't need any semantic info, just xml systax. > > Here's a new image where a simple build.xml file not only gets errors > but also gets a beanshell dump: > http://backspaces.net/files/jEdit003.jpg > > Owen > >> I"m sure I"m doing a dumb thing, but ... I"ve got the xml plugin which >> works great for xhtml editing. I"ve just loaded a downloaded ant >> build.xml file, however, and there are lots of errors noted. >> >> The error list shows <project>, <target>, ... and the other ant xml >> keywords as being not recognized. But the xml insert side panel shows >> these as being just fine. I believe this means the ant dtd/catalog is >> known by the plugin. Here"s a picture: >> http://backspaces.net/files/jEdit001.jpg >> >> I"ve found this in other contexts as well. When I start looking at >> jedit mode files or the catalog file, for example, I get errors of a >> similar nature: >> http://backspaces.net/files/jEdit002.jpg >> >> Sounds like the xml editor does fine by using the mode files but jtidy >> needs a dtd? >> >> So what dumb thing am I doing wrong?! >> >> Thanks... >> >> Owen > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click |