From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: How to use base64-encode-region with MULE?
Date: 13 Jun 1999 03:43:35 +0200 [thread overview]
Message-ID: <m3lndo7u48.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Hrvoje Niksic's message of "13 Jun 1999 02:16:40 +0200"
Hrvoje Niksic <hniksic@srce.hr> writes:
> Well yes, but shouldn't the Base64 code proceed character by character
> and read the "decoded" characters from the buffer? That's what the
> code in XEmacs does, and to me it seems like the only sensible thing
> to do. Otherwise, you get the \201 junk in otherwise perfectly fine
> buffers.
Yup. The Emacs implementation encodes the internal representation.
One the one hand, that may seem totally weird. On the other hand,
Emacs has both multibyte and unibyte buffers, so this isn't all that
catastrophic for Emacs, while doing the same in XEmacs would be, er,
catastrophic.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-06-13 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-05 11:54 Kai.Grossjohann
1999-06-12 22:48 ` Lars Magne Ingebrigtsen
1999-06-12 23:29 ` Hrvoje Niksic
1999-06-12 23:57 ` Lars Magne Ingebrigtsen
1999-06-13 0:16 ` Hrvoje Niksic
1999-06-13 1:43 ` Lars Magne Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3lndo7u48.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).