And is there a good way of taking them out?
I've been playing around a bit with using b64 to embed images in HTML (and trying to stay within
the spec). I've noticed that with openssl's base64 encoder, the output files have newline characters @ every 65th column or so. This renders them useless, at least in Firefox and SeaMonkey (where this method usually works). After pasting the base64 from the output file into an HTML document, and adding the appropriate HTML tags, instead of a visible image I get a broken thumbnail. I already know why this is, having had some user-end experience with base64 (before either Outlook or Netscape knew how to decode it on the fly). My perception, phrased as a rule-of-thumb for the benefit of some who might argue its finer points, has always been the following:
Quote:
Originally Posted by Code Gods of the 1990s
Base64 encoding must be one continuous code stream or else it is invalid.
So what happened? Did someone find an application of this particular encoding where broken streams were more useful? Or even crucial?
At any rate, a sed or awk one-liner seems appropriate here. Anyone have a good one for this situation? One to remove newline characters?
BZT.
