Reading MS Word '.docm' (macro enabled doc) files

Someone sent me a file that Pages '09 wouldn't open. The author told me the files opened in Word 2007 and what the format was. Then he sent me a version compatible with Word2003 which was OK in Pages. So my question is why? Why is Pages incompatible with this format? And why is there no update?

Henry

MacPro1,1 2.66GHz. 4 Core, MBP 15" 2.0GHz, MB2008 2.0GHz, Mac Mini (10.5.8), Mac OS X (10.6.1), iPhone 3G, AEBS 802.11n

Posted on Feb 17, 2010 5:18 PM

Reply
16 replies

Feb 18, 2010 1:55 AM in response to Tom Gewecke

Tom Gewecke wrote:
So my question is why?


You're not talking to Apple here, just other users like yourself who can't possibly know why. To tell Apple you want an update with some new feature, use this link:

http://www.apple.com/feedback/pages.html

Okee-dokee.

So maybe the first question should have been, does anybody else know about this or am I the only one? Can you at least confirm it??

Feb 18, 2010 2:32 AM in response to HenryS

In the Pages User Guide it is stated:

+Opening a Document from Another Application+
+You can create a new Pages document by importing a document created in another application, such as Microsoft Office 2007 or AppleWorks. Pages can import the following file formats: plain text (.txt), Rich Text Format (.rtf and .rtfd), AppleWorks 6 word processing (.cwk), and Microsoft Word (.doc).+

Some people has also been able to open .docx files

Feb 18, 2010 3:14 AM in response to fruhulda

fruhulda wrote:
In the Pages User Guide it is stated:

+Opening a Document from Another Application+
+You can create a new Pages document by importing a document created in another application, such as Microsoft Office 2007 or AppleWorks. Pages can import the following file formats: plain text (.txt), Rich Text Format (.rtf and .rtfd), AppleWorks 6 word processing (.cwk), and Microsoft Word (.doc).+

Some people has also been able to open .docx files


Hello fruhulda

the problem is that many users never look at the User Guide based on the bad old formula ReadThisFu…ingManual 😟

Yvan KOENIG (VALLAURIS, France) jeudi 18 février 2010 12:14:38

Feb 18, 2010 3:39 AM in response to fruhulda

fruhulda wrote:
Also talk to Microsoft and ask them why they don't make their apps more compatible.

Ask the sender to send a document that isn't macro enabled. Pages doesn't do macros.

Clearly. And why not read it as a text file? But Pages Manual says that depending on the doc being read they do strip macro information from certain imports. So (like M$) why can't the app strip off un-readable macros? TextEdit has no problem reading this doc as text, coincidentally stripping the macros, and retaining formatting, just like I'd expect Pages to do.

This isn't (in my fuzzy logic) mind at least a M$ problem, rather Pages is flawed. If I look at the info on this doc, it says it is an XML document. I also read the manual (thanks to the poster who says people don't RTFM) about the types of files supposedly compatible in Pages. Clearly the point of the section others partially quoted about the type of files that ARE compatible (.doc, etc.) seems actually directed to show users (and to have them understand) that _ALL documents formats that can be saved in M$ Word2007 are NOT readable in Pages_. Hence, if someone incorrectly formats a document as an XML format of some kind, perhaps as a default, then sends it on, the recipient is left with a dilemma.

As to what happened here, I probably wasn't clear in my rant.

I found that I could also open the document in TextEdit (Apple version 1.6(264)). For what I wanted, that was good enough.

Feb 18, 2010 7:14 AM in response to HenryS

HenryS wrote:
fruhulda wrote:
Also talk to Microsoft and ask them why they don't make their apps more compatible.

Ask the sender to send a document that isn't macro enabled. Pages doesn't do macros.

Clearly. And why not read it as a text file?


Because, extracting the text require the knowledge of the document internal structure.

But Pages Manual says that depending on the doc being read they do strip macro information from certain imports. So (like M$) why can't the app strip off un-readable macros?


Same responce : doing that requires the knowledge of the document internal structure.

TextEdit has no problem reading this doc as text, coincidentally stripping the macros, and retaining formatting, just like I'd expect Pages to do.


The team building TextEdit isn't the one designing Pages so they may have different point of view and are free to think different.

This isn't (in my fuzzy logic) mind at least a M$ problem, rather Pages is flawed. If I look at the info on this doc, it says it is an XML document. I also read the manual (thanks to the poster who says people don't RTFM) about the types of files supposedly compatible in Pages. Clearly the point of the section others partially quoted about the type of files that ARE compatible (.doc, etc.) seems actually directed to show users (and to have them understand) that _ALL documents formats that can be saved in M$ Word2007 are NOT readable in Pages_. Hence, if someone incorrectly formats a document as an XML format of some kind, perhaps as a default, then sends it on, the recipient is left with a dilemma.


Perfectly logic. If someone write a letter in cuneiform scripting, the recipient will be left with the same kind of dilemna.
When I send something to somebody, if I want to be read, I take care to ask which format he is able to decipher !

As to what happened here, I probably wasn't clear in my rant.


Yvan KOENIG (VALLAURIS, France) jeudi 18 février 2010 16:14:06

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Reading MS Word '.docm' (macro enabled doc) files

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