French PPC

[Rubber Duck]

Originally Posted by jacksonm

What is the version number of the Japanese version you installed?

Look at the configuration like this:

1. in the address bar, type about:config <enter>

2. in the filter bar, type idn <enter>

network.enableIDN should be set to "true"
network.IDN_show_punycode should be set to "false"

You should also see a bunch of entries which start with:

network.IDN.whitelist.*



They really could choose to make this easier for users... Maybe we should write them a letter :-)

.

It can get more complicated to follow in the Japanse Version.

This Version is showing both of the above options as True by default.

Version is 2.0.0.3

[jacksonm]

Originally Posted by Rubber Duck

It can get more complicated to follow in the Japanse Version.

This Version is showing both of the above options as True by default.

Version is 2.0.0.3

That's the problem then. Punycode is the default for everything. It might actually be the same in the english version of FF, I don't remember what all I changed to get it to work anymore.

Double-click on "network.IDN_show_punycode" and it will change to false. Alternatively, right-click and choose "toggle".

.

[Rubber Duck]

Originally Posted by jacksonm

That's the problem then. Punycode is the default for everything. It might actually be the same in the english version of FF, I don't remember what all I changed to get it to work anymore.

Double-click on "network.IDN_show_punycode" and it will change to false. Alternatively, right-click and choose "toggle".

.

I don't think it is the default for everything in the English Version. I believe you can add dot com and dot net to your White list as well.

Clearly, there would be a strong argument for allowing all of these extensions in Asian language versions as the arguments that apply for putting a block on dot com are grossly outweighed by the disavantages in the Asian context. They clearly have the capacity to tweak different downloads in different ways. The question remains, why the f*ck don't they put their logical heads on and allow the Chinese and Japanese to download something that will work for them, before they all end up with a castrated version? I always though computer people were supposed to be strong on logic?

[jacksonm]

Originally Posted by Rubber Duck

I don't think it is the default for everything in the English Version. I believe you can add dot com and dot net to your White list as well.

network.IDN_show_punycode set to "true" cancels all whitelisted extensions.

Originally Posted by Rubber Duck

Clearly, there would be a strong argument for allowing all of these extensions in Asian language versions as the arguments that apply for putting a block on dot com are grossly outweighed by the disavantages in the Asian context. They clearly have the capacity to tweak different downloads in different ways. The question remains, why the f*ck don't they put their logical heads on and allow the Chinese and Japanese to download something that will work for them, before they all end up with a castrated version? I always though computer people were supposed to be strong on logic?

Mozilla is a big, bureaucratic organization. Complete with product managers, project managers, release managers, security managers, managers of managers, etc. They are very clearly geared toward the US market, but don't mind including the international users when counting market share...

.

[Olney]

It might be a bad download.
All of the Japanese computers at work view my jps fine in unicode usually.
But anyway only people in IT in Japan use Firefox, there's no big push for other browsers over here...

If it's Mac they use Safari, if it's PC it's IE...

[jacksonm]

Originally Posted by Olney

It might be a bad download.
All of the Japanese computers at work view my jps fine in unicode usually.
But anyway only people in IT in Japan use Firefox, there's no big push for other browsers over here...

If it's Mac they use Safari, if it's PC it's IE...

http://himazuj.blogspot.com/2006/03/...-in-japan.html


It's a year old, but probably still relevant.

.

[Rubber Duck]

Originally Posted by jacksonm

network.IDN_show_punycode set to "true" cancels all whitelisted extensions.

Mozilla is a big, bureaucratic organization. Complete with product managers, project managers, release managers, security managers, managers of managers, etc. They are very clearly geared toward the US market, but don't mind including the international users when counting market share...

.

Which is somewhat bizzare as there are at least twice as many non-English speaking Firefox Users in Europe as there are English Speaking ones in the US.

Still it true what they say: "If you can't make it here, you cannot make it anywhere."

Still it doesn't stop GM trying to chance their arm in China. Like that is ever going to work

[domainguru]

Originally Posted by Rubber Duck

It can get more complicated to follow in the Japanse Version.

This Version is showing both of the above options as True by default.

Version is 2.0.0.3

I think you will find all versions on one PC share the same settings....

The situation is pretty clear. VeriSign have not published an "IDN security document" on their registry website, so Mozilla refuse to whitelist .net and .com domains in Firefox.

Until they come to an agreement, I don't even regard Firefox as an IDN-compatible browser. You can't be scaring off your users by displaying xn-- in the browser bar. They will think they have been hacked or something !!

[Olney]

I have one IDN Domain that webmasters use daily... The percentage of FireFox use is at 24%
It's rare & the other domains are all about 1% & this is looking at one month of traffic.

[Rubber Duck]

Yes, the whole thing comes back to who is responsible for regulating Versign as a Registry, ICANN or Mozilla. I would have thought the answer was obvious, but apparently not.

Originally Posted by domainguru

I think you will find all versions on one PC share the same settings....

The situation is pretty clear. VeriSign have not published an "IDN security document" on their registry website, so Mozilla refuse to whitelist .net and .com domains in Firefox.

Until they come to an agreement, I don't even regard Firefox as an IDN-compatible browser. You can't be scaring off your users by displaying xn-- in the browser bar. They will think they have been hacked or something !!

[thegenius1]

Dot JP always showed the unicode in the addy bar , and im using a english os and never changed anything in the FF settings.

[Alphamale]

Originally Posted by thegenius1

Dot JP always showed the unicode in the addy bar , and im using a english os and never changed anything in the FF settings.

yup, thats because JPRS have submitted to Mozilla's whitelist.

[Rubber Duck]

Originally Posted by domainguru

I think you will find all versions on one PC share the same settings....!

I never attempted to have multiple versions. I did an uninstall from English, then load Japanese, and then uninstalled the Japanese before downloading the latest version of English .

[jacksonm]

Originally Posted by Rubber Duck

I never attempted to have multiple versions. I did an uninstall from English, then load Japanese, and then uninstalled the Japanese before downloading the latest version of English .

Yes, but the prefs.js (mozilla prefs) file from your previous install is stored in your profile and that is not removed when you uninstall software. It was probably created from an older version which had punycode disabled by default, and didn't get automatically changed after you started the new version.

.

Originally Posted by Alphamale

yup, thats because JPRS have submitted to Mozilla's whitelist.

Basically, the Mozilla policy is that if a registry allows non-natural mixed-script registrations, then they are not whitelisted.

.

[domainguru]

Originally Posted by Rubber Duck

I never attempted to have multiple versions. I did an uninstall from English, then load Japanese, and then uninstalled the Japanese before downloading the latest version of English .

I think its very easy to get confused with various installations / de-installations. I have gotten confused myself thinking the .com was being whitelisted automagically when it wasn't.

The bare facts are the VeriSign registry is not complying with Mozilla's requirements for .com / .net. You can read which registries are compliant here:

http://www.mozilla.org/projects/secu...licy-list.html

So it really shouldn't matter which version of Firefox you download or from where. The default on a fresh machine is that .com and .net will show as punycode. .jp and others will show properly in unicode.

[Rubber Duck]

Originally Posted by jacksonm

Yes, but the prefs.js (mozilla prefs) file from your previous install is stored in your profile and that is not removed when you uninstall software. It was probably created from an older version which had punycode disabled by default, and didn't get automatically changed after you started the new version.

.




Basically, the Mozilla policy is that if a registry allows non-natural mixed-script registrations, then they are not whitelisted.

.

Well that figures.

It looks like you need to be a nuclear physists to optimise Firefox!

On the second point I find it bizarre that people critisize ICANN for over-stepping this remit and then accept that from Mozilla.

It is not Mozilla's place to decide what can and cannot be registered. They are only jumping on the back of work ICANN has done anyway. Verisign has always complied with ICANN policy. It is just now that Mozilla wants a lot of pre-existing domains deleted without intruction from ICANN which is possibly not within Verisign's contractual remit to carryout even if they bloody wanted to. It is a bit like having the engine driver dictacting how the track signalling is installed.

[domainguru]

Originally Posted by Rubber Duck

Well that figures.

It looks like you need to be a nuclear physists to optimise Firefox!

which is exactly why I've written it off as being "IDN compliant" - for .com and .net at least. No problem for me because no Thais really use Firefox anyway.

[thegenius1]

Originally Posted by Rubber Duck

Well that figures.

It looks like you need to be a nuclear physists to optimise Firefox!

LOL , if you are installing different versions and what not , but straight out the package it resolves unicode for .jp

Can somebody link me to a good screen shot software that is free tia ?

[jacksonm]