You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Converting Appleworks 6.2.3 documents created on an iMac OS 9.0.4. to Pages on my new MacBook Pro OS 10.8.3.

I have many Appleworks 6.2.3 documents created on an iMac OS 9.0.4. I want to convert these files to Pages on my new MacBook Pro OS 10.8.3. so I can share the documents with newer computers that use Microsoft Word. How do I do this? Pages can't read my Appleworks documents. When I try to open the older document with Pages, the window says, "The document “Name” couldn’t be opened." These older documents show up on my new computer as Unix Executable Files. Any help would be appreciated.

MacBook Pro with Retina display, OS X Mountain Lion (10.8.3)

Posted on Apr 2, 2013 7:55 AM

Reply
46 replies

Aug 14, 2013 11:47 AM in response to fruhulda

Because for many it doesn't work. For the reasons I gave. You get a message saying that Pages will not support the version of AppleWorks that people are trying to convert and this is the only way it works.


If you can open in Pages then you are one of the fortunate ones. Many, like myself, cannot open it, so this is the next best way of doing it.

Apr 20, 2014 10:57 PM in response to fruhulda

I have about 2500 Apple Works docs, dating back to 1995 which I need to convert either into Pages or text .txt / .rtf or whatever, but I need a script to do it. Most of the AW docs are textdocs, some are spreadsheets (they can also become text .txt docs) This way I don’t have to convert them next time when Pages will be succeeded by a newer app.


So who knows about an


AW - to -text- script or an

AW - to -Pages- script

?



with best regards,

Omar K N

Stockholm, Sweden

Apr 20, 2014 11:12 PM in response to oktan

Have you tested LibreOffice?


If LibreOffice works, then there is no need to convert anything as you can just access them as needed.


Also if you are concerned with future compatibility, as you should be, you should convert to .txt or otd, preferably the later.


No way should you convert to .pages which doesn't even have a standard format in the very restricted current versions.


.pages certainly is neither accessable nor accessible by anything else than the current Pages version, whatever and whenever that is. Pages 5.0 won't open even Pages 5.01 or Pages 5.2, let alone anything earlier than Pages '09 which it converts badly, as it does .doc/x


Peter

Apr 20, 2014 11:41 PM in response to oktan

> Have you tested LibreOffice?


Now I did, and well: Phantastico!


If LibreOffice does the job why can't Apple provide a better backward service??


Thank you,


This saved me some headache!



with best regards,

Omar K N

Stockholm, Sweden



PS: Iwanted to use the ”This solved my question -” thing but I can't see it!

Apr 21, 2014 8:17 AM in response to PeterBreis0807

The LibreOffice solution works on simple documents, but fails on documents which exploit the nice inherited styles that made AppleWorks thousands of times better than Pages. It does import the text just fine, it does not import derived styles very well.


I'm not posting this to dispute the utility of LibreOffice, only because I got all excited about trying LibreOffice, and then was sad to see that it isn't the Rosetta stone I was hoping for.

Apr 22, 2014 1:17 AM in response to Bill Rising

Hello,

> It does import the text just fine, it does not import derived styles very well.

do you have some files which exhibit such a problem ? Ie. this is probably a problem that I miss(*), so...


(*) at least, if there are not ClarisWorks v2-3 files, in this case, I do know that I must change the code which retrieves the different styles :-~

Apr 22, 2014 6:22 AM in response to fosnola

fosnola wrote:


Hello,

> It does import the text just fine, it does not import derived styles very well.

do you have some files which exhibit such a problem ? Ie. this is probably a problem that I miss(*), so...


(*) at least, if there are not ClarisWorks v2-3 files, in this case, I do know that I must change the code which retrieves the different styles :-~


I do, but I should install AppleWorks on my virtual machine so that I can tell you what the styles/derived styles in the document were. I'm away from my office for the week, but I'll be able to post a file next week.

Apr 22, 2014 11:46 AM in response to PeterBreis0807

Alright Peter,


So far so good (with LibreOffice :-)



However with my 2500 Apple Works docs I need some Automator assistence - if you where would be very good. I would even be prepared to pay for it.


Something like this:


-> find next Apple Works doc > open it with LibreOffice > save it as .odt in some folder > open next one…


/

Would be nice to let the dumb computer do the work, what'ya think?



with best regards,

Omar K N

Stockholm, Sweden

Apr 22, 2014 11:33 PM in response to oktan

Hello,

one solution can be to use the LibreOffice command tool line ( see http://blog.vogella.com/2012/02/27/batch-converting-libreoffice-documents-into-p df/ ), ie. to typing in a Terminal's window something like:

/Applications/LibreOffice.app/Contents/MacOS/soffice --invisible --nologo --convert-to odt *.cwk

to convert all files *.cwk to odt


Another solution can be to modify mwawOSX ( http://sourceforge.net/projects/libmwaw/files/ ), an AppleScript which called the libmwaw library, ie. the filter that LibreOffice uses...

Converting Appleworks 6.2.3 documents created on an iMac OS 9.0.4. to Pages on my new MacBook Pro OS 10.8.3.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.