C:\ONGRTLNS.IPN
I got an e-mail yesterday on my iPhone from Dan Miller, the executive editor of Macworld’s print magazine. As you might expect, we pass around a lot of files at Macworld. Our print manuscripts are in Microsoft Word format. (Although to be honest I write most of my stories in BBEdit — one of these days we’re going to eliminate Word from our process, somehow.) Our magazine layout previews are in PDF.
So I was excited to get a real, live Macworld manuscript on my iPhone. What better way to explot its file-viewing prowess than by reading a Word file?
No dice.
It turns out that the iPhone is very particular about what files it will open. Dan, being a Mac user of the old school, doesn’t find it necessary to add “.doc” to every file he sends. So he sent me a file with the title “24.10 Security.” (That’s volume 24, issue 10 of Macworld: the October 2007 issue.) My iPhone refused to open it, and displayed it as a generic file attachment (see the top image to the left).
When I got home, I decided to investigate the issue. I renamed the file “24-10 Security.doc” and sent it to myself. Sure enough, that one came through with flying colors (see the bottom image to the left). And I could read it when I tapped on it — although not until the iPhone took quite some time to munch on the 88K file.
So be warned: if you’re an iPhone user, you’re going to need to tell your friends to always name the files they send you with extensions, or the phone simply won’t understand what to do with it. Even plain text files, which should be easy to understand, aren’t available for tapping unless followed by a “.txt” extension.
Go figure.
Category: Tips & Troubleshooting
ABOUT iPHONE CENTRAL
Get the latest news, reviews, and opinion about Apple's groundbreaking iPhone from the Apple experts at Macworld.
Want more information? Be sure to check out our complete iPhone coverage.
iPHONE VERSION
Our site's pretty iPhone friendly. But if you'd like to test an iPhone-app-like version of our site, click here and give it a go.
MACWORLD'S iPHONE REVIEW
How does the iPhone stack up? Read our in-depth review.
iPHONE QUESTIONS OR COMMENTS?
Send your iPhone thoughts:
via e-mail
via voicemail
and we may use them on the site.
RECENT COMMENTS 
- maclia on Google's Vic Gundotra on the iPhone
- Philip Michaels on Google's Vic Gundotra on the iPhone
- Daniel Chow on Google's Vic Gundotra on the iPhone
- Nathan on Google's Vic Gundotra on the iPhone
- Liz on Google's Vic Gundotra on the iPhone
- Stuart on MegaPhone now PhoneView: an app by any other name would smell as sweet
- mc mike on iPhone Love, Italian-Style
- rg on Aliph Jawbone goes double or nothing
- PJ Mudd on iPhone cleans out your wallet (in a good way)
- backguy on New Google Reader is iPhonerrific
CATEGORIES
- Accessories (39)
- AT&T (43)
- Hacking (31)
- Hardware (26)
- Musings (101)
- News (204)
- Reader Experiences (4)
- Reviews (51)
- Software (138)
- Tips & Troubleshooting (78)
- Videos (9)
- Wi-Fi (15)
BLOG ARCHIVE
- May 2008 (24)
- April 2008 (34)
- March 2008 (33)
- February 2008 (50)
- January 2008 (34)
- December 2007 (33)
- November 2007 (42)
- October 2007 (45)
- September 2007 (53)
- August 2007 (67)
- July 2007 (111)
- June 2007 (82)

Comments (8)
even though i've been a mac user for over 20 years, i made myself get into the extension habit long ago. i think it's a good habit to have, and i'm glad when i see it pay off, like in this case. i'll be danged if i can get my mac-using friends to get used to doing it, though -- it's like a mark of pride or something to not use 'em. well, maybe this will help change that.
personally, i would love to be able to SAVE the docs i receive via email somewhere on my iphone for future reference, and i can't figure out how to do that. any clue? i thought that iphoto used to handle PDF files, so that would be a workaround, but i heard that didn't work any more, so maybe apple broke it on purpose at some point.
Posted by franko | July 10, 2007 3:18 PM
And worse, the phone goes a long way toward trusting the .doc extension. (Although my test didn't seem to crash the phone.)
I took a netgear.cfg file I had lying around, and renamed a copy of it to netgear.doc. I then sent that to my phone as an attachment.
Rather than fireworks, I simply get a blank (white) screen (below the title bar or whatever that is at the top with file name and the left arrow named Message). Other non-Word .doc files might do more damage...this one is seemingly benign.
(One of the very early Windows viruses spread because Outlook Express, when it received an audio sort of MIME part whose file had a .exe extension thought to itself: "This is a sound file, I guess to play it I should execute it." (Windows Eudora put up an alert about the improper file and--at least--asked what to do.)
Posted by John Baxter
|
July 10, 2007 3:39 PM
Yes, I'm a little disappointed that the iPhone isn't looking at the file to confirm what file type it really is.
Posted by Jason Snell
|
July 10, 2007 3:49 PM
"Yes, I'm a little disappointed that the iPhone isn't looking at the file to confirm what file type it really is."
On the plus side, Jason, that is a nice C:/ prompt you've got there. So it all evens out in the end.
Posted by Kate Marshall
|
July 10, 2007 7:32 PM
Perhaps I should have made my reference more explicit.
Posted by Jason Snell
|
July 10, 2007 7:45 PM
@Jason: Cute.
Posted by Kate Marshall
|
July 11, 2007 6:01 AM
Wow, that is good to know. You guys can just figure out all the solutions to my iPhone problems and let me know about 'em ok?
Posted by David | July 11, 2007 2:26 PM
within my first 2 days of iPhone ownership I have 2 emailed mp3s that I cannot open and 4 SMS photo attachments that I can't view. What kind of multimedia device is this? Am I the only one that thinks this is bizarre? Or is it just my phone?
Posted by debbi | July 14, 2007 2:00 AM