unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Coding system robustness?
Date: Fri, 18 Mar 2005 19:33:46 +0100	[thread overview]
Message-ID: <x5acp0by7p.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87wts43jxx.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 18 Mar 2005 13:11:43 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> I'd like to know whether coding systems in general are supposed to be
>> robust, meaning that decoding some random byte string into the coding
>> system and reencoding it is guaranteed to deliver the same byte string
>> again?
>
> AFAIK, (encode-coding-string (decode-coding-string STR 'foo) 'foo)
> should always return STR, otherwise it's a bug.  With the
> introduction of eight-bit-*, this should be true of "all"
> coding-systems in Emacs-21, although IIRC some bugs were found in
> this area and fixed in Emacs-CVS (maybe for utf-8), but my memory is
> fuzzy.

Ok, that means I'll go for it.  I _know_ that XEmacs 21.4 is not
robust in that manner, and maybe I'll provide some customizable
workaround variable you can set to "raw-text" if necessary.  But if
you ask the XEmacs developers' opinion, they'll tell you that you are
mad to use mule-ucs in XEmacs 21.4, anyway.  Not that they could offer
any alternatives right now.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-03-18 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18 17:45 Coding system robustness? David Kastrup
2005-03-18 18:11 ` Stefan Monnier
2005-03-18 18:33   ` David Kastrup [this message]
2005-03-20  0:22     ` Richard Stallman
2005-03-19  1:08   ` Kenichi Handa
2005-03-19  9:10     ` David Kastrup
2005-03-19  0:52 ` Kenichi Handa
2005-03-19  3:09 ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x5acp0by7p.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).