Closed
Bug 519151
Opened 16 years ago
Closed 14 years ago
Ñ is displayed as punycode for Philippine domains (.ph)
Categories
(Core Graveyard :: Networking: Domain Lists, defect)
Core Graveyard
Networking: Domain Lists
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: renrengabas, Unassigned)
Details
(Whiteboard: [CLOSEME 2011-1-1])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 GTB5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 GTB5 (.NET CLR 3.5.30729)
The Filipino alphabet contains 28 letters, 26 of them are from the English alphabet with an additional 2 letters: ng and ñ. For orthographic purposes, NG is treated as two letters, but Ñ needs to be addressed properly.
Reproducible: Always
Steps to Reproduce:
1. Go to http://www.parañaque.gov.ph/
Actual Results:
http://www.xn--paraaque-g3a.gov.ph/
Expected Results:
http://www.parañaque.gov.ph/
Reporter | ||
Comment 1•16 years ago
|
||
IDN displays properly on Opera 10, but not on IE 8.
Comment 2•16 years ago
|
||
.ph is not in the list at <http://www.mozilla.org/projects/security/tld-idn-policy-list.html>, which is the whitelist that Mozilla uses to decide which TLD's are safe to use (which don't present spoofing vulnerability)
- dotPH doesn't support IDN in domainnames
- gov.ph might be different, but the whitelist is only for the TLD (.ph)
Note: http://www.parañaque.gov.ph/ doesn't seem to be accessible outside of the Philippines.
Reporter | ||
Comment 3•16 years ago
|
||
I think this is a chicken-and-egg problem. If no browser will display Philippine IDN's properly, then dotPH will not support it. Economically, dotPH have no business case for supporting IDNs.
Culturally, Filipinos are losing a lot when they replace ñ with a simple n.
Should we, Filipinos, simply wait for dotPH to request IDN support for Mozilla?
Comment 4•16 years ago
|
||
I have contacts at dotPH. Let me contact them to see what their stance is wrt IDN.
Comment 5•15 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.
Whiteboard: [CLOSEME 2011-1-1]
Updated•15 years ago
|
Component: General → Networking: Domain Lists
Product: Firefox → Core
QA Contact: general → networking.domain-lists
Comment 6•15 years ago
|
||
Adding Regnard, Mozilla Philippines community lead.
Comment 7•14 years ago
|
||
The way to get this supported is for the .ph registry to officially request inclusion in the list, as documented here:
http://www.mozilla.org/projects/security/tld-idn-policy-list.html
Gerv
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Comment 8•14 years ago
|
||
Let me ping the dotPH guys once more.
Comment 9•14 years ago
|
||
I spoke with Joel Disini of DotPH and he said:
"there is no support for ñ here, and unless there is a sudden demand
for this, I do not see it happening soon. The local languages (eg Tagalog,
Bisaya, etc) do not use ñ, only proper nouns of Spanish origin do."
So no Ñ for .ph domains until there is demand for it.
Updated•1 year ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•