Dwight sez:
>>If the standard for accepting new features in Frame is that they don't break Word, we may as well just pack up and go home. <<
and Horace adds:
>>It's one thing to say do such-and-such like Word (I sure did). But, in so-saying, might we assume that FM would actually make that feature work before including it? <<
A couple points: I don't assume Word is the way it is because Microsoft hires a bunch of stoooopid programmers, nor do I assume Adobe's programmers will necessarily be significantly smarter. Rather (and full disclosure here: I'm not a programmer myself), I suspect that certain features that are memory intensive (e.g., multiple undo) or real-time processor intensive (e.g., on-the-fly spellchecking) *inherently* increase the risk of flakiness, regardless of how slickly they're programmed.
As for revision marking... well, the interface gives users lots of choices about *how* they make changes, and they use them all. Given the need to change one word within a sentence, one user will highlight and retype the entire sentence; another will highlight and retype the one word; another will backspace over the word and retype it; yet another will highlight, delete, and type.... While all these actions produce the same result, they all look like different actions to the machine... so it's not surprising they might get marked differently (and don't even get me started about change tracking in tables!). Programming in the smarts to recognize and reconcile these differences would use up a lot of the resources available to the application. So I think there's an *inherent* issue -- not just Microsoftian incompetence -- with that sort of revision tracking that makes it unsuitable as a replacement for redlining tools.
I've been a Word user since the very first (Mac) version was released, and I still use it as part of my current workflow. I think it's a FINE program... for what it does. It's just that FrameMaker does *different* things for me, and I'm reluctant to trade (or even risk trading) any of those things to get some of the niceties of Word.
Sorry if all this seems OT, but the on-topic point is this: All of *my* "wish-list" items are just that... wishes. FrameMaker works very well for me as-is, and I wouldn't willingly trade any of its current functionality and robustness for any of the things I've mentioned.
Of course, I recognize that others use the product differently, and YM most definitely MV! ;^)
-Bill