Quote:
Originally Posted by DawnFalcon
. Why should I be locked into TeX parsers rather than XML ones?
|
I was just using that as an example of the kind of editor I had in mind. You could certainly have one that used XML as its own underlying code. Clearly the reason for it to use TeX is so it can make use of TeX's typesetting algorithms, for which nothing of comparable quality exists for XML for the same price and availability. Prince XML comes close, but is not open source.
I don't know whether or not a good WYSIWY-whatever editor exists for web pages. I have no need of one. But nothing you've written has provided a single reason for why there couldn't be one. I even asked you for a reason, and you've yet to provide one. You've simply asserted over and over that it's a fact. Anyway, CSS is a fait accompli. You're going to have resign yourself to that fact.
Aside from IE, CSS noncompliance is really not that bad... and certainly it's fine for the needs of the casual user.