The interesting point here is that TCC is compatible with Windows, and CMD isn't. TCC uses the Windows GetDateFormat API to display the date in the default locale format; CMD uses its own formatting (i.e., not what the locale or the user specified). Is that a good thing?My take, for whatever it's worth: %DATE% exists only for compatibility with CMD.EXE batch files — it's otherwise pointless and redundant — so it makes sense that it should emulate CMD.EXE as closely as possible, even to the leading zero. DATE /T is more a convenience for interactive use at the prompt, so there's far less need for it to exactly match CMD.EXE's behavior. I think the present, leading-zero-suppressed format is more esthetically pleasing; but of course others might disagree about that.
CMD.EXE is weird. It looks as if it's using DATE_SHORTDATE and then somehow misinterpreting the format string. MM gives a two-digit month as specified. M also gives a two-digit month, but causes the day of the week to be prepended. I don't know how Microsoft managed that....CMD uses its own formatting (i.e., not what the locale or the user specified). Is that a good thing?