202353 - [mach-o] BinHex attachment is saved but can't be read correctly

Status: RESOLVED INVALID

(MailNews Core :: Attachments, defect)

Description

[Cavin Song]

Send yourself a jpeg attachment in binhex encoded format (you can use Eudora to
do this), receive the msg and save the binhex attachment to a local file. Then
double click on the saved file, nothing shows up at this point. The application
which could render jpeg files should be launched and you should be able to view
the jpeg file.

Comment 1

[Cavin Song]

What I found out is that the saved file contains LF (\n), instead of CR (\r),
which makes StuffIt fails to decode binhex data correctly.

The CFM build uses CR and it works fine.

Note that the saved (binhex) file contains data like:

(This file must be converted with BinHex 4.0)

:(R"QAf&XBQ&ZD@9I-M8i-$)`-epbCA9dCA*c,QT`C`!!!!!!!!!!!!!!!!"mc3!
!!!"EH[rBrq!!%%T'58B!!3)!!'3!C!!!rq`!%84eBfYj!!%!"!!!!#J!!2rZ!#&
. . .

Comment 2

[Cavin Song]

> What I found out is that the saved file contains LF (\n), instead of CR (\r),
> which makes StuffIt fails to decode binhex data correctly.
>
Actually StuffIt Expander 7.0 can handle both formats and it's only the older version of 
StuffIt (version 6.x I think) that can't handle files containing LFs. So if StuffIt Expander 7.0 
is the default app to launch when you double click on the saved files then it should work 
just fine.

> Note that the saved (binhex) file contains data like:
>
> (This file must be converted with BinHex 4.0)
>
> :(R"QAf&XBQ&ZD@9I-M8i-$)`-epbCA9dCA*c,QT`C`!!!!!!!!!!!!!!!!"mc3!
> !!!"EH[rBrq!!%%T'58B!!3)!!'3!C!!!rq`!%84eBfYj!!%!"!!!!#J!!2rZ!#&
> . . .
>
It works this way for Mac only (I guess we rely on StuffIt Expander to decode the binhex 
data for us). Windows actually decodes the binhex data and saves the binary data into 
the files. 

Comment 3

[Jo Hermans]

isn't this fixed by bug 192602 ?

Comment 4

[jwq]

 This appears to have been an end of line character handling bug in Stuffit Expander prior to version 7. Perhaps it is best resolved as invalid?

Comment 5

[jwq]

While the passage of time has seen the BinHex encoding system become as obsolete as the classic Mac OS from which it originated, as suggested by me in comment #4 the original report appeared to not be a bug in the core code.