If you can't see why that previous reply was defensive, I have no hope of explaining to you why it was. But, one more response, which I promise is not an attack, and then I'm done.ncollingridge wrote:I don't think I'm in the slightest bit being defensive. It's more that I don't agree with the reply you made to my post and I'm saying so. I don't know how you construe that as being defensive.
For some reason I don't think you're seeing the constructive side of my comments - nothing is perfect, even Nisus Writer, and I am trying to identify an aspect of the product which could be enhanced to improve its prospects in the marketplace.
I think it would be great if Nisus would make these small changes to take advantage of this.
Do you think that Nisus hasn't thought of Word compatibility? Or that you're the first person to broach the topic? Or, that maybe, there are some pretty good reasons that they haven't implemented these "better ways" that you speak of? And do you think if it were a small change, say simply substituting OpenOffice's conversion engine for AbiWord's, they wouldn't simply implement it? Do you have an insight into their code that no one else does? Do you think they're simply holding out on us for spite? Of course not.
I see the constructive side, just want to remind you that this has been discussed before, and there have been responses on this very forum about why things were done the way they were done that make pretty good sense (economic, code, or otherwise).
Offering you a workaround is not making excuses for a program. We tend to be helpful people around here, many of whom have been using this program for years and have encountered many of the problems new users face. I took a day when I first converted to NWE and resaved all of my files (over 500 of them) into RTF from Word, and I've never had to do it again since. It was a very small price to pay. From there on, I required my students to send me files in RTF only rather than .doc. Of course, not everyone has this much control over their senders, and I recognize that. That's why it is not for everyone.
We love the program and continue to use it for a reason, and often that reason is that its Word compatibility, especially in that it uses RTF as its native format (which can be read by Word natively), is good enough for us and its flaws in translation are a small price to pay in order to work with a program that is well thought out, responsive, and works with you instead of against you. This, once again, doesn't mean that it is for everyone. If you need your files (especially your Word files) to look the same across platforms, then really, Microsoft Word is the better choice. I don't think anyone at Nisus, or even its loyal users, would argue that.
Most of us who have stuck with the program all of these years have made the decision that the compatibility issue is not that big of a deal to us, and you have to make that decision as well. If it is too big of hurdle to jump, and the thought of using a Microsoft product makes you sick, I would suggest once again that you try Pages, because it does a very good job of translating Word files back and forth, as you would expect from a program backed by one of the top five richest computer companies. Or even NeoOffice, although I would rather cut my head off than use that program.
Good luck on finding some sort of solution,