Jolly
Fri Oct 26 08:45:56 PDT 2007
In article <C347478F.44AC%raf44ael98@sbcglobal.net>,
Rafael Montserrat <raf44ael98@sbcglobal.net> wrote:
> On 10/25/07 10:23 PM, in article
> jollyroger-4DAAF9.00230326102007@news.supernews.com, "Jolly Roger"
> <jollyroger@pobox.com>
>
> > In article <C346B7D3.448C%raf44ael98@sbcglobal.net>,
> > Rafael Montserrat <raf44ael98@sbcglobal.net> wrote:
> >
> >> On 10/25/07 8:50 PM, in article
> >> jollyroger-842A87.22500125102007@news.supernews.com, "Jolly Roger"
> >> <jollyroger@pobox.com>
> >>
> >>> I would definitely give .jpg a shot, since Windows typically uses a
> >>> three-character convention for filename extensions.
> >>
> >> I see I didn't send .jpeg. Here's what I sent:
> >>
> >> I originally sent him eleven attachments with a total size of 4534 kb
> >> Five are .jfif
> >> Six are .jpg
> >>
> >> Is there any reason that having five .jfif would keep him from opening six
> >> .jpg?
> >
> > Not that I can think of... If you want, re-send the exact same message
> > to my email address and I'll tae a look.
>
> I sent it to your address. 11 attachments. Maybe you'd like a nice
> halloween costume. Holiday discount.
Well now I think it *must* be the 4-character .jfif extensions throwing
a wrench into things, because those files don't even show up correctly
in the attachment list of Office 2004's Entourage:
<
http://jollyroger.kicks-ass.org/jollyroger/JFIF/Entourage-JFIF.png>
Note that Entourage says the files have no filename extension. And if I
drag one out to my desktop, the file on the desktop has no filename
extension either.
I even forwarded the message to my Windows XP machine and Outlook shows
the same thing:
<
http://jollyroger.kicks-ass.org/jollyroger/JFIF/Outlook-JFIF.png>
What's very interesting is the message source does indeed show the
correct extensions!:
---
--B_3276156103_22611341
Content-type: application/applefile; name="10. Accessories.jfif"
Content-transfer-encoding: base64
Content-disposition: attachment;
filename="10. Accessories.jfif"
---
Strange, right? It seems Microsoft simply doesn't support four
character filename extensions (at least .jfif) very well.
I'm curious: Why do these images have the .jfif extension to begin with?
At any rate, I think the thing to do is shorten these filename
extensions to three characters. I suggest changing them to .jpg like the
rest of the images, since JFIF is really JPEG anyway. Doing this, in my
tests, allowed the receiver to open and view the images without a hitch.
--
Note: Please send all responses to the relevant news group. If you
must contact me through e-mail, let me know when you send email to
this address so that your email doesn't get eaten by my SPAM filter.
JR