Cart
[Home] [By Thread] [By Date] [Recent Entries]
Come on. If it's not XML, please don't call it XML. This has NOTHING to do with nitpicking. Just because something displays in browsers doesn't make it well-formed XML (or valid HTML, btw). > -----Original Message----- > From: Joshua Allen [mailto:joshuaa@m...] > Sent: Wednesday, July 26, 2000 12:04 PM > To: 'Julian Reschke'; 'Michael Champion'; xml-dev@l... > Cc: 'Ken Irving' > Subject: RE: XML in .NET - more than just SOAP? > > > OK, I have looked more closely and Word's output is not entirely > "well-formed". On the other hand, it displays nicely in a > wide range of browsers. Also, it took me only five minutes > to figure out what I need to do to the file to be able > to run XSL transforms against it using Saxon, Xalan, etc. > grep|tr|cut can do wonders.. > > So, while it is not perfect (and it will get better) > it seems to me to be quite useful. I call it XML, > although a purist could nitpick some of the flaws. > If you want to use XSL/XML to read and/or generate office > docs, you can do it quite easily. If you want to > build solutions that work today, you can. If you want > to wait, things will probably conform much better. > I suggest you read the documents I pointed out and > try some things. Try sending XML out a servlet as > application/x-msexcel and see what happens; it really > does work. Just try things! It is not so hard.. > > Ken, re: your question about the format -- it *is* a > self-extracting .EXE and unpacks to a .chm file. > I'm not sure how you could view it on non-windows > systems; I've never tried viewing .chm on anything else. > You could always install our VM (Win2k) on one of your > machines :-) If you know a way to look at HTML help > (.chm) on your system, I can send the .chm to you > as well.. And whoever is about to suggest that we make > those docs available as .htm -- great idea! > > Thanks, > -Joshua
|
