On Monday 25 March 2002 09:56 am, you wrote: > We comply entirely with the RTF standards except for internal use only > (cut & pasting of lists, mostly) that the outside world never sees. > You're filing a bug with the wrong people here. We aren't going to give > people an option to save as non-complaint RTF.
Agreed. > > 3.) Stop pretending to have Word export capability and simply have the > > option to select whether to comply with Word or with the actual RTF > > specs, and make it clear in the documentation that Word can read RTF > > files, and they are often smaller than a "real" Word document. > > We pretend to have word export because too many people complained that > we didn't and couldn't get it through their skulls that RTF was > compatible with MSWord, no matter how loudly we shouted and how many > places we documented it. So we fake it for now, and in my opinion, do a > terribly good job at it. I think you do a good job. For general user, or lay people (no offense whatsoever), RTF is unfamiliar. I myself have to explain to a lot of my colleague that RTF can be opened in MS Word. And I got tired of it. So, this hack in abiword is a lifesafer. Now, even when I encourage and install Abiword for other people, and they ask if Abiword can save as M$ Word, I only need to answer with one word, "sure". No need to sing that long boring explanation about RTF and M$ Word. > Stick to the standards. Make others comply. The world will be a better > place. Yeah ... yeah. Agreed. As web developer, for dynamic sites for uses in our internal network, I only designs it to comply to W3C standard. I don't give a damn if the sites look sucks in MSIE because MSIE does not comply to standard. I tell them to switch to Mozilla. We NEED standards!!! Rdb ----------------------------------------------- To unsubscribe from this list, send a message to [EMAIL PROTECTED] with the word unsubscribe in the message body.
