nisus.com

My colleague in UK unfortunately must use Windows. He has been sending DOCs to me, which I have opened in the past. Currently, they don't open. Now he is saving in RTF, and they open.
If I open his RTF saved file, then save it in WORD, then it will open in NW PRO.

Is there a translator missing for WORD DOCs in the new PRO update?

I use a new iMAC.

Thanks

cas99 wrote:My colleague in UK unfortunately must use Windows. He has been sending DOCs to me, which I have opened in the past. Currently, they don't open. Now he is saving in RTF, and they open.
If I open his RTF saved file, then save it in WORD, then it will open in NW PRO.

Is there a translator missing for WORD DOCs in the new PRO update?

I use a new iMAC.

Thanks

Which version of OS-X and which version of NWP are you using?

Also, how do you go about saving the Word document? The Save As feature only generates a regular RTF file with a .doc file extension. If you want to create a real Word binary file, you need to use the Export feature.

I have the same problem... Since I upgrade to Snow Leopard (and to the 1.3.1 beta 1).... The only solution is to open the document with Notpad (or word), export to RTF and then open with Nisus...

The problem seems fixed with de Beta 3

Yes, if you're on Snow Leopard (10.6) please make sure you're using the latest beta (#3), otherwise this could be a problem.

had the same problem with WordPerfect files but the beta fixed it

Any chance of recompiling the importers as universal binaries or Intel-specific?

Derick wrote:Any chance of recompiling the importers as universal binaries or Intel-specific?

The importer is over 150MB, just to support PPC. That would make universal importers more than 300MB, which is a lot of bloat. Perhaps one day everyone will be Intel-only (Apple moved that way with Snow Leopard). Or we could offer separate downloads, but that tends to confuse users.

Why confuse, Martin? I always download Intel-only versions whenever the application has split versions, just like I used to download PPC-only previously.

Greetings, Henry.

I have to agree with Henry. Wholeheartedly. I'd rather just have the Intel package and avoid installing Rosetta.

Thanks
Lou

I'd vote with offering separate downloads. I still have an iMac G3 in my office and an iBook G4, but most of my work is on my year-old iMac and my first-generation MacBook. It wouldn't be any problem, when there's an update, to download separate Intel and PPC versions. I already have to do that with some other software.

I want to echo the sentiment. I use Intel Macs only, and I would love to eliminate redundant PowerPC files, if only to save hard disk space. Many software developers offer two separate versions of their applications, and if you Nisus guys label the download files appropriately, there should be no confusion for your users.

+1 for separate downloads.

mrennie wrote:I want to echo the sentiment. I use Intel Macs only, and I would love to eliminate redundant PowerPC files, if only to save hard disk space. Many software developers offer two separate versions of their applications, and if you Nisus guys label the download files appropriately, there should be no confusion for your users.

You can always use one of the stripper utils that will remove the PPC code from any app. The space savings are not that great however unless you strip every app you own.

Better still drop PPC support altogether for NWP 2.0. If you're still using PPC Macs then you can still use NWP 1.x and Mac OS 10.5 or 10.4, but the future is Intel only (and 64-bit Intel at that). It's time to stop being held back by obsolete hardware and software, I can't see the next version of iWork still supporting PPC (or pre-10.5 versions of Mac OS X), and it might even be 64-bit too.

Actually at this point you can't strip the PPC code from NWP b/c the importers included with NWP are only in PPC, even in the beta for Snow Leopard.