Sorting it all Out Michael Kaplan's random stuff of dubious value Be sure to read the disclaimer here first!
The bug report:
STEPS:1. Create a custom list in SharePoint2. Click List tab...Create Column...Date and Time3. Give the field a name and click ok to create the column4. Add a new item to the list5. For the date field, choose Feb 17, 2011
EXPECTED RESULT:Date is displayed with Hebrew new year: י"ג אדר א תשע"א
ACTUAL RESULT:Date is displayed without Hebrew new year: י״ג אדר תשע"א
Sound familiar?
Think back.
The year was 2008.
The month was April.
The Blog was Sorting it all Out.
The blog was I Adar you! Hell, I Double Adar you!.
The bug clearly still repros.
One funny twist on the story....
Not funny ha-ha, but funny ironic, kinda.
My Blog, or to be specific that Adar blog, was referenced in the "won't fix" resolution:
Also we learned Michael Kaplan already has a blog regarding this issue which will help people understand Windows behavior.
I suppose I should be flattered....
Honestly, it almost makes me want to change my writing style to be more severe about bugs, and less willing to try to be entertaining if blogs in my Blog are cited in the justification to not fix a bug!
Sigh.
I suppose I should just let it go.
Because there's more!
I can't tell you yet, but almost.
Stay tuned....
In general, customers don't want vendors to get them to "understand the vendor's behavior": they want the vendor to understand their behavior, and *@#$ well implement it. Whoever wrote the resolution sounds way too much like the Secretary in Brecht's poem "The Solution" (1953), tr. Willett and Manheim:
After the uprising of the 17th of June
The Secretary of the Writers Union
Had leaflets distributed in the Stalinallee
Stating that the people
Had forfeited the confidence of the government
And could win it back only
By redoubled efforts. Would it not be easier
In that case for the government
To dissolve the people
And elect another?
By the way, I am now convinced that the blogs.msdn.com server times how long it has been since it sent me the page I'm trying to comment on, and if it's more than about a minute, the posting is silently rejected. Perhaps this is an effort to prevent commenters from overthinking?
So I now write my comment taking as long as I want, copy it to the clipboard, hit Post knowing that it will take me straight back to the same page while ignoring my comment, paste the comment back in, add my name, and hit Post again.
I wrote this one quickly (unlike the previous one), so let's see if it makes it within the deadline. But I'm copying it too, just to be sure....
Yup, that was fast enough.
@John: It's a known bug (probably session timeout related or something stupid) - Raymond Chen got the complaints the worst I think, but it's quieted down . It sucks for me since I tend to open tabs in the background and look at them when I have time.
@John: Yeah this is a known problem with the blogging software they use. Copy your text, then refresh the page before you post is the most reliable way. (If it worked you get the #comment posted anchor in the URL and the green box above the comments on most of the blogs)