Closed Bug 55582 Opened 26 years ago Closed 23 years ago

MacRoman filenames/paths displayed incorrectly

Categories

(SeaMonkey :: UI Design, defect, P3)

PowerPC
Mac System 9.x
defect

Tracking

(Not tracked)

VERIFIED WONTFIX
Future

People

(Reporter: devsin, Assigned: trudelle)

References

Details

(Keywords: helpwanted, intl, Whiteboard: [rtm-])

Mozilla M18 2000100608, OS 9.0.4 - Mozilla cannot handle MacRoman file names nor paths. 1) Choose to save a file (of any type) 2) Add a (TM) to the file's name (by typing Option-2) 3) Choose save The (TM) special character appears as the Windows cp1252(?) equivalent. The resulting file does have the correct file name, but Mozilla should be able to display the characters correctly. This also occurs when trying to open a file whose path contains a special character (a folder named "Mozilla(TM) Folder," for example) and when choosing to open a document with a specific application (e.g. Mozilla(TM)) when downloading an unknown file type.
over to ftang
Assignee: don → ftang
I think the file widget need to handle the unicode conversion correctly.
Assignee: ftang → pinkerton
the file widget _is_ handling it correctly (as adam says, the file is created with the correct name), it's the d/l progress dialog that isn't. -->law, though maybe pchen would be a better person to fix it. nominating for rtm, but i'm sure it's well beyond too late for the 6.0 train. This is only cosmetic, there is no data loss.
Assignee: pinkerton → law
Severity: normal → minor
Keywords: rtm
Note: this happens everywhere in Mozilla, not just the download dialog. This occurs in any place where a special character (in applications, paths, filenames, etc.) might possibly be displayed.
nav triage team: too late for rtm schedule, so rtm-
OS: All
Whiteboard: [rtm-]
nav triage team: Ok, we'll look into this for beta1, but not promising much. Marking nsbeta1, p4, mozilla0.9.1, reassinging to pchen
Assignee: law → pchen
Keywords: nsbeta1
Priority: P3 → P4
Target Milestone: --- → mozilla0.9.1
Keywords: intl
nominating for dogfood (from sdagley's list of bugs that are good candidates for our next release)
Keywords: nsdogfood
Marking nsbeta1+, all right, really gotta nail this one this time. ;-)
Keywords: nsbeta1 → nsbeta1+
Keywords: nsCatFood
Keywords: nsdogfood
as discussed in nav team meeting, moving P4 and P5 nsbeta1+ bugs to Future.
Keywords: helpwanted
Target Milestone: mozilla0.9.1 → Future
nav triage: not an nscatfood issue. please explain how it fits the catfood criteria if you wish to renominate.
Keywords: nsCatFood → nsCatFood-
Severity: minor → normal
Priority: P4 → P3
Target Milestone: Future → mozilla0.9.2
Renominating for nsCatFood. TradeMarks and copy right issues extend past borders, and should be honored. If the user can't see the marks, thye have no need to honor the intellectual property of the company. Hence, this could be a legal issue and should be CatFood. Per Vishy's request, setting priority P2, so that we can triage with Nav for M0.9.2.
Keywords: nsCatFood- → nsCatFood
Priority: P3 → P2
vishy&jaime: on further discusssion, not a m0.9.2 issue, for now at least.
Keywords: nsCatFood → nsCatFood+
Priority: P2 → P3
Target Milestone: mozilla0.9.2 → mozilla0.9.3
nav triage -> m1.0.1
Target Milestone: mozilla0.9.3 → mozilla1.0.1
*** Bug 93157 has been marked as a duplicate of this bug. ***
-> default assignee
Assignee: pchen → trudelle
Target Milestone: mozilla1.0.1 → ---
Target Milestone: --- → Future
Mozilla 1.1, machineID 604 I think I found a similar case of this bug, and it is the closest I could find to my problem. Create a file name "ML2/ML3.xls", and try attaching it to an email. Show up in file area as something like "file:///NAME_OF_DISK/Desktop fold..." Normally, it would just show up as "ML2/ML3.xls" Now try to send the email, and you will get a dialog that states: "Sending of message Failed. Please verify that your Mail & Newsgroups account settings are correct and try again." Change the name of file to "ML2_ML3.xls" and all works as expected.
bug 55582, but 147075, and bug 189350 are clearly related in some way. Not sure if it's dupes or dependencies.
Mach-O handles ™ (TM) and other special characters successfully as Unicode. Mozilla CFM build is dead.
Status: NEW → RESOLVED
Closed: 23 years ago
OS: All → Mac System 9.x
Resolution: --- → WONTFIX
v
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.