when saving web page "complete" subfiles not loaded if title is in FARSI(PERSIAN)




Downloads API
11 years ago
9 years ago


(Reporter: Amin Diary, Unassigned)


(Depends on: 1 bug)

Firefox Tracking Flags

(Not tracked)





11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

hi dear FireFox!
I'm an Iranian user of you and want tell you when I browse persian(farsi)
pages that their's page titles are farsi,and save them you(firefox 1.5 and 2)
can't open them after saving!!! but IE can!
and since you (firefox) are more better than IE please fix this bug!

your lover
Amin Diary 

Reproducible: Always

Steps to Reproduce:
1.open a farsi titled URL.
2.save page.
3.open page that saved.

Actual Results:  
cannot open the page, but IE can!!!

What do you mean by "can't open"?

When I use the en-US Firefox 2 on Windows XP as in your user agent I always get the page opened, but it doesn't always look right. Is that what you mean?

In both Firefox and IE, if I save as just the web page then most of the images and styles aren't applied because they're specified as relative values. Same on both as far as I can tell.

In IE if I choose the .mht archive option I get a complete mess when I open it, it appears to have lost the character encoding.

When I choose to save as "Web Page, complete" then the results look much better in IE. Both FF and IE appear to save all the same pieces, in the same-named <title>_files directory (correctly done in Persian). But in the main html file Firefox has re-written the source, and instead of referencing "<title>_files/whatever" they all look like "____%20_____%20____/whatever" and thus aren't found.

Assuming that's what you mean I can confirm it. It's not a security issue however; clearing that checkbox because all it's doing is hiding the bug from people who could fix it.

Axel: could you help me find a home for this i18n bug?
Assignee: nobody → l10n
Group: security
Ever confirmed: true
Summary: if save a page that it's title is in full FARSI(PERSIAN) language firefox can't open it after saving → when saving web page "complete" subfiles not loaded if title is in FARSI(PERSIAN)

Comment 2

11 years ago
This seems to be a problem in the download manager.

If I click on the link in the download manager, I get to

but when I look at the explorer and open the page from there, it is at


Seems that the download manager is giving the wrong link to click at. Probably it's lossy converting to ascii somewhere.
Assignee: l10n → nobody
Component: General → Download Manager
QA Contact: general → download.manager

Comment 3

11 years ago
i mean thaf FF can't open! for example save this page to your computer http://www.cloob.com/  and double click on the file: جامعه مجازي ايرانيان.htm so u can see what i mean!!!! ;)


11 years ago
Depends on: 239279, 282285

Comment 4

10 years ago
The same problem on a german WinXp when using Characters about ASC 127 in the HTML filename when saving a Web page.

My example:
HTML name: Äußerlich.html
Directory name: Äußerlich-Dateien
Image ref. in the saved HTML file: <img src="%C4u%DFerlich-Dateien/picture.jpg">

This is the normal ISO-8859-1 encoding.
%C4 = 196 = Ä (I guess on US keybord: Alt + 0 (NUM) + 1 + 9 + 6)
%DF = 223 = ß (I guess on US keybord: Alt + 0 (NUM) + 2 + 2 + 3)

Adding a <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> helps nothing.

When loading the picture from the Äußerlich-Dateien directory direct in FireFox the Pathname ist:

Again I'm guessing, but this seems to be a UTF8 encoding.

I solved this proplem by loading the HTML file in Notepad.exe and exchanging the text
by the text
using the Search and Exchange dialog from the notepads Edit menu.

Now the HTML file works fine, but an automated function in FireFox would be nice ;-)

I didn't test this with CSS files and other filetypes!


9 years ago
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.