=================== BUG #2474: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=2474&group_id=1968
Changes by: Earl Hood <earl(_at_)earlhood(_dot_)com>
Date: 2003-Feb-05 12:56 (US/Central)
------------------ Additional Follow-up Comments ----------------------------
Changes have been made to readmail::MAILhead_get_disposition
to return addition values to address this problem,
including an optional return value to give an HTML
display name taking into account any charset specifications.
The various filters that use the routine have been updated.
Note, the actual physical filename is basically mapped
to the ASCII character domain since it is unknown what
the can be supported by the underlying OS. Of course,
this is only a concern when using the unsecure option of
saving attachments with filenames designated in the
message.
Changes are available in the latest snapshot and will
be part of the v2.6.0 release.
=================== BUG #2474: FULL BUG SNAPSHOT ===================
Submitted by: ehood Project: MHonArc
Submitted on: 2003-Feb-04 13:13
Category: MIME Filter Severity: 5 - Major
Bug Group: Incorrect Behavior Resolution: None
Assigned to: ehood Status: Open
Platform Version: All Perl Version: all
Component Version: <=2.5.14 Fixed Release:
Summary: non-ASCII encoded filenames not displayed properly for attachments
Original Submission: Reported by t_sugihara, character set encoding ignored
in non-ASCII encoded filenames when the filename is
displayed on message page for attachments. For multi-byte
encodings, the filename can looked garbled.
Follow-up Comments
*******************
-------------------------------------------------------
Date: 2003-Feb-05 12:56 By: ehood
Changes have been made to readmail::MAILhead_get_disposition
to return addition values to address this problem,
including an optional return value to give an HTML
display name taking into account any charset specifications.
The various filters that use the routine have been updated.
Note, the actual physical filename is basically mapped
to the ASCII character domain since it is unknown what
the can be supported by the underlying OS. Of course,
this is only a concern when using the unsecure option of
saving attachments with filenames designated in the
message.
Changes are available in the latest snapshot and will
be part of the v2.6.0 release.
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=2474&group_id=1968
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHONARC-DEV
