Samuel Bronson writes:
On Wed, Oct 20, 2010 at 10:23 PM, Stephen J. Turnbull
<stephen(a)xemacs.org> wrote:
> text/* media. Files where magic number can be used to determine
the
> coding are by definition binary.
Er, that's basically what the facility I'm thinking of is used for.
Ah, OK. File-coding, strictly defined as handling text encodings, is
a hot button with me; it's the main reason I started using (GNU) Emacs
again in the early 90s, after missing the whole post-TECO/MockLisp/
Why-I-Must-Start-GNU interlude. Unfortunately, it was originally
implemented with only one goal: keeping the multiple Japanese feet
(ISO-2022-JP, Shift JIS, EUC-JP, and various Unicode TFs) from
stepping on each other. This worked fine in the world (the
Universities of Tokyo and Osaka) it was designed for, but .... gah.
XEmacs actually implements a more somewhat general facility that could
be used for, say, gzip decoding (any zero-lookahead stream processing,
actually), but it's not used that way in practice. :-(
Yeah, care is definitely needed, and that sounds like the facility I
was thinking of. I remember it being used to detect (some) zip files
by content when they didn't have names ending in .zip;
Well, currently XEmacs doesn't use it for that. The only thing it's
used for is detecting rich-text-format mail (and even that presumably
isn't used by real MUAs like Gnus and VM).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta