From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/23214 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: How to use base64-encode-region with MULE? Date: 13 Jun 1999 02:16:40 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: <87ogil3qfr.fsf@pc-hrvoje.srce.hr> References: <87lndp9evl.fsf@pc-hrvoje.srce.hr> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035160989 837 80.91.224.250 (21 Oct 2002 00:43:09 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:43:09 +0000 (UTC) Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id UAA07343 for ; Sat, 12 Jun 1999 20:17:22 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.1/8.9.1) with ESMTP id TAB14055; Sat, 12 Jun 1999 19:17:07 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sat, 12 Jun 1999 19:17:54 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id TAA17935 for ; Sat, 12 Jun 1999 19:17:44 -0500 (CDT) Original-Received: from pc-hrvoje.srce.hr (mail@pc-hrvoje.srce.hr [161.53.2.132]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id UAA07329 for ; Sat, 12 Jun 1999 20:16:44 -0400 (EDT) Original-Received: from hniksic by pc-hrvoje.srce.hr with local (Exim 2.05 #1 (Debian)) id 10sxx2-0004W8-00; Sun, 13 Jun 1999 02:16:40 +0200 Original-To: ding@gnus.org X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h writes: > Hrvoje Niksic writes: > > > > And, in Emacs 20.3 you have to be in a unibyte buffer. > > > > Why? Isn't it sufficient that all the characters are within [0,255] > > range? > > No -- é, for instance, is encoded internally as \201\040 (or > something). 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.