Bug 507831
Summary: | unable to change encoding for ftp | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stas Sergeev <stsp2> | ||||||
Component: | firefox | Assignee: | Gecko Maintainer <gecko-bugs-nobody> | ||||||
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 11 | CC: | gecko-bugs-nobody, mcepl, walters | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-06-24 20:59:35 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Stas Sergeev
2009-06-24 13:10:38 UTC
Created attachment 349249 [details]
illustration of the localized FTP
What's your locale (output of the program locale in the command line) and what's the language of your browser? Apparently we try to provide localized terminology in FTP and switching from UTF-8 to 8859-* encoding.
What's actually your problem with this?
> What's your locale (output of the program locale in the command line) and > what's the language of your browser? My locale is ru_RU.UTF-8 and the language of firefox is Russian. > What's actually your problem with this? I am not sure I understand what you say, but my problem is that this particular release of firefox doesn't allow me to select the ftp encoding, while the previous ones did that fine. My firefox is set up to have the 1251 encoding by default, and for some reasons, the default encoding is now the only encoding it allows for FTP. The selection via View->Encoding UI simply doesn't work. Whatever I select, it stays on 1251. That's the UI bug, the selection should work, as it always did before. It is not a locale-specific bug or whatever, just a simple UI bug. Selecting from the encoding list doesn't work. (In reply to comment #2) > > What's actually your problem with this? > I am not sure I understand what you say, but > my problem is that this particular release of > firefox doesn't allow me to select the ftp > encoding, while the previous ones did that fine. There is no such thing as "FTP encoding", these are just Firefox generated pages which presents structure of FTP directories. What I meant was asking you for some kind of use case where changing encoding could be useful? Could you give us a screenshot of the FTP directory in your browser, please? Is it unreadable? Thank you very much for your cooperation > There is no such thing as "FTP encoding", these are just Firefox generated > pages which presents structure of FTP directories. Yes, and View->Encoding dialog used to affect them, as well as the normal web pages. Now, it works only for the normal web pages, but not for the FTP pages, even if they are just the same pages. > Could you give us a screenshot of the FTP directory in your browser, please? > Is it unreadable? I'll make it now, and will attach. Yes, it is unreadable. And I repeat: this used to work before. Created attachment 349277 [details]
screenshot
I created a few files with the russian
names, and they are unreadable. If I would
be able to select UTF8, they would became
readable. That was possible in all the previous
releases of firefox, but not any more.
(In reply to comment #5) > I created a few files with the russian > names, and they are unreadable. If I would > be able to select UTF8, they would became > readable. That was possible in all the previous > releases of firefox, but not any more. OK, so it is just filenames, right? Hmm, that could be the issue. I suppose names of those remote files are not UTF-8 encoded, right? Can you by chance got their names in other ftp client with correct encoding? > OK, so it is just filenames, right? What else could it be on ftp? :) > I suppose > names of those remote files are not UTF-8 encoded, right? They _are_ utf-8 encoded. I created them so. > Can you by chance got > their names in other ftp client with correct encoding? Not too much of them allows to select the encoding, but firefox did. Now it doesn't. The encoding selection simply doesn't work when you browse ftp. Could you just try that yourself? Its not difficult, just try to change the encoding. It doesn't change. Just tried: even the command-line ftp client gets them right, as thay are utf8-encoded, and the locale is utf8 too. Please just check and see that the firefox doesn't change the encoding in this release. We filed this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=500282) and believe that it is more appropriate to let it be resolved upstream. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report. Just a few notes about the upstream report you filled: The test URL that you took from the screenshot, is my PC. It will now disappear, as I go to sleep and switch it off. :) You haven't mentioned that this always used to work before. That might be very important. I always enjoyed the fact that firefox has this feature while the IE does not (or I wasn't able to find). And now it have disappeared here as well. (In reply to comment #10) > Just a few notes about the upstream report you filled: > > The test URL that you took from the screenshot, is my PC. > It will now disappear, as I go to sleep and switch it off. :) > > You haven't mentioned that this always used to work before. > That might be very important. I always enjoyed the fact that > firefox has this feature while the IE does not (or I wasn't > able to find). And now it have disappeared here as well. I think the best thing to do is to join the bug upstream and correct my mistakes. |