Open Bug 199229 Opened 21 years ago Updated 2 years ago

Decode ACE encoded international domain names (IDN) for UI


(Core :: Networking, defect, P5)





(Reporter: nhottanscp, Unassigned)


(Depends on 1 open bug, )


(Keywords: intl, Whiteboard: [necko-would-take])

Separated from bug 196717.

nsIIDNService::convertACEtoUTF8 is now implemented. 
ACE encoded string need to be decoded before shown to UI.

nsIIDNService::isACE can be used to check the domain name is ACE encoded.

darin mentioned nsStandardURL needs this
-> me

nhotta: is this required for mozilla 1.4?
Assignee: dougt → darin
The decode is also needed for showing HREF link with raw ACE in status bar.
HREF link may contain raw ACE in order to work with non-IDN browsers.
Summary: Decode ACE encoded international domain names for UI → Decode ACE encoded international domain names (IDN) for UI
Blocks: IDN
Yeah, maybe.  Although I think we definitely want to make nsStandardURL smart
enough to automatically make this conversion as part of its URI normalization
not quite.  in some cases, fixing this bug means that we need to remember to use
the value of nsIURI::host instead of nsIURI::asciiHost.  remember that bug you
fixed for the status bar just recently?  :-)

that said, this bug certainly depends on bug 237819.
Depends on: 237819
This may be fixed (or wontfixed) by bug 320807.
In bug 320807, we stop to use |unEscapeURIForUI| if the string has host name.
Depends on: 320807
Assignee: darin → nobody
QA Contact: benc → networking
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008041001 SeaMonkey/2.0a1pre

"Copy Link Location" on the URL link at top of this bug gives me http://日本語.jp/ which looks "possible" as a decoding result.

Reporter (nshottanscp) and/or Masayuki Nakano (Mozilla Japan), I don't know Japanese, so:
- is the above result the desired one?
- do you still experience this bug on a current build of Firefox 3 or SeaMonkey 2?
If your answers are yes and no (respectively), I suppose this bug could be resolved WORKSFORME.
it's still not possible to send Emails to IDN Domains for expamle example@exä
Whiteboard: [necko-would-take]
Bulk change to priority:
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.