Closed Bug 309608 Opened 19 years ago Closed 19 years ago

Save a "complete" Web page on my Finnish XP desktop, fail to open it

Categories

(Firefox :: File Handling, defect)

1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 263570

People

(Reporter: app, Unassigned)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fi-FI; rv:1.7.10) Gecko/20050717 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fi-FI; rv:1.7.10) Gecko/20050717 Firefox/1.0.6 If I save a copmplete Web page on my dekstop, I can not open it. See the Windows error message as attachment. Reproducible: Always
Attached image Screenshot of the error message (deleted) —
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050922 Firefox/1.6a1 ID:2005092205 WFM in branch, trunk and 1.0.7. Maybe an extension problem - have you tried it in the safe mode? http://kb.mozillazine.org/Safe_Mode_(Firefox)
saving a gmail page fails (too complex) I get page can not be loaded message. most other pages work.
Can you open it if the complete file/path name contains only US-ASCII chars? Perhaps dupe of Bug 263570?
Version: unspecified → 1.0 Branch
The error message in English: "The file <a file name with scandinavian characters rendered in MIME encoding "quoted-printable"> can not be found. Check the location and try again."
Yes, it works OK if I save to a path with US-ASCII only. My Finnish "Desktop" folder is the default of Finnish Windows XP, which is "...\Työpöytä". Those scnadinavian characters there seem to be the problem. My guess is, it gets translated to quoted-printable and passed to Windows, which expects Latin1 and treats it as a non-existing path. Note that the desktop is the default in Firefox for this operation.
Yes, this seems to be a duplicate of that. So that seems fixed, I am currently trying to figure out, fixed in what version? Anyway, I resolve this as a duplicate now. *** This bug has been marked as a duplicate of 263570 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
It is fixed in beta 1.5. I switched to that, although my extensions are now mostly broken. If there is a way to fix this without going to 1.5 and breaking extensions, that might be communicated somehow to the general public. List it in 1.0.x known issues, and just tell people to avoid file names with non-ASCII!
(In reply to comment #8) > It is fixed in beta 1.5. I switched to that, although my extensions are now > mostly broken. Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: