Page 1 of 1
Bug in rtf
Posted: 2004-10-13 08:40:56
by nspy
Do this:
1. write a Nisus classic document with some formatting -- bold, italic, centring, whatever.
2. save
3. drag and drop on NWX
4. It opens and all looks fine
5. Save as an rtf file
6. open in Word --- all character formatting is lost, though para formatting such as centre and left is retained.
If at stage 3, however, the document is a long (in my case merged) document this step may take half an hour or more. Last time I tried this with a 225K word document from classic, I had to leave it overnight to open, then scrolling took minutes. This is even worse than Word.
Rick
Posted: 2004-10-13 08:45:01
by nspy
Oh, and I should add to this, that any large document (again mine are all merged from chapters) when created in classic and then pasted into Word will have the centering miscalculated and some loss of font format info. I suspect this is a NW classic issue, but do not know.
Posted: 2005-08-30 09:16:32
by nspy
This problem still exists in 2.5b6 NWE cannot write rtf that can be read by Word (at least not in a large file).
Rick
Posted: 2005-08-30 11:23:23
by martin
Express should be saving RTF files that Word can read properly. Please, if you are still having issues using beta 6 then email me (
sneakpeek@nisus.com) the original Classic document so I can have a look. It would also be helpful to know what version of Word you are testing against. Thanks.
Posted: 2005-09-02 09:44:00
by nspy
martin wrote:Express should be saving RTF files that Word can read properly. Please, if you are still having issues using beta 6 then email me (
sneakpeek@nisus.com) the original Classic document so I can have a look. It would also be helpful to know what version of Word you are testing against. Thanks.
I posted a bug report and Mark asked for the files, so I sent him the whole folder--original chapters, merged version, version opened by NWE and saved as rtf. Try reading the latter with Word Mac 2004. Most formatting gone.
Rick
Posted: 2005-09-02 21:40:36
by martin
The fix for this bug should be in final candidate 2. Let me know if it gives you any troubles in that version.
Posted: 2005-09-07 05:43:06
by nspy
martin wrote:The fix for this bug should be in final candidate 2. Let me know if it gives you any troubles in that version.
As reported directly to you (but placed here for the record) this particular bug seems fixed in RC2. This will help me immensely. Each version is also faster than the one before, though speed is still nowhere near NWC.
Rick