Sorting it all Out Michael Kaplan's random stuff of dubious value Be sure to read the disclaimer here first!
Please read the disclaimer; content of Michael Kaplan's blog not approved by Microsoft!
Everybody hates Microsoft.
Well, not everybody.
But hating Microsoft seems awfully popular....
It seems like to try to be the best at anything you have to make choices that lots of people won't like. And then before you know it, people are hating you.
Everyone hates what Microsoft does with the BOM (Byte Order Mark). That thing I talked about in Every character has a story #4: U+feff (alternate title: UTF-8 is the BOM, dude!).
Lots of people hate it so much that they will complain about it when it is not completely on topic, like in that other post (unicodeFFFE... is Microsoft off its rocker?).
But I feel I must ask one question.
Why are people writing their UNIX Shell scripts in Notepad such that the issue of Notepad saving the BOM in UTF-8 is such an issue?
I mean, people who are writing UNIX shell scripts are not guaranteed to be among the Microsoft haters, but all things be equal they are probably more likely to be than the people who pay their own fees to go to TechEd or PDC.
So why are they writing their UNIX shell scripts in Windows Notepad, exactly?
I'd just like it if someone could explain this one. It just makes no sense to me....
This post brought to you by U+fffe, a permanently reserved code unit in Unicode so that BOM determination can remain easier....
I don't have to answer every point because it is a 10-year-old argument that you have lost. :-)
See the latest blog put there today. It is time to move on.
AND STOP USING NOTEPAD.
I do not understand why anyone would use an application with so many potential replacements that they believe has been broken for 10 years.
It IS the right solution....just not for you.
Move on. Please....
Wow, someone really messed up when they decided to have Notepad add a BOM to the beginning of a file...
Notepad should be phased out of windows
(Excuse the Shaggy reference!) It wasn't me. Well, this time it wasn't me. I mean, yes, it was me in