all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pmr@pajato.com, stephen@xemacs.org, ueno@unixuser.org,
	emacs-devel@gnu.org
Subject: Re: Need some help with Rmail/mbox
Date: Sun, 21 Sep 2008 18:07:10 -0400	[thread overview]
Message-ID: <jwvzlm117p7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <u7i95p694.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Sep 2008 23:56:55 +0300")

>> >> The only reliable way to do decoding in buffers is by using
>> >> the `destination' argument to decode-coding-region so that you can
>> >> decode from a unibyte buffer into a multibyte buffer.
>> > Why is that the only reliable method, and what do you suggest as the
>> > value of `destination' argument for it to DTRT?
>> As I said in my message: use the dest arg so as to "decode from
>> a unibyte buffer into a multibyte buffer", so `destination' should be
>> ... a multibyte buffer.
> And the source a unibyte one?

Yes, of course.

>> As for why it's the only reliable method, it's because:
>> >> Dealing with "bytes in a multibyte buffer" or with "non-ascii chars in
>> >> a unibyte buffer" (as is necessarily the case either as source or as
>> >> destination if you do the decoding in-place) is just too delicate in my
>> >> experience (and of course, it's also somewhat inefficient).
>> I'm not sure which part of the above paragraph is unclear.
> The fact that other methods are not 100% reliable does not yet mean
> that this one is.  I thought you had a more specific explanation why
> this method is reliable.

No, I don't have such an explanation, except that the most natural input
for decoding is a unibyte (string|buffer) and the most natural output is
a multibyte (string|buffer).  I'd expect that to be pretty obvious.


        Stefan





  reply	other threads:[~2008-09-21 22:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 16:02 Need some help with Rmail/mbox Paul Michael Reilly
2008-09-19  3:28 ` Stephen J. Turnbull
2008-09-19  5:35   ` Paul Michael Reilly
2008-09-19  9:32     ` Eli Zaretskii
2008-09-20  7:12     ` Stephen J. Turnbull
2008-09-20 10:04       ` Daiki Ueno
2008-09-20 10:19         ` Eli Zaretskii
2008-09-20 10:46           ` Daiki Ueno
2008-09-20 11:30             ` Eli Zaretskii
2008-09-20 23:33               ` Richard M. Stallman
2008-09-21  3:18                 ` Eli Zaretskii
2008-09-21 13:34               ` Stefan Monnier
2008-09-21 17:59                 ` Eli Zaretskii
2008-09-21 19:26                   ` Stefan Monnier
2008-09-21 20:56                     ` Eli Zaretskii
2008-09-21 22:07                       ` Stefan Monnier [this message]
2008-09-22  3:07                         ` Eli Zaretskii
2008-09-22  3:36                           ` Stefan Monnier
2008-09-22  3:41                           ` Daiki Ueno
2008-09-22  3:58                             ` Stefan Monnier
2008-09-22 18:48                               ` Eli Zaretskii
2008-09-22  4:31                         ` Kenichi Handa
2008-09-22 14:10                           ` Stefan Monnier
2008-09-24  0:56                             ` Kenichi Handa
2008-09-24  2:53                               ` Stefan Monnier
2008-09-24  3:48                                 ` Kenichi Handa
2008-09-22 15:24                           ` Paul Michael Reilly
2008-09-20 13:48         ` Stephen J. Turnbull
2008-09-21  0:57           ` Daiki Ueno
2008-09-22  9:14             ` Stephen J. Turnbull
2008-09-19  4:30 ` Richard M. Stallman
2008-09-19  4:30 ` Richard M. Stallman
2008-09-19  9:12 ` Eli Zaretskii

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=jwvzlm117p7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pmr@pajato.com \
    --cc=stephen@xemacs.org \
    --cc=ueno@unixuser.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.