RMS: Putting an End to Word Attachments 1022
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.
unfortunate ? (Score:4, Insightful)
Most Word users, I expect, want to write letters to their mothers, not recompile the application.
.doc is a de facto standard (Score:2, Insightful)
RMS spouting off (as usual) (Score:1, Insightful)
Honestly, the people that attach word docs are usually the people that give you a blank stare when you say words like 'linux' and 'unix'. They're the people that work in accounting and marketing that only know how to use Word, Excel, PowerPoint, and Exchange.
If you write a polite reply, asking them (usually putting in instructions) to cut-and-paste the word doc into exchange, and send it in normal text, and an explanation why, they usually comply.
Honestly, what does RMS expect to accomplish with this editorial?
The people that read it don't send word attachments anyway.
Going in and telling people to "Stop sending documents in Word!" Is not giving people the 'choice' on what wordprocessor to use. Isn't he supposed to support the 'choice', or just his idea??
PDF? (Score:4, Insightful)
Thats not the problem (Score:4, Insightful)
You don't need email with Word attachments. The problem is having such a format be so widespead that it interferes with normal communication, like email. I am a UNIX network engineer that has been bitten *many* times by the 'please send a resume as a Word doc'. That is difficult if you don't run Windows at all.
Though I generally feel RMS isn't an effective speaker, he definitely has a point here. Honestly, do people really need Word for the majority of text documents? Is everyone sending emails with tabular, image-embedded documents? I think not.
Re:.doc is a de facto standard (Score:4, Insightful)
Word documents, along with other proprietary formats, especially ones which may or may not be able to be opened with future software, are a bad idea for information transfer.
It's a stupid, terrible, dumb standard which Microsoft revels in because it helps to ensure their position and sales.
It behooves everyone who uses computers to compose documents and share information to break the current standard
This, I believe, is RMS's point. The fact that he has Open Source advocates' ears is a fact of reality, not the ideal.
Personal versus Political (Score:5, Insightful)
A more general issue is that all of the examples provided are political in nature.
Could one accomplish something similar with a message like "I'm sorry but I'm unable to read documents in Microsoft Word format because I use Linux. Please send your document in a format that I can read, such as ASCII Text or PDF."
Educating people about the political issues surrounding proprietary document formats isn't always appropriate in a business situation. If I need to ask a customer to use a format other than Word, I also need to be able to do it in a non-alienating way. I think that Stallman offers some good suggestions, but the specific examples he provides wouldn't work well in some social contexts.
Re:.doc is a de facto standard (Score:2, Insightful)
No matter how much it may seem that
Truly amazing (Score:1, Insightful)
Instead of getting on your soapbox about Word files, a much more productive approach would be to support the development and extensive testing of import filters for Word files. I have a lot of experience in this area, and I can tell you without hesitation that correctly importing Word files of arbitrary complexity is a far more difficult task than even most programmers know. The Word format has got to be one of the most Byzantine file formats ever created, especially when you start adding embedded or linked graphics.
We first need ... (Score:5, Insightful)
That is, it should be possible to read and edit the same document with different open-source tools [since there is no chance that we all use the same] without loosing neither text, nor formatting or meta information (like indexes, cross-references, review marks etc...).
Re:.doc is a de facto standard (Score:5, Insightful)
No.
RMS' main problem with Word format is that it is non-standard, and most people probably don't care. But that isn't the only problem that format has. The other major problem it has is the same thing you'll find in most MS formats: it contains too much power. In order to support Word format in a Word-compatable way, you have to support the scripting language and virus capability too.
And that is a Bad Thing, even if you don't give a damn about open vs closed formats. Getting people off Word format is a good idea for everyone except for anti-virus software vendors.
So if RMS' goal seems unrealistic because it's too idealistic, by all means, just be pragmatic instead. And the pragmatic thing to do is say goodbye to MS Word's file format.
Re:.doc is a de facto standard (Score:4, Insightful)
While the premise of your argument may be unfortunately true, the suggestion simply won't work because Microsoft won't let it work. That's why they keep changing the format and don't publish the spec in the first place.
Red Herring (Score:5, Insightful)
Re:RMS spouting off (as usual) (Score:4, Insightful)
RMS is suggesting that supporters of free software, when they receive an attachment in Microsoft Word format, request the attachment be sent again in a non-proprietary format such as HTML or ASCII text. He provides three boilerplate replies, mostly polite and one includes instuctions.
No where in the article does he ask people to stop using Word, nor does his suggestion limit their choice of wordprocessors.
In his suggested reply text, their is only a passing mention of GNU/Linux in the first and no mentions of Linux/UNIX in the other two.
Please take your ignorant posts elsewhere.
Simple. (Score:2, Insightful)
Its really two situations. Both parties can read text while both parties may not be able to read
Re:PDF? (Score:2, Insightful)
No need to be a prick (Score:3, Insightful)
That said, Stallman is proposing a particularly counterproductive way to go about it. When I receive a file I can't open, I send a polite message to the effect of, "I can't read that file format. Please save the file in RTF format (Select "Save As.." from the File menu, and then choose Rich Text) and resend it. In the future, please send me files that way, so I'll be able to open them right away."
That has the advantages of a) not confusing the secretary or supplier who doesn't even know that there are different file formats with some political rant about Kenya, the Microsoft monopoly, bytes and freedom, b) doesn't convince a more knowledgeable recipient that Linux users are rabid, socially dysfunctional loons and c) is the way a decent human being behaves.
Richard Stallman probably doesn't realize that when the rest of us receive a Word attachment, it's not from a reporter seeking our views on Free Software and appreciating his tantrums as a little added color for his article, it's from a coworker just doing what any normal computer user does.
Re:Thats not the problem (Score:2, Insightful)
Should be positive instead of negative (Score:1, Insightful)
Re:Personal versus Political (Score:5, Insightful)
No. The general response (from my experience) has been, "Then you suck and there's nothing I can do about it. You should use Windows."
You _must_ explain why Word attachments themselves are the problem and how to get around them.
I've found the "size of the attachment" argument to be the most effective (and that's relative
Actually, recently, many users have been bitten enough times with transferring documents up through old versions of Word that they pay attention to, "Do you really want to be using a program which saves information in a form which may be unusable or, most probably, improperly read in a year or two?"
Finally, sometimes I just outright lie and say, "Oh, man, I'm sorry I don't have Word XP (or whatever), could you maybe save it in Word 95 format
Re:Wishful Thinking (Score:4, Insightful)
Good idea wrung and ruined thru Stallman (Score:2, Insightful)
But to "politely" call those who use
Stallman's not worried about secret file formats (which he should drop from those silly email replies about
* Write a vba script for Word that turns
* Suggest that they use AbiWord, something that can read
Stallman is, imo, no better than Microsoft in that he has great ideas wrung through a strange, self-serving translator that mangles the original, useful message. In MS's case, it's a profit maximization machine. In Stallman's, it's GNU. Both biases serve to dilute what could have been a well-received and useful technology or lesson, and this Word scare is another one.
"a polite reply"? (Score:1, Insightful)
Oh, wait, all three(four?) describe RMS
Seriously, half the problem is that we've got this guy, who has NO tact or social skills, as one of the most visible "lobbyists"...when asking people to do something aside from their set routine, you MUST be VERY tactful and polite...
RMS - Typical. (Score:1, Insightful)
Some people use word because it supports documents
that are not typed in US-ASCII. Chinese, Japanese
you get the point? 300 million Americans do not
represent the whole of humanity.
At least Microsoft has made their latest OS's
totally UNICODE. I would like you to show me
a UNIX derivative OS that can say the same.
Yeah, keep looking for things to complain about.
- Penguin Kicka
Re:.doc is a de facto standard (Score:5, Insightful)
And by the way, you shouldn't be so quick to underestimate Microsoft's morals/motives. They're monopolistic and nosy and untrustworthy, granted, but they do make good products that are easy to use and featureful. It's naive to believe that they are into just screwing the customer over with every successful revision. If they really were that stupid and antipathetic towards the people paying the bills, I doubt they'd be the largest software company in the entire world.
Re:RMS is full of shit (Score:4, Insightful)
In a word, yes.
The only reason you would NOT use MS Office is ideology.
Oh, and ideology is such a horrible thing. Ideology is what prompted colonists to buck taxation without representation too. I guess you think that's horrible as well.
Pragmatism is not such a wonderful thing. You can thank pragmatism for corporations who would rather pay MS license fees than save jobs.
Then I got a job and learnt that tolerance instead of shitty elitism is the way to go. Too bad RMS never learnt that.
Asking people to send plain-text or HTML is not "shitty elitism" -- it's asking people to recognize that they are non-proprietary formats that anyone can view on any platform. How is that bad? Maybe you don't like RMS' phrasing, which is understandable because he tends to devolve into hippy-ish terminology, but the ideas are valid.
Asking people not to send MS attachments, politely, is not fanaticism. It's an attempt to change people's minds. You don't like it? Fine, but don't call it fanaticism, because it's not. It's simply a viewpoint that's different than yours. He has a right to express it. If you think differently, (that he shouldn't express it, not that you don't agree) perhaps RMS isn't the fanatic here.
You didn't learn tolerance, you conformed. There's a difference. Tolerance would be understanding that the world is not fully comprised of Microsoft Word users, and that there are people who do not want to be forced to use Word to correspond with the people who choose to -- or who simply don't think about it at all.
You sound like one of those (Score:4, Insightful)
When you send them polite reply that they should send normal email in text format, attach only pre-written documents if there's no way to convert into another format that engineers can read. The next thing you know, you get a review of having a bad attitude and you don't want to cooperate. And you know where that comments come from, right?
It's a royal pain in the butt when you have one Windows machine shared between 20 engineers all working on Unix.
Re:Thats not the problem (Score:2, Insightful)
Re:We first need ... (Score:3, Insightful)
We first need...
Welcome to
Now, the above post was meant in jest, I understand there are sometimes where a nice looking document will go a long way (price-quotes, resumes, etc), but, really, how many people need something other than
~z
Staroffice 6.0 (Score:2, Insightful)
Re:Personal versus Political (Score:5, Insightful)
Perhaps just turn it around, like "I'm sorry but I cannot access the file you sent me, because you sent it in a format that is only usable in Windows. Please use a format that is more accessible to all computer users, such as plain text or PDF".
Maybe?
Re:Thats not the problem (Score:4, Insightful)
I think he was trying to make two points. This is one of them, the other is that sending Word attachments complicates life for people who don't use Word -- and unintentionally or intentionally continues the idea that Word is the de facto standard so everyone should just go ahead and buy Windows and Office and conform already.
If you're happy using proprietary MS products, cool. That's okay, I don't agree with it, but whatever. Just don't force your choice on my by choosing to send a proprietary bloated attachment instead of a nice neat plain-text message that I could read in my mail client.
It's one thing if you're sending a QuarkXPress attachment to a printer so they can do a job for you. That justifies a proprietary format, rather than sending plain-text. But many PR people and business folks just write something in Word and attach it, when it's a press release or something that could be plain-text with no loss in information.
It's not just a viewing thing either, RMS travels a lot and probably collects email via modem. It's annoying to spend an hour downloading your email because two jerks decided to send Word attachments rather than a simple email. I've been there, done that, hated it.
I'm a writer for several tech pubs, and I refuse to open Word attachments sent by PR flacks. Send it in plain text, or forget about being covered. I'd do the same thing even if I used Windows. Why? Because sending attachments that can carry viruses is also rude.
There are a lot of good reasons NOT to send Word attachments, and no good reasons to send them.
I only wish someone else other than RMS had spoken up about this. People automatically dismiss RMS because they percieve him as being too rigid, which he is, but he has good points as well.
Re:Same with my car (Score:3, Insightful)
1) Cars require regular maintenance. Word processors don't (or shouldn't).
2) Cars cost hundred times more than word processors.
3) Amortization and used car sale.
More appropriate comparison would be with something like your coffee maker. Many of us use things every day, but we don't care what's inside.
Yes, we need to "Be A Prick"! (Score:3, Insightful)
Browse Slashdot at -1. How many of those trolls would you not need to beat with a clue-by-four within an inch of their lives to get them to post on-topic? (I don't mean just once or sometimes, I mean forever and always.)
My sister is like this. Every six months I get another chain letter from her ("Re: New Virus Warning" or maybe "Re:Great Internet Snowball Fight 2005"). I do not like chain letters. They are spam; I filter them as such. Each time she sends me a chain letter, I send a very polite "don't do this again; chain letters go to my trashcan"-style response.
Maybe I ought to take a clue from RMS; tell her that I believe chain letters consumes network resources, that massive numbers can become counter productive-- in short all the standard anti-spam arguments. If I present myself calmly and rationally I expect (from experience) that she will stop. If I do a really good job, maybe she'll change her opinion. Take this example from letter 2: "Receiving Word attachments is bad for you because they can carry viruses" is calm, well spoken, and provides a reason that the sender may never want to see another Word file themselves. Spoken in this manner they might see your "opinion" against Word
Something tells me that's the reason my sister keeps sending me spam: I've never really told her why I want her to stop (just been a prick and threatened to trash her emails to me, if in a polite manner).
Freedom only has value... (Score:2, Insightful)
RMS sometimes lives in a fantasy world, as evidenced by this quote from the article:
I hate to break it to you, Robert, but the vast majority of computer users couldn't program their way out of an "if" statement. And they don't want to program. You and I may have a grand time exploring code and writing software; most people just want to sit down, write a note to Aunt Emma, read the joke their kid sent them from college, or check the latest football score. They want to play Quake, not write it.
The freedom to examine a program's source code is meaningless to 99% of computer users. They'd rather spend a hundred (or two) bucks on an upgrade than learn C...
Now, as for getting rid of Word attachments, I totally agree. I also despise HTML e-mail. I'd love for them to go away -- but even some programmers I know can't send an e-mail unless it contains a dozen fonts and background images. And don't forget its easy to be on a religious crusade when you don't live in the real world. You may be able to tell people to stop sending Word attachments; I say such a thing to a potential client, and I guarantee they'll hire someone else.
I note that O'Reilly, supposed scion of Open Source, uses Word for all of its book publishing. I spent more time fiddling with their damned Word templates than I did writing a book (not yet printed)... but was I going to refuse a book contract because they kept mailing Word docs around? I think not...
Re:Thats not the problem (Score:2, Insightful)
Re:Thats not the problem (Score:5, Insightful)
It's about having the freedom to do this, not necessarily using it.
To take an analogy from another post, I wouldn't buy a car with the hood locked so only the dealer could open it. But let me be frank -- there is really nothing productive I could do by opening the hood, except check the oil. I'm useless with cars. But being -able- to is good. Plus, I know that if I had a friend who did know cars, they could modify it.
Similarly, I am very glad that I have rights under the Freedom of Information Act, even though I've never used them and may never feel the need to.
Just because you, personally may never hack a line of code in an app doesn't mean that you don't benefit from having the right to. Remember, you have the right to and so does everyone else, and "everyone else" includes a lot of programmers.
but RMS is making a politcal point (Score:3, Insightful)
And the whole thrust of this article was not "Let's convince people to send us documents we can read" it was "Let's use the issue of not being able to read these documents to promote the wider issue of Free Software".
I happen to disagree with RMS but what he's saying is totally consistent with his beliefs. I would no more expect him to use 'non-political' examples than I would for him to call GNU software Open Source.
RMS Missed the point, again. (Score:2, Insightful)
All they want to do is read their email and use their documents. If they have to forward it on to someone else then they just want to take the document and drop it in a letter and send it on. They don't want to have to deal with the complete and total hassle of opening the document and saving it off as some sort of Stallman approved attachment and then dropping that into an email attachment.
The whole point behind the computer age is that these machines are supposed to make our lives easier. I for one could care less who owns the format for Microsoft
The other possibility is that Microsoft obsoletes documents written more than seven or some years ago. This is, of course, nutty because Microsoft's customers would sue them into the poor house, or worse, just stop buying upgrades.
Think I'm wrong, take a look at how long it took for them to get ride of the 8086 stuff, and that was an idea everybody agreed on.
I understand Stallman's political point but what he is doing is guaranteeing that he never sees another email from someone who uses Word. His proposed solution is little more than taking a tiny sharp stick and digging it around in an open wound. Or worse, its just another rock in the shoe of life.
Want to make a political statement? Then ask why
It's the users, silly! (Score:2, Insightful)
If you email someone saying not to send Word documents (and I know this from experience), they are baffled. They don't know what file formats are. They don't know what ascii text is. They don't even know how to copy-n-paste for Pete's sake!!!
Asking actual end-users to use a different format, or copy-n-paste text, is like asking a monkey to set the table.
Plus, you come across as an elitist geek snob. Joe Jackass end-user couldn't care less about proprietary formats, open source, operating systems, etc. Until this elementary fact is well understood, open-source will continue to get the cold shoulder from the 90% of people out there who qualify as "end-users".
Now how do I do this and stay in business? (Score:5, Insightful)
Clients, unconsciously, have a scale in their head that weighs how much they've put into me versus how much they've received back from me. Every little thing I ask them to give me or do for me reduces their perception of the benefit/cost ratio, and reduces the likelyhood they'll use my services again. Really, clients generally want me to come in and pull a completed job out of thin air with no assets from them, and much as they technically understand that they have to give me stuff to work with they don't actually like it.
So, I make a point to bend over backward for the client on the little stuff so that when I do have to ask the client for something, it's always something that's really important to the project. Convincing them to support free software does not constitute "important to the project".
I can just imagine telling a client I can't read their Word file. They'll think I'm incompetent for being improperly equipped and replace me.
Like it or not I'm stuck with Word unless a court breaks up the Microsoft monopolies and businesses start using more of a variety of software. I can give my clients PDFs, but that isn't going to change their file habits anytime soon.
Low Hurdle (Score:2, Insightful)
It's a stupid requirement, sure, but would you hire someone who can't (or won't) problem-solve? Apart from the obvious technical solutions, you could go to Kinko's, or ask a friend, or whatever. If this is a showstopper for a job applicant, they're either an idiot or a prima donna.Neither one makes a very good employee.
Re:RMS is full of shit (Score:2, Insightful)
It's always so funny to see people with such simple problems trying to compare them to matters of great import.
That is the very definition of a fanatic.
Comment removed (Score:5, Insightful)
Re:Thats not the problem (Score:4, Insightful)
Hmmm, no good reasons to send Word attachments? How about formatting, tables, graphics, password-protection, spelling/grammar checking, highlighting, correction/collaboration. All supported by the fact that (as RMS admits) most computer users can read Word documents - even if it's a scaled down Wordpad reader.
Re:.doc is a de facto standard (Score:2, Insightful)
- Standards composed by standards bodies (e.g. HTML).
- Standards which become standards due to their wide acceptance (e.g. PDF).
MS's DOC format is the latter type of standard. Many many MANY people use this format daily, and it's not going away any time soon.As much as I'd rather have the world distribute formatted docs in HTML (or better yet XML + XSL), it's not going to happen. Trying to get people to distribute formatted docs as PDF files (which can be read on almost all graphical interfaces) is also a non-starter, as Acrobat is an add-on, and you can't simply save to PDF format. It's too much work for "normal" computer users to save to PDF (or RTF or even ASCII).
As much as we all hate to admit it, the problem being addressed in this forum is only a problem to a small percentage of email users. Most email users are running MS Office on Windows 98 or 2000, and they're not having any problems with the attachments.
We'll just need to bite the bullet and either read the Word docs with Open Source applications like AbiWord, or do as I do, which is to either run Windows (and MS Office) on a second machine or in VMWare.
Trying to get the vast majority of email users to change their habits because of a few people is most likely a waste of time.
Then again, how many of us actually do receive Word docs as attachments on a regular basis? Outside of a work environment (where Windows is the standard platform), I'd bet very few.
Re:RTF file with .doc extension (Score:3, Insightful)
This question ranks up there with, "Well, if the problem is that it takes a long time to download stuff over the Internet, why doesn't everybody just get DS-3 lines to their house? Duh."
The reason we're often dependent on the name to determine the type of a file is that so far, it seems to be the only thing that really makes sense. Requiring that an OS read the beginning of a file to determine its type isn't practical: consider the case when you open up a directory full of files, and every one has to be read in order to determine its type. Plus, any files you have that don't conform to your header standard - basically, anything that adheres to any other standard - won't show up correctly. And what do you do when the "file" is actually a block device on a *NIX system?
Using file extensions to determine the type of a file is a good idea in general, that was made into a requirement on the Windows platform. Maybe MS could have gone about it better, but I'm not going to fault them for the decision.
Oh, by the way: if you're really intent on escaping that "legacy" of DOS/Windows, just use Linux (or whatever). You can name executable files whatever you want. (although you may fuck up your terminal when you try to read it using "more". Been there, done that.)
Re:Personal versus Political (Score:4, Insightful)
"I'm sorry, but I cannot view the attachment that you sent to me because it is a Microsoft Word document (.doc extension). Microsoft Word documents are only accessible to people using software that is approved by Microsoft. Please consider using a format that is freely accessible such as HTML, PDF or plain text. This will ensure that files that you send are readable by anyone who receives them."
Re:RMS is full of shit (Score:3, Insightful)
Or, he should steal it?
Isn't politely asking the user to send it in another format, one that they have in common, a better answer?
Good reasons to send Word attachments (Score:4, Insightful)
I use Word attachments every day. I couldn't do my job without them.
Is Word the best thing since sliced bread? No.
Is Word worth using? Yes.
The main thing I use Word for, besides all the fancy formatting stuff which is not even strictly necessary, is collaboration/reviewing. I write professionally, and I need to be able to track changes through several review cycles (editors, client, legal, publication). To my knowledge, no other widely-available word processing solution supports these features, at least not the extent the .doc format does.
But it's still not enough to make me use MSWord for all my editing (although I keep a copy in my VMware Win98 just in case). I use StarOffice 6 and love it. I really only have two qualms about it:
When I first switched to using Linux full-time for work, nobody at the office noticed. (I telecommute, so no one could actually see my desktop.) At the time, I was using Mandrake + KMail + StarOffice 5.2 -- the only one who knew about it was the editor directly above me, and he's cool with Linux. (Even he wouldn't have known if I hadn't told him.)
What I mean to say is: the Word .doc format has a number of very useful features I couldn't live without. But that doesn't mean I have to use Word. In Evolution, I can open Word attachments in StarOffice seamlessly -- and since StarOffice doesn't quite support VB, I've yet to find a document which could cause damage to my system.
I do agree, however, that you shouldn't use .doc files when something simpler or lighter (like plain text) would do the job as well. I'm involved with PR, and I've seen embarrassing things happen to clients when someone stupid converts a Word doc to HTML and posts it on their site. One page had internal tracking info in the title which actually referred to a different project which had been used as source material. On the website, this information was paraded across the title bar.
Tangent: why does Word include a "title" field in the document properties which it never displays to the user? Word's titlebar just shows the filename without path -- for me, a completely useless piece of informaiton, since I often have identically-named but very different files in separate sections of my file tree. StarOffice's title bar (which displays the contents of the "title" field) is much, much better... yet another reason to use .doc, and just not use M$Word.
Hey, sorry to ramble on like this.... just my two and a half cents.
Re:RMS is full of shit (Score:3, Insightful)
I think that's why most linux-users use linux. I recall that the reason I first used it was because Windows 95 sucked really badly(crash, crash, crash. Even when I wasn't moving the mouse, even with a fresh, clean install. Call it hardware problems, but every other OS ran without any problems.)
Later I found out it was free and the code was available, and I thought "Cool! I legally own this software!", and it was a bonus.
The person above has apparantly never needed to pay for his software, nor does he have a problem with people being forced to buy redundant copies of software(I use lotus wordpro or Cetus WordPad -- why the hell should I be forced to pay for software I consider inferior, especially when it's so damn expensive?)
The usual snobbery (Score:2, Insightful)
The problem here is that an average person does not care about making the future better for everybody. They just care about saving time and money. Now, an average linux user does care about making the future better for everyone, but linux users are few and far between. Instead of trying to guilt-trip the user into submission, it might be better to say,
Re:RMS is full of shit (Score:1, Insightful)
No, the word I was looking for to convey the meaning of 'simplistic' was 'simplistic.'
Re:PDF? (Score:2, Insightful)
Re:RMS is full of shit (Score:3, Insightful)
Elitism is not the same thing as disliking or even hating proprietary software. Please, for the love of whatever God you worship and the good of humanity, buy a fscking dictionary and look words up before you use them. It degrades the language when you don't use it properly.
(And that is probably a good example of me being an elitist language snob, which doesn't bother me in the least. I have a funny idea that people should be able to master their native language...)
RMS isn't asking that people use *Free* Software to send email, merely that they don't use proprietary formats. That's not unreasonable. Granted, RMS would probably prefer it if you did, but that's not the discussion here. Discussion works much better if you limit yourself to the actual discussion rather than trying to re-frame the discussion.
Yes, let's not be software Nazis. Let's all use software that can communicate in open formats so that everyone can use what they want. I agree with that. That doesn't discount Word, either -- it just means that they have to hit "save as" and choose text or HTML. Unfortunately, when someone chooses to send Word docs, they're forcing me to:
A. Give up my preferred program for reading email and open the attachment in another program. (I also despise HTML and PDF for this, but that's just a general hatred of attachments...)
B. Adopt a program I don't like and do not wish to pay for.
C. Not read the attachment.
Asking people to send a non-proprietary format is not unreasonable.
Asking that no one dare bring the topic up because it disagrees with your world-view and because you happen to think that everyone should just conform and use YOUR choice is unreasonable.
Re:Thats not the problem (Score:4, Insightful)
It's funny, because in the article that spawned this discussion, he doesn't once say anything against using Word, just sending documents in Word format to others.
But sending people documents in Word format (and refusing to cease this practice) is much closer to "forcing" someone else to use Word. It's not literally forcing, but it is applying leverage on them, if they want to read your docs. I can't actually think of anytime RMS has applied any leverage on someone to use free software.
Re:RMS is incorrect (Score:2, Insightful)
So it does kindof compel users to upgrade, wouldn't you say?
a.
Three letters (Score:2, Insightful)
Re: Can't open Word Document (Score:1, Insightful)
Dear Mr. Stallman,
Your overly "closed-minded" and selfish approach to a simple obstacle has confirmed our suspicion that you are an idiot.
When you come to work on Monday, you will find that your security card has been disabled. Please contact the security team for an escort into the building, they will be expecting you. You will have 30 minutes to clear your personal belongings from the building and un-ass the premises.
For future reference, the world owes you nothing. If you choose to use a non-industry standard word processor, please expect to put up with, and overcome, such trivial inconveniences.
>You sent the attachment in Microsoft Word format, a secret proprietary format so it is hard for me to read.
>If you send me plain text, HTML,
>or PDF, then I will read it.
Re:Personal versus Political (Score:2, Insightful)
That way you have a good reason, and you question their sanity for using Word.
No usual user has heard of Linux, but they are afraid of virii and will do anything you say.
Re:We have been trying to do that for years. (Score:2, Insightful)
Now that was flamebait (or maybe a troll). My original statement, as much as you may disagree with it, was dead on. Just ask anyone who deals with customers.
Dinivin
Re:In Defense of Microsoft...Yes, Microsoft. (Score:3, Insightful)
Re:Same with my car (Score:2, Insightful)
Sure you can. You just have to use VBA rather than hacking the source of the program itself. People have made all kinds of modifications to Word via a robust and well-documented API. I'd argue that's more useful for most people than monkeying around with the source code (which makes the software unsupportable, from a Microsoft point of view -- "Yeah, I've been getting fonky crashes since I tweaked the spell-check algorithm....").
LaTeX! (Score:2, Insightful)
Use LaTeX!
Re:We first need ... (Score:2, Insightful)
What I can't understand is why... Yes for some stuff htm on a server is the way to go, but for most things the company wants you to have a compy 100% of the time. That way if the server goes down one can still read the sexual harrasment policies in the handbook that was e-mailed to everyone.