Closed
Bug 42899
(iri)
Opened 25 years ago
Closed 7 years ago
IRI support (RFC 3987)
Categories
(Core :: Internationalization, enhancement, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 906714
Future
People
(Reporter: bobj, Assigned: smontagu)
References
(Depends on 3 open bugs, Blocks 1 open bug, )
Details
Putting this on the radar.
INTERNET-DRAFT:
Internationalized Uniform Resource Identifiers (IURI)
http://www.ietf.org/internet-drafts/draft-masinter-url-i18n-05.txt
See also W3C Internationalization - URIs and other identifiers
http://www.w3.org/International/O-URL-and-ident.html
See also bug 42898: iDNS support
What happens now if I type a non-ASCII URL in the location bar?
What should we do?
IE5 has a preference under Advanced tab of the menu Tools|Internet Options...:
[ ] Always send URLS as UTF-8
Comment 3•25 years ago
|
||
why don't you try it ?
See bug 43852 "Send URLs as UTF-8" not working.
Probably need to link these either with depend or dup.
Internationalized Resource Identifiers (IRI), April 17, 2002
http://www.w3.org/International/2002/draft-w3c-i18n-iri-00.txt
This draft replaces draft-masinter-url-i18n-08.txt.
Due to a series of misunderstandings, this draft was earlier announced
as draft-w3c-i18n-iri-00.txt, and has also been published as
draft-duerst-i18n-iri-00.txt. This draft replaces
draft-masinter-url-i18n-08.txt. Please send comments to
www-i18n-comments@w3.org.
Updated URL:
http://www.ietf.org/internet-drafts/draft-duerst-iri-00.txt
Comment 8•21 years ago
|
||
It is unclear to me what this bug is requesting.
Assignee: ftang → smontagu
Status: ASSIGNED → NEW
QA Contact: teruko → amyy
Summary: IURI support → IRI support
Comment 9•20 years ago
|
||
IRIs are now last call:
<http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg00383.html>
At may be the case that Mozilla already supports (most of) the functionality
defined in that draft, but I haven't tested it thoroughly yet.
Severity: normal → enhancement
Updated•20 years ago
|
Alias: iri
Assignee | ||
Comment 10•20 years ago
|
||
(In reply to comment #8)
> It is unclear to me what this bug is requesting.
Me too, so let's make it into a tracking bug.
Updated•20 years ago
|
Assignee | ||
Updated•20 years ago
|
Summary: IRI support → IRI support (RFC 3987)
Comment 11•18 years ago
|
||
Does Firefox transmit the path part of the IRI in UTF-8 as RFC 3987 suggests?
It does not seem to.
Try http://hapax.qc.ca/Recettes/Noël.html
Firefox producest http://hapax.qc.ca/Recettes/No%EBl.html, which codes the path as Latin-1, while my server codes the resource as UTF-8 (http://hapax.qc.ca/Recettes/No%C3%ABl.html),,,
If an option exists in Firefox to sent the path in UTF-8, where is it? I could not find it.
Comment 12•18 years ago
|
||
Additional info: this problem (sending the filename's path in Latin-1) happens when I key in "Noël.html" in the address field, even if the current page's encoding is UTF-8.
It does not happen, when you click on a link like this one http://hapax.qc.ca/Recettes/Noël.html from within a page, it that case the path part is properly encoded in UTF-8.
Comment 13•18 years ago
|
||
To exemplify the problem (which occurs also within HTML pages) :
I created two HTML pages pointing to http://hapax.qc.ca/Recettes/Noël.html.
Both links look similar :
<a href="http://hapax.qc.ca/Recettes/Noël.html">Noël is here</a>
But as you will see the page written in Latin-1 will fail to reach http://hapax.qc.ca/Recettes/No%C3%ABl.html, but not the one in UTF-8.
http://hapax.qc.ca/Recettes/LinktoNoelLatin-1.html
http://hapax.qc.ca/Recettes/LinktoNoelUTF-8.html
In other words, the current page's encoding determines the way the resource path is encoded, I believe this is very annoying, the server has no way of knowing what encoding was chosen, and this is what RFC 3987 averts (all paths are encoded in UTF-8 as a "broker" encoding).
I would like RFC 3987 to be implemented at the very least as an option set by the user (preferably as a default but they may be some resistance here).
Assignee | ||
Comment 14•18 years ago
|
||
(In reply to comment #11)
> If an option exists in Firefox to sent the path in UTF-8, where is it? I could
> not find it.
Set network.standard-url.encode-utf8 to "true" in about:config. See bug 284474 for why this is not the default.
Comment 15•18 years ago
|
||
Thank you very much, I was looking precisely for this.
I wish there would be a less cryptic of setting this parameter
But doesn't this contradict RFC 3987?
Also one of the examples given to justify this default works perfectly (since then?) with UTF-8 encoded URLs (as well as the Latin-1). I left a comment to that effect.
I will follow answers on bug 284474. Thanks again.
Updated•15 years ago
|
QA Contact: amyy → i18n
Updated•15 years ago
|
Flags: wanted-fennec1.0?
Updated•15 years ago
|
Flags: wanted-fennec1.0?
Comment 16•15 years ago
|
||
[my apology for the accidental wanted- request: not sure how that happened.]
Comment 17•7 years ago
|
||
Duping this against bug 906714, which is our actual target for URLs these days.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•