The email seems to be sent properly, at least as far as the encoding goes.
 If I do "view original" in gmail and cut and paste the base64 encoded
image into a new file and then decode the base64 encoded image, the picture
appears fine.  Perhaps some of the mail headers or sections dividers are
incorrect/non-standard?

Anyways, for those that would like to view it:

http://www.austin-lane.net/shovel.jpeg

Joe:  If you want me to delete it, please let me know, although be aware
that this listserv is archived onto a number of publicly viewable web sites
anyways.

If anyone is curious about the encoding used on the picture:
http://en.wikipedia.org/wiki/Base64

The reason it is done is that mail is not traditionally a safe conduit for
arbitrary binary data (like photos) - many mail gateways only accept
"normal" text, and so base64 is a way to take arbitrary binary data
(encoded as a sequence of base256 bytes) and put it into a sequence of 64
safe for email characters - each 6 bytes of the original is changed into 8
characters that each encode 6 bits (2^6 = 64).

Anyways, like they say, we don't say the shovel handle doesn't change from
shiny and new to weathered and old - rather we say the shiny new handle is
shiny new handle fully; and the old weathered handle is an old weathered
handle fully.

Thanks,

--Chris, writing from an actual computer, having used the emacs editor to
convert the image.


Thanks,

--Chris
[email protected]
+1-301-270-6524


On Mon, Nov 26, 2012 at 5:56 PM, Joe <[email protected]> wrote:

> Group,
>
> Aha, I see what is happening.
>
> The pics I sometimes paste into the rich-text edit window often become
> encoded in some funny way, and then the website cannot display them when
> the post is read online.
>
> Those who access these while mobile will waste many bytes receiving the
> wrongly-encoded data.
>
> I wonder what the correct way of encoding is.
>
> When I read the post online and use the "Read as Source" option (I think
> it is), I see a HUGE block of encoded gibberish after my several lines of
> plain ASCII typed message text.
>
> This shows that, although I pasted the image in the rich-text editor
> window, and I could SEE the image there, and then sent the message, that,
> nonetheless, the encoding of the image is not being done right, so that the
> image might be viewable when the message is read online.
>
> Part of the header that introduces the huge block of gibberish reads:
>
> Content-Type: text/html; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> My browser is the latest v. of Firefox; I open an image in a Firefox tab,
> "Copy" it with the mouse, and "Paste" it with the mouse into the edit
> window of a reply or message before sending.
>
> I don't know how to force the proper kind of encoding, nor do I know what
> the proper encoding protocol is.  I'll keep looking for clues to my error.
>
> I've tried this using MS-Explorer as the browser instead, and the same
> thing happens.
>
> --Joe
>
> > "Joe" <desert_woodworker@...> wrote:
> >
> > PS  I wasn't sure if the pic went out; when I look at the post on the
> website, it claims "Message truncated: larger than 64k".  But the jpg is
> 26.4k in size (so, some encoding is prob. being done; I still don't know
> why I intermittently have this prob., when attaching images in rich-text
> mode of the online editor).
>
>
>
>
> ------------------------------------
>
> Current Book Discussion: any Zen book that you recently have read or are
> reading! Talk about it today!Yahoo! Groups Links
>
>
>
>

Reply via email to