Firefox 2.0 Launched.

[Rubber Duck]

Yes it is out Today!

http://news.bbc.co.uk/2/hi/technology/6078016.stm

but not at Mozilla:

http://www.mozilla.com/en-US/

[Wot]

Ah the Beeb - the news before it happens. :)

[Ben]

It was actually uploaded to the FTPs yesterday.

[OldIDNer]

I assume the foreign language versions of FF will not be supporting native character resolution of IDN.com.

[Rubber Duck]

I assume the foreign language versions of FF will not be supporting native character resolution of IDN.com.

No idea, but in the short-term it is likely to have little impact. Uptake of previous version in Asia was negligible.

Do we know what languages are going to be supported?

[OldIDNer]

Here is a list of release candidate languages:

http://www.mozilla.org/projects/bonecho/all-rc.html

[Rubber Duck]

Here is a list of release candidate languages:

http://www.mozilla.org/projects/bonecho/all-rc.html


That is quite impressive and although there is no Hindi the fact that they have already done Gujarati for the RC3 is very encouraging indeed. Would suggest an underlying commitment to do the other Indian Scripts.

The other mission critical languages are all there.

[OldIDNer]

Here is their IDN TLD whitelist:

http://www.mozilla.org/projects/security/tld-idn-policy-list.html

[Rubber Duck]

Firefox to launch a 17:00 PST.

36 Languages are available at launch.

http://news.bbc.co.uk/2/hi/technology/default.stm

[Olney]

Now I understandd why dot jps & cns always show Punycode & dot com, net, cc, & TV don't in FireFox. Good Post this had me puzzled. I think some search engines have adapted some of this into their algorythms.

Here is their IDN TLD whitelist:

http://www.mozilla.org/projects/security/tld-idn-policy-list.html

[Rubber Duck]

Verisign's policy is to implement ICANN's policy. Why is that not acceptable?

Are Mozilla playing politics here?

It would strike me to do it this way is to ensure that IE7 will become de facto standard, as FF will be no use to anyone.

Now I understandd why dot jps & cns always show Punycode & dot com, net, cc, & TV don't in FireFox. Good Post this had me puzzled. I think some search engines have adapted some of this into their algorythms.

Interesting indeed, but the guy who wrote this commentary obviously doesn't understand English very well or the following statements would not have been possible:

* It is based on simple and non-political principles.

*It is based on a much more thorough analysis of the problem than the earlier ICANN proposals, and builds on the experience of the Unicode community, and the earlier analysis of the spoofing problem for the CJK languages performed for RFC 3743. For example, simple script restrictions alone, as per ICANN, do not solve the problem -- there are plenty of subtle homographs in the Latin alphabet.

*It does not treat IDNs as second-class citizens.

*And, most of all, it uses human, and not technical, means to provide a chain of trust from the registry to the application to the user.

[jose]

Opps...

" No, we have. Not. Released. Firefox. 2. Yet. "

http://weblogs.mozillazine.org/preed/2006/10/the_antirelease.html

That's why the mozilla page was not updated.
But it will be released soon, I've learned.

[Rubber Duck]

Nine and Half hours from Now, I understand in 36 Languages and everything bar dot com and net will resolve properly. :mad:


Opps...

" No, we have. Not. Released. Firefox. 2. Yet. "

http://weblogs.mozillazine.org/preed/2006/10/the_antirelease.html

That's why the mozilla page was not updated.
But it will be released soon, I've learned.

[jose]

Excuse me?! :S

[Ben]

Microsoft sends congratulation cake to Mozilla:
http://static.flickr.com/118/278562314_14716c0232.jpg

[TrafficDomainer]

At first I thought it was strange that Firefox 2.0 is available in Punjabi and Gujrati for Indic scripts but not Hindi since Hindi is more widely used. I read up a bit about how they work and found out that languages are only available where they were volunteers to put things together. I suppose they got no help from a qualified Hindi expert with their international project.


QUOTE=Rubber Duck]That is quite impressive and although there is no Hindi the fact that they have already done Gujarati for the RC3 is very encouraging indeed. Would suggest an underlying commitment to do the other Indian Scripts.

The other mission critical languages are all there.[/QUOTE]

[alex]

Microsoft sends congratulation cake to Mozilla:
http://static.flickr.com/118/278562314_14716c0232.jpg

Where's our IDN cake? :)

[rofsjan]

Firefox 2 had about 30 downloads per second

http://browserden.co.uk/blog/2006/10/28/firefox-2-30-downloads-per-second/

[Rubber Duck]

Firefox 2 had about 30 downloads per second

http://browserden.co.uk/blog/2006/10/28/firefox-2-30-downloads-per-second/

Thanks for that! Hopefully it will be enought to motivate the IE team to greater and better things.

None of this actually means anything unless they can reach out to Hinterland of Asia. I somehow doubt that is happening.

[alpha]

I assume the foreign language versions of FF will not be supporting native character resolution of IDN.com.

Gran Paradiso Alpha 2 has been released, it looks like it's the final version of what will become Firefox 3.0

yours truly tested it, and yes you guessed, they are still using the same lame whitelist technology for IDN, so your idn.com will still show as punycode :mad:

[domainguru]

Gran Paradiso Alpha 2 has been released, it looks like it's the final version of what will become Firefox 3.0

yours truly tested it, and yes you guessed, they are still using the same lame whitelist technology for IDN, so your idn.com will still show as punycode :mad:

I've been using the Firefox 3 alpha for six months now, been very stable. The IDN thing is a policy decision, not technical, and I don't expect the policy to change any time soon.

Nobody in Thailand uses Firefox because it doesn't know how to "break" Thai sentences (no spaces between words in Thai language), so web sites look horrible with text not wrapping properly and running off to the right all the time. So in terms of how Firefox treat IDNs, I'm really "not bovvered" :)