| Su | Mo | Tu | We | Th | Fr | Sa |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 |
Browse archives
|
Untitled
Submitted by reeses on Mon, 2002-02-11 20:15.
I bloody well love Microsoft's solution to this Outlook/Outlook Express bug. Basically, UUENCODE slaps a header on its data consisting of "begin
Apparently, the LookOut MUAs just look for "begin" followed by a space, with a mode, followed by a space, followed by a filename, in email attachments. The mode and filename are optional parms, so "begin" followed by two spaces is a legal construct. So, what do you think would happen if you put, say, the word "begin" at the beginning of a line in an email to a person using Outlook? Yup, Outlook would think it was an attachment, be unable to UUDECODE it, and leave it blank. We all write bugs, so this isn't a big deal in and of itself. The hilarious and ludicrous part is MSFT's solution to the problem: To workaround this problem:
I can see it now: From: Wage Slave Sir, I'd like to Begin to talk about a salary increase, based on my attention to detail and professional presentation. Thank you. Wage From: Big Boss Mr. Slave, If you can't be bothered to capitalize the correct words in a sentence, how can you be expected to help us capitalize on our good name in the industry? Not only are you not going to receive an increase in compensation, a copy of your grammatically incorrect email will be placed in your permanent personnel file. Love, Big With this one bug, and the inane workaround, MSFT will usher in a new dark age, an economic depression, a new era of illiteracy, as children expect to see this quasi-germanic capitalization as acceptable. Capitalonics! Post new comment |
SearchSimilar entriesUser login |