Signature file path containing JPN chars is garbled

RESOLVED WORKSFORME

Status

SeaMonkey
MailNews: Message Display
P3
major
RESOLVED WORKSFORME
18 years ago
14 years ago

People

(Reporter: hirata masakazu, Assigned: Jean-Francois Ducarroz)

Tracking

({intl})

Trunk
Future
PowerPC
Mac System 9.x

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Select Signature file from Mail/News account settings and hit OK.
Reopen the settings.
The signature file is shown as a subdirectory which does not exist, and no
signature is added when you compose a message.
2000102312 MacTrunk
(Reporter)

Comment 1

18 years ago
On further analysis, I have realized that a new folder that resembles the folder
name originally picked in the settings dialog has been created.
I believe this is a well known problem with Unicode handling in directory in
MacOS8.6 and beyond.  Can Mozilla have a workaround for this?
Changing component to Internationalization.
Component: Composition → Internationalization
Summary: No signature file is recognized. → No signature file is recognized. (Unicode in file path problem?)

Updated

18 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Assignee)

Comment 2

18 years ago
accepting
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9

Updated

18 years ago
Keywords: intl

Comment 3

18 years ago
changing milestone to unknown.  It will get changed back when we figure out what
milestone to put this bug in.
Target Milestone: mozilla0.9 → ---

Updated

18 years ago
Keywords: nsbeta1

Updated

18 years ago
Keywords: nsbeta1 → nsbeta1-

Comment 4

18 years ago
marking nsbeta1-
Nominating for 0.8
Target Milestone: --- → mozilla0.8

Comment 6

18 years ago
nominating means changing the keywords, not the target milestone. We've already
rejected this for the nsbeta1 release that makes up mozilla0.8 and mozilla0.9 
Perhaps there's someone on the I18N team who wants to look at this in that period?
Target Milestone: mozilla0.8 → Future

Comment 7

17 years ago
Checked 05/15 trunk build on both Ja Mac and En Mac + Ja lang kit.

On Ja mac, the signature path is not garbled and the signature file contents
appears correctly in the mail compose window.

On a En Mac, the signature file path containing JPN chars appears garbled on
account manager window. But the signature file can be found when opening a mail
compose window. However if the signature file contains Japanese characters, the
signature appears garbled on mail compose window.
Changed the summary accordingly. 
QA Contact: esther → ji
Summary: No signature file is recognized. (Unicode in file path problem?) → Signature file path containing JPN chars is garbled

Comment 8

17 years ago
Marking as nsCatFood, as all users should be able to have a signature file work 
proberly.
Keywords: nsCatFood

Updated

17 years ago
Keywords: nsBranch

Updated

17 years ago
Component: Internationalization → Mail Window Front End

Comment 9

17 years ago
Marking nsbranch- as it was decided in the August bug triage that we wouldn't
have eenough time in eMojo to fix this.  Let's revisit for MachV.

Keywords: nsbranch-

Updated

17 years ago
Blocks: 99230

Comment 10

17 years ago
branch keyword cleanup.
Keywords: nsbranch
(Assignee)

Updated

17 years ago
Target Milestone: Future → mozilla0.9.7

Updated

17 years ago
Blocks: 107067

Updated

17 years ago
Keywords: nsbranch-

Updated

17 years ago
Target Milestone: mozilla0.9.7 → mozilla0.9.9

Updated

17 years ago
Keywords: nsbeta1-
Target Milestone: mozilla0.9.9 → Future

Updated

16 years ago
No longer blocks: 107067
(Reporter)

Comment 11

16 years ago
Seems fixed. Probably the same fix in; about: plugins displaying Japanese
QuickTime info.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 12

16 years ago
While this has been fixed, bug 66868 is still broken.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.