by Michael S. Kaplan, published on 2013/10/16 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2013/10/16/10456308.aspx
It was just a few years ago, when IE9 was out there, that I pointed out how ECMA added i18n support to ECMAScript (just seven years too late!).
I pointed out that I was cynical about changes being made here.
And it was just a few days ago that friend and colleague Mihai Nita pointed out in a comment to that blog that
Good news: it is in IE 11 :-)
I think they are perhaps updating Internet Explorer too often for my tastes, but there is no rule about them sticking to operating system versions, so I guess it does not matter. It just means that they will have to deal with the "Do we have a version 13?" sooner than we will. 😏😏
They are more standards conscious then they used to be, even if they are helping to push standards forward like with the brackets in Bidi work in Unicode 6.3, previously mentioned here.
We finally got the support we wanted in
JavaECMAScript, where both client and server can take advantage of the functionality. 😏
Anubhav Chattoraj on 16 Oct 2013 9:21 AM:
Not about this post, but I've been trying to leave a comment on the chained dead keys post from a few days ago and my comment just never appears.
Checking if I can comment on other posts.
go to newer or older post, or back to index or month or day