IE7 Today

[idn]

Was IE7 released in additional languages today? Turkish, Portuguese, etc?

[sarcle]

Was IE7 released in additional languages today? Turkish, Portuguese, etc?

Was it supposed to? I don't think the IE7 team knows what's going on. I haven't read anything about foreign auto-updates for awhile on their blog. http://blogs.msdn.com/ie/

And they certainly didn't announce it there today.

Last thing I read was they had 100 million downloads. But those are to US users. Hardly anything to read on the international front.

I’m pleased to report that on January 8th, we had the 100 millionth IE7 installation. However, even more important than installations is usage. According to WebSideStory (http://www.websidestory.com/) (the company we use to measure browser usage), as of this week, over 25% of all visitors to websites in the US were using IE7, making IE7 the second most used browser after IE6. We expect these numbers to continue to rise as we complete our final localized versions, scale up AU distribution,

Um.. Scale up AU distribution and complete our final localized versions. Okay, can you tell us when that exactly is going to happen?

[idn]

Was it supposed to? I don't think the IE7 team knows what's going on. I haven't read anything about foreign auto-updates for awhile on their blog. http://blogs.msdn.com/ie/

And they certainly didn't announce it there today.

Last thing I read was they had 100 million downloads. But those are to US users. Hardly anything to read on the international front.



Um.. Scale up AU distribution and complete our final localized versions. Okay, can you tell us when that exactly is going to happen?

Did a quick search and this is where I read it. Automatic uptates on Jan 22. for Turkish, Portuguese, Czech, Hungarian, ELL.

http://www.microsoft.com/technet/updatemanagement/windowsupdate/ie7announcement.mspx

[sarcle]

Did a quick search and this is where I read it. Automatic updates on Jan 22. for Turkish, Portuguese, Czech, Hungarian, ELL.

http://www.microsoft.com/technet/updatemanagement/windowsupdate/ie7announcement.mspx

I also read somewhere that Russia was supposed to be on Jan. 1st, but didn't read on their blog anywhere that they achieved this date. Where they said they would announce them when they happen.

From news stories it sounds like MS is having problems in the US with their "welcome to IE7" page when IE7 opens up it crashes. They didn't see a need for a larger server? I have to admit these guy's foresight are simply the kings of idiocracy.

[Rubber Duck]

Did a quick search and this is where I read it. Automatic uptates on Jan 22. for Turkish, Portuguese, Czech, Hungarian, ELL.

http://www.microsoft.com/technet/updatemanagement/windowsupdate/ie7announcement.mspx

Once upon a time, over the White Mountain in a far away land, live a little Prince called Willliam........

[Drewbert]

Checking Google's cache of the page from Jan 17th, added is:

Czech Republic
Hungary
Portugal (note, Portuguese version for Brazil released earlier)
Turkey

[sarcle]

I know we have some natives here from other countries can anyone here from any of these countries verify they have actually recieved an automatic update from Microsoft for IE7?

German, French, Spanish, Finnish, Brazilian Portuguese, Arabic
15-Nov-06
Italian, Dutch, Russian, Sweden, Danish, Norwegian, Polish, Hebrew
1-Jan-07
Turkish, Portuguese, Czech, Hungarian, ELL
22-Jan-07


Would really like to know the uptake in these countries and how fast they are getting it out there. I read that it's currently around 1 million a day in the US.

[Explorer]

Looks like we are moving forward.

http://www.w3schools.com/browsers/browsers_stats.asp

[Rubber Duck]

Looks like we are moving forward.

http://www.w3schools.com/browsers/browsers_stats.asp

Stats are difficult to evaluate and compare. Some would suggest that in the US at least there is one installation in three of Internet Explorer is IE7.

Of course until it is downloaded in our target markets it means nothing.

I think you can be reasonable confident that nothing much has happened in the Far East as yet.

[rhys]

According to Google Analytics for my two top Japanese traffic sites, absolutely 0% are IE7

[Drewbert]

There you go.

Here's another stat. An ASCII site of mine with Chinese content.

4329 visitors from Mainland China using IE6.

Mainland China visitors using IE7 during same period: 49

But that's not uniques. So not too accurate. But let's call it 1%, ballpark.

[touchring]

There you go.

Here's another stat. An ASCII site of mine with Chinese content.

4329 visitors from Mainland China using IE6.

Mainland China visitors using IE7 during same period: 49

But that's not uniques. So not too accurate. But let's call it 1%, ballpark.


1% is very good, most is <0.1%.

According to Google Analytics for my two top Japanese traffic sites, absolutely 0% are IE7


Rhys, btw, what's the % for the FFs?

[domainguru]

My Thai games site has gotten probably 2 IE7 visitors to date from several thousand uniques. And one of those was me.

So to all intents and purposes, IE7 doesn't exist yet in Thailand.

[touchring]

I think we're overly fixated on IE7 when FFs are more significant statistically.

[domainguru]

I think we're overly fixated on IE7 when FFs are more significant statistically.

The *major* problem with Firefox is that it shows .com and .net IDNs as punycode i.e. xn--

That to my mind is *not* an IDN browser. No website visitors want to see xn-- in their browser bar. Imagine the user experience if they click on a nice native language unicode link and arrive at your site and it says xn--d0ej231r.com in the browser bar. Many users will think they have been sent to a phishing site ....

Only when Mozilla / VeriSign can agree on displaying native language domains inside Firefox can Firefox be considered an IDN browser.

And yes, I do realize you can adjust Firefox yourself to show unicode for .com / .net IDNs. But this sort of stuff has to work *out of the box*, not require end users to fiddle with config files ...

[touchring]

The *major* problem with Firefox is that it shows .com and .net IDNs as punycode i.e. xn--

That to my mind is *not* an IDN browser. No website visitors want to see xn-- in their browser bar. Imagine the user experience if they click on a nice native language unicode link and arrive at your site and it says xn--d0ej231r.com in the browser bar. Many users will think they have been sent to a phishing site ....

Only when Mozilla / VeriSign can agree on displaying native language domains inside Firefox can Firefox be considered an IDN browser.

And yes, I do realize you can adjust Firefox yourself to show unicode for .com / .net IDNs. But this sort of stuff has to work *out of the box*, not require end users to fiddle with config files ...


Yes, this change can be done easily - FF evolves very quickly, they will have to patch this phishing loophole.

I often type-in idn to access chinese idn sites, prefer using FF to IE7 because i do not need to swtich keys to enter .com or .cn.

[blastfromthepast]

# re: 100 Million IE7 Installations!
Tuesday, January 23, 2007 7:02 PM by Mike
And on how many of these english language installs have you ignored the user's locale setting and replaced it with English(US).

Although bugged repeatedly through the IE7 and Vista betas, you still set the radio button defaults incorrectly on the runonce page that appears after first launching IE7. It offers the user the choice between the user's current settings (which might be UK, Australia etc) and English(US), but always sets the defaults on the latter. This is buried in the middle of settings for anti-phishing etc and is very easy to overlook.

Why is Microsoft determined to overwrite non-US English settings? It messes up so many website redirects!!

http://blogs.msdn.com/ie/archive/2007/01/12/100-million-ie7-installations.aspx#1517901

[Drewbert]

Fucking morons.

[touchring]

Why is Microsoft determined to overwrite non-US English settings? It messes up so many website redirects!!

http://blogs.msdn.com/ie/archive/2007/01/12/100-million-ie7-installations.aspx#1517901


Come to think of it, a good thing they delay the regional AU rollouts. Just US alone, they can't handle, let alone for unicode. I'll definitely hate to be in the IE7 team, probably one of the worst microsoft product section to be in. :o

[rhys]

1% is very good, most is <0.1%.




Rhys, btw, what's the % for the FFs?

Out of 1119 visits this week - exactly 1 was IE7 (one of you?) and 4 (0.36%) were FF. Pretty small.

[touchring]

Out of 1119 visits this week - exactly 1 was IE7 (one of you?) and 4 (0.36%) were FF. Pretty small.


Hmm, only 0.36% for FF, this is negligible, big upside to come for type-in. :)

Anyone else has FF stats for JP names??