by Michael S. Kaplan, published on 2007/08/15 03:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2007/08/15/4396922.aspx
Wherever John Bonham is, I doubt he'd be very happy about this.
Regular readers may remember my post from almost two years ago entitled Is Excel CSV misusing NLS functionality? that explains how Excel's CSV import functionality depends on the LOCALE_SLIST setting from Regional and Language Options.
I still think the design there is bad, but it is easy enough to work around, so I am able to get over my outrage quickly enough when I remember it again....
Then the other day the email I received via the Contact link was:
We created a Macro used to Save a workbook in .csv format.
In Regional Setting we changed our list separator as ~. But when we run Macro we are still getting output as comma separated not ~ separated. What's going on
Ordinarily the lack of consistency between input and output would bother me, though in this case since I didn't care for the original design, I have to admit that it is not something I am terribly eager to see people try hard to make consistency work.
Though jokes aside, this looks like more of a difference in the "convert via UI" vs. "convert programatically" more than anything else. Which in its own way makes the weirdness kind of appealing to me in a strange way....
This post brought to you by ឿ (U+17bf, a.k.a. KHMER VOWEL SIGN YA)
# Robert L. on 17 Aug 2007 10:27 AM:
If the IN technique is based on Regional Options but the OUT technique is not and someone is asking about the OUT then wouldn't that be "No 'out through the IN door' ?
# Michael S. Kaplan on 17 Aug 2007 10:36 AM:
Good point Robert -- yes, you are correct, but I was worried no one would get the reference (I was already worried enough to add Led Zeppelin to the title!).
go to newer or older post, or back to index or month or day