[
Lists Home |
Date Index |
Thread Index
]
So far, the only reliable witness outside of MS on
this list is Tim Bray.
I don't see why they couldn't do it. There were
SGML editors that handled worse and still managed
to be WYSIWYG. The tedious part was setting
them up, but otherwise, it could be done. XML
is simpler than SGML.
The painful thing about WYSIWYG was it usually
presumed a fixed set of types internally, so
it was more like an HTML editor, just better at
formatting.
But the thrust of the XML seems to be opening
Word, Excel, etc. up to easier integration. That can
mean any number of things with regard to how
each Office app uses XML. Remember, Office
is more than Word. If it all works, it will
be pretty darned neat, and a bit of risk for
MS since Office is traditionally a cash cow
but a pain to integrate with anything other
than MS products. If what I read is true,
then this enables the Office apps to get
information updates from other sources, so
as one article said, like a web browser without
the web browser.
Maybe you are being too cynical, but hey, this
is XML-Dev. We live to cynic. :-)
len
From: Justin Lipton [mailto:justin@ns.xn.com.au]
Does anyone know or have ideas about what XML enabled Office 11 actually
means?
I can't imagine Office having a concept of validity and behaving like a
true XML editor.
It's easier to envisage being allowed to define tags (like styles) and
markup text such that the output document can be appropriately tagged. I
just can't see it properly handling IDs, IDREFS, ENTITIES, encoding etc.
etc.
There is a hint of this in the following article
http://www.eweek.com/article2/0,3959,561973,00.asp
Am I being too cynical?
|
