I guess the Y1C issue may kinda be a problem after all....

by Michael S. Kaplan, published on 2011/08/09 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2011/08/09/10193739.aspx

Remember when I blogged About the Y1C problem, which really isn't too much of a problem (except maybe in North Korea)... at the beginning of this year?

Darn, I was hoping you had forgotten about that one.

I take it then that you remember this guy too?

As it turns out, I may have understated the problem, slightly.

You see, there actually is perhaps kind of a Y1C problem after all....

The good news is that the problem is just in the user interface.

The bad news, however, is that the problem is in the user interface.

More good news: the long standing "date window" UI still exists, even for this calendar.

Roughly offset by related bad news: the default date window for this calendar starts with 00 and ends with 99.

But there is some good news! The short date format itself has three 'y' letters in it.

Alas, there is also bad news here: the short date format can be customized.

Maybe someone should do a Y2K-style fixup on this UI, though this issue is more likely to embolden the "switch to Gregorian" folks than inspire user interface changes....

Raymond Chen - MSFT on 9 Aug 2011 7:13 AM:

I always forget about that calendar. I'll find some packaged food, see that it expired TEN YEARS AGO, and then realize "Oh wait, it's using a different calendar."

Cheong on 9 Aug 2011 6:10 PM:

In fact I've also seen Taiwan food have "1" of "100" covering the ":" of expiry date... Just that it doesn't really matter.

go to newer or older post, or back to index or month or day