>>PS. I'm aiming for 100% RTF export compatibility with Word. I need it for >>my job. > >As do I. And from what I read on the lists, we are not alone. The problem, >as Hub has pointed out, is that MS doesn't follow its own RTF specs in terms >of default RTF font size, so a philosophical decision has to be made. Do we >make Abi follow the RTF specs or do we make it follow what Word actually >does? I vote for the latter.
Since Abi pretends to save as .doc when it in fact saves in RTF format, perhaps the best ways to solve this are: 1.) Actually export in MS Word format, so as not to confuse applications that rely entirely on extention or 2.) When saving as a .doc file, make the RTF comply with what Word does, and when saving as a .rtf file, comply with RTF standards or 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. I would like to have perfect compatability with Word, just like when I design a web page I want perfect compatability with Internet Explorer. But not at the loss of complying with the standards that browsers (or word processors) should be following anyway. ____________________________________________________________ woof! woof! I'm @dog.com Get your free @dog e-mail at http://www.dog.com ----------------------------------------------- To unsubscribe from this list, send a message to [EMAIL PROTECTED] with the word unsubscribe in the message body.
