Closed
Bug 242068
Opened 21 years ago
Closed 17 years ago
Chatzilla does not resolve non-ascii characters correctly in the URL.
Categories
(Other Applications :: ChatZilla, defect)
Other Applications
ChatZilla
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rebtun, Assigned: Gijs)
References
Details
(Whiteboard: [cz-charset][cz-0.9.81])
Attachments
(1 file, 1 obsolete file)
8.67 KB,
patch
|
bugzilla-mozilla-20000923
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Im not able to use ÆØÅæøå in channel names.
If i join a channel in chatzilla it shows the correct name of the channel , but
i always get this type of URL
irc://irc.homelien.no/osteh%c3%b8vel
When it should be
irc://irc.homelien.no/ostehøvel
Other people cant invite you to their channels eighter if they have ø,æ or å in
them.
Reproducible: Always
Steps to Reproduce:
1. After installing latest chatzilla client 0.9.63a i type
irc://irc.homelien.no/ostehøvel.In the Firefox browser URL box.
This error is consistent in the previous releases of chatzilla also.
2. Sent invite from mIRC #ostehøvel to my chatzilla user and I dont join the
correct channel when i accept the invite.
Actual Results:
result of 1st step: This will make you join a channel , but not the correct one,
though the display name inside the irc client is correct. URL is wrong it shows
instead irc://irc.homelien.no/osteh%c3%b8vel
result of 2nd step: You join this channel instead #ostehøvel URL is also wrong
it shows irc://irc.homelien.no/osteh%c3%83%c2%b8vel
Expected Results:
The software should have been able to resolve the ÅØÆåøæ into the correct
channel names.
This bugg seems to be consistent through out all settings and themes.
This error renders the chatzilla extension to firefox unusable for many users.
Updated•21 years ago
|
Component: Extension/Theme Manager → ChatZilla
Product: Firefox → Browser
Version: unspecified → Trunk
Updated•21 years ago
|
Assignee: bugs → rginda
QA Contact: bugs → samuel
Comment 1•21 years ago
|
||
The URL irc://irc.homelien.no/osteh%c3%b8vel is correct. URLs cannot contain the
characters in the channel name, and get escaped based on the UTF-8 representation.
By default ChatZilla sends channel names using the UTF-8 encoding. If the server
you are using does *not* use UTF-8 you *will* need to tell ChatZilla this. It is
impossible for ChatZilla to guess.
I do seem to be having problems joining the channels, though. I will have a look
at this.
Updated•20 years ago
|
Product: Core → Other Applications
WILL NOT ALLOW DOWNLOAD OF VIAVOICE
Attachment #179510 -
Flags: superreview-
Attachment #179510 -
Flags: review-
Attachment #179510 -
Flags: approval1.7.7?
Attachment #179510 -
Flags: approval-l10n?
Attachment #179510 -
Flags: approval-aviary1.0.3?
Comment on attachment 179510 [details]
NOT A WIN32 APPLICATION
I don't see what the point of an approval request for a screenshot is.
Attachment #179510 -
Attachment mime type: image/x-bmp → image/bmp
Attachment #179510 -
Flags: approval1.7.7?
Attachment #179510 -
Flags: approval1.7.7-
Attachment #179510 -
Flags: approval-l10n?
Attachment #179510 -
Flags: approval-l10n-
Attachment #179510 -
Flags: approval-aviary1.0.3?
Attachment #179510 -
Flags: approval-aviary1.0.3-
Updated•20 years ago
|
Attachment #179510 -
Attachment is obsolete: true
Attachment #179510 -
Flags: superreview-
Attachment #179510 -
Flags: review-
Updated•19 years ago
|
OS: Windows XP → All
Hardware: PC → All
Comment 4•19 years ago
|
||
Isn't this just a charset issue? Since you're most likely dealing with mirc users, change the network/server charset to whatever they're using and it should work.
Comment 5•19 years ago
|
||
There is a bit more to it than charsets; when we get an invite, we MUST be able to join the correct channel for the invite, even if we're in the wrong charset (which will mean we display the channel name incorrectly, but nothing more).
Whiteboard: [cz-charset]
Comment 6•18 years ago
|
||
Changing to confirmed, based on comments there's enough to say theres an issue.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Chatzilla does not resolve ØÆÅøæå correctly in the URL. → Chatzilla does not resolve ������ correctly in the URL.
Updated•17 years ago
|
Summary: Chatzilla does not resolve ������ correctly in the URL. → Chatzilla does not resolve non-ascii characters correctly in the URL.
Assignee | ||
Comment 8•17 years ago
|
||
This fixes invite URLs. It does a couple of things:
- Use inline buttons to get a full URL instead of just a channel name (which would always be incomplete info, which means we lose if we don't have the correct charset)
- make cmdJoin work if you give it a channel object to join, using only the encodedName for sending stuff to the server, which then means things Just Work.
- make x-cz-command properly escape things (unescape from the x-cz-command URL, then js toSource so it evaluates to a string which is passed to view.dispatch, then escape so it's a javascript: URI)
- make gotoIRCURL use the object variant of /join
We should probably make /query do the same as join, though that's less of a priority as most servers will prevent people from having non-ascii nicks.
Then, as Silver suggested on IRC, we need a general audit of usage of unicodeName where we should really be using the methods on objects or encodedName instead, so we keep the correct references.
Assignee: rginda → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Attachment #302357 -
Flags: review?(silver)
Comment 9•17 years ago
|
||
Comment on attachment 302357 [details] [diff] [review]
Patch
>+ var commandStr = decodeURI(ary[1]).toSource();
Please use .quote() here, as discussed on IRC.
>+ var jsStr = "void(view.dispatch(" + commandStr + ", null, true))";
>+ var jsURI = "javascript:" + encodeURI(jsStr)
Nit: missing semi-colon.
Attachment #302357 -
Flags: review?(silver) → review+
Assignee | ||
Comment 10•17 years ago
|
||
(In reply to comment #8)
> Then, as Silver suggested on IRC, we need a general audit of usage of
> unicodeName where we should really be using the methods on objects or
> encodedName instead, so we keep the correct references.
>
I filed bug 416966 for this issue.
Assignee | ||
Comment 11•17 years ago
|
||
And this is now checked in, so, FIXED. :-)
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: [cz-charset] → [cz-charset][cz-0.9.81]
You need to log in
before you can comment on or make changes to this bug.
Description
•