Slashdot Mirror
RMS: Putting an End to Word Attachments
sombragris writes "I've spotted in NewsForge a very interesting editorial by none other than RMS himself on the subject of getting rid of those annoying MS Word attachment that people send. The essay is worth thinking and doubtless worth implementing." I've found that KWord and Abiword both did a fine job of reading Word files - it's the being able to Save As Word where things get messy.
When I heard that Word would support saving to HTML I was very happy. Then I saw the HTML that was output and was depressed again. Dreamweaver does have a neat feature - "clean up Word HTML" which makes them a little more acceptable, but it is a nightmare to edit in HTML anything that was generated in Word.
It's a shame, as XHTML and CSS allows for very clean separation of content from presentation... maybe someday they will hit critical mass and it will be the accepted form of "rich" content presentation. But for now I have to slog through RTF, Word, Powerpoint (ugh) and Excel documents that are not converted cleanly to the office suites on Linux.
Sig under construction since 1998.
I use Abiword to save to Word format all the time, and have never had a problem. Since Version 0.95 came out, that is. Also has lots of other niphty features. My wife and my godmother both stick to Word like postage stamps, but I use of AbiWord has never hampered my communicating with them.
You are not the customer.
Adobe has a little advertised web service that will convert a variety of documents formats, including MS Office, to PDF files. Cost is 9.95 a month, but the 5 conversion freebie trial which is controlled by email address.
Enjoy -jim
That's just the opposite of my experience with StarOffice. I've opened .doc files from the network, with "track changes" enabled, edited them in StarOffice Writer, and then saved them. None of my coworkers were ever the wiser.
I also print a lot of homework at work. I've saved my files as Word 2000 files, opened them on Word 2000, and printed without a problem.
I'd rather have someone respond than be modded up.
The difference is, PDF is perfectly readable with a number of tools, free and Free and not, without issues.
Unless things have changed, nothing reads word docs correctly all of the time...
WWJD? JWRTFM!!!
The letters in the article asked for alternative formats, which can be created with MS-Word: text, HTML, and PDF. The third can be created within MS-Word if you have Adobe's Acrobat software. (not just the reader; the distiller).
I think...I think it's in my basement. Let me go upstairs and check. -M.C. Escher (1898-1972)
No - there're several specification documents freely available from Adobe:
Scroll down to the File Format Specification section.
In fact, I believe that if you rename an RTF file so that it has the .DOC extension, it will appear to Windows users to be a normal Word document. Opening it will launch Word, which handles the file without complaining. This can be a useful trick for sending to recipients who require .doc files. You shouldn't abuse it too much, because it will inconvenience non-Word users who can deal better with RTF than DOC.
(Assuming I have Word of course.)
-jfedor
I have this problem as well. I explain to the person that they can use Word's File->Open Web Page menu option, enter the URL for my resume, and it will be opened as a Word document. (I have my resume formatted completely into a table, which makes it look right on Word as well as the web.)
If they are not willing to go that small distance for me, there is generally not going to be a good working relationship anyway.
-- Two men say they're Jesus. One of them must be wrong. - Dire Straits
Richard's wrath is misdirected: if the MS Email clients emitted proper RFC compliant MIME email---where each message had a plain text part and a rich text (i.e., MS Word) part---then there wouldn't be the same issue. MS's very poor record complying to RFCs and other industry standards is the real problem, not the use of MS Word.
None of MS's email clients emit RFC compliant email. MS Outlook combined with an MS Exchange server running in Enterprise Mode can be coerced into sending almost compliant email messages, but it is tough to do and the messages are still problematic enough that some email systems cannot deal with the resultant messages (e.g., Exchange to Notes email is very troublesome).
At my old job, our engineering department successfully lobbied for people to stop sending documents as Word attachments.
Their explanation was a little simpler, which was basically, "Hi. Those of us with Unix machines don't have Word installed, so it's a major pain in the ass for us to read that document you just attached. Can you send it in a different format?" Personally, I wouldn't recommend using any of the examples in the article, as they all sound pretty self-righteous and would probably make an average recipient more likely to walk over and give the writer a massive wedgie than to change their email attachment behavior.
The drawback, of course, is that the people who were sending Word attachments in the first place were still composing them in MS Word. And so you've either got to deal with the huge mess that is Word's "Save as HTML" or you lose all the pretty formatting (which does sometimes include important diagrams or tables) when it's saved as text. But I suppose it's a moral victory, if nothing else...
"Do you expect me to talk?" "No, Mr. Bond. I expect you to die!"
For business, definively not. My company generates docs of hundreds of pages. It would takes days to reformat one of them (I had to, a couple of times :-( ).
And it is not only the good-looking. For large docs, things like cross-reference and automatic indexes are a god blessing.
Ciao
----
FB
T
I spent a lot of money on booze, birds and fast cars. The rest I just squandered. - George Best
Here's a perl kludge I use to convert doc on the fly into PDF and open in acrobat from kmail:
/_/g;
/\\ /g;
#!/usr/bin/perl
my $fn=shift;
my $or=$fn;
$fn=~s/.*\/(.*)\.doc$/$1/o;
$fn=~s/
$or =~ s/
`antiword -p letter $or | ps2pdf - > $HOME/tmp/$fn.pdf `;
exec("/usr/bin/acroread $HOME/tmp/$fn.pdf");
It does require antiword which you can obtain from freshmeat.
My poetry site welcomes the unusual.
"Most computers come with Microsoft Windows pre-installed. Getting the MS Office suite isn't that difficult (either legally or illegally).
The only reason you would NOT use MS Office is ideology. "
True. And by my ideology, stealing is wrong. Since I can't afford to buy a copy of MS Office (and really wouldn't wish to spend that much money simply to read email attachments, even if I could), I don't have MS Office. There's also the little fact that I run linux on my home system, and Office isn't known for it's compatibility with linux. And no, I don't run linux for political or ideological reasons; I run linux because I believe it's a better system. My computer doesn't crash, I don't have to upgrade my system every time a new version is released, and I have massive amounts of free (as in beer) software to play with. The fact that I agree with much of the ideology is a bonus, but wasn't enough to get me over to linux until I found that it suited my needs much better than Windows did.
I just opened up Word '97 and typed two letters ("Hi") into a new document and saved the file. This file is 19,456 bytes. What was a simple email has now become large and complex. Not good.
See LyX or kLyX, that will fill many of your needs. I usually start files as LyX files then, when they get too big to easily handle in a WYSWIG editor, export to LaTeX and break the document up into multiple files and continue on in "raw" LaTeX from that point (it is quite easy to cut and paste out of an existing LaTeX doc, somewhat troublesome to create a LaTeX doc from scratch w/o a template).
Send mail here if you want to reach me.
"And because Microsoft changes the Word file format with each release, its users are locked into a system that compels them to buy each upgrade whether they want a change or not. "
This statement is incorrect... Microsoft redefined the file format with Word 97 to make it extensible. SO the basic text, formatting, images, etc are all compatible between Word 97, 2000, and XP. I can save a Word file in WordXP and open it in Word 97 without any sort of conversion or downgrading... its just that the "extensions" not supported by Word 97 won't be displayed or might be displayed incorrectly.
The differences between 97 and 2000 are especially small... we have about 85% of our users on Office 97 and they exchange documents both ways with our other users of Office 2000. Of course they don't do anything special with fileformats (remember: these users think their keyboard can 'get a virus') -- the Word 97 users can open the Word 2000 files without conversion.
Natural != (nontoxic || beneficial)
If someone wants a resume in word format, just send it to them in html format. They will most likely be too ignorant to know the difference.
Now it could be a problem, when they send you stuff back in word format.
1. Nice screw up on the analogy on part one. I can take a car to a mechanic for scheduled maintenance (bug fixen), or I can do the oil change myself. I don't, personally, but I'm happy that I don't have to take my Chrysler to a Chrysler dealer in order to do that.
2. A car is a car is a car, whether its a 2002 Viper or a 1985 Ford Tempo. A 1985 Ford Tempo, if you can find one, can probably be purchased for the same as Word. Software is software is software, no matter what the price point.
3. I write Content Management software for a web development company. People need to get into that code all the time. People need to get into the code in Word, or Outlook, or other Office products to fix buffer overflows and other bugs. The fact that I can't but Joe at Redmond can is the point, and the problem.
4. (the coffee maker argument) Point to you, *but* if I heavily modified my cars looks (a fair number of people heavily tweak the settings in Word, turning off things like AutoCorrect), and somebody broke a window, I'd rather not have to make my car look like it did when I first drove it off the lot. Similarly, I'd rather not have to download all my patches again because my mom accidentally deleted some obscure file I didn't know that Word needed.
The point is that anybody who happens to think that "I wish I could change function X in Word, because it isn't powerful enough for me" is in no way allowed to do that. Just because you will never exercise a liberty does not mean that it's okay to take that liberty away. Slippery slope, and all that.
Is this post not nifty? Sluggy Freelance. Worshi
Actually, Works does not include Word. It has an editor that supports many formats, including older word formats, but not the newest. That's why Works is so cheap. And frankly, for most people, it seems to have more than enough power and features.
Works has included the most recent version of Word for a while now. I bought a computer a year ago and it came with Works preloaded, and Word 2000 was right there with it. I don't know how long it has been a part of it, but it IS a part of it now.
Many modifications are possible, of course. (P.S. The indentation is nicer in my file, but the lameness filter won't allow it. Sorry.)
Now, my message: