unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: string-as-unibyte
Date: Wed, 20 Jul 2005 09:36:15 +0900	[thread overview]
Message-ID: <E1Dv2ZL-0003hq-00@etlken> (raw)
In-Reply-To: <87wtnmg9iw.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 19 Jul 2005 10:26:31 -0400)

In article <87wtnmg9iw.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>  If a multibyte string is given to mac-code-convert-string,
>>  and the string is made mutlibyte by string-to-multibyte from
>>  the raw-byte sequence (ex. inserting a file by raw-text in a
>>  mutlibyte buffer and extracting a string by
>>  buffer-substring), using Fstring_as_unibyte is correct.

> Indeed, but sadly so.  In order to make it clear that the multibyte string
> is expected to only contain single-byte chars (including eight-bit-* chars),
> a comment is in order.

I agree.

>>  Please note that we don't have Fstring_to_unibyte because it
>>  should work the same way as Fstring_as_unibyte.

> Actually no.  string-to-unibyte should signal an error if it encounters
> a non-ascii non-eight-bit-* char.

Ah, hmmm, you are right.  I remember to implement it in
emacs-unicode.

---
Kenichi Handa
handa@m17n.org

      reply	other threads:[~2005-07-20  0:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 21:33 string-as-unibyte Stefan Monnier
2005-07-18 22:41 ` string-as-unibyte YAMAMOTO Mitsuharu
2005-07-18 23:52   ` string-as-unibyte YAMAMOTO Mitsuharu
2005-07-19  2:50     ` string-as-unibyte Kenichi Handa
2005-07-19  2:56   ` string-as-unibyte Kenichi Handa
2005-07-19  3:49     ` string-as-unibyte YAMAMOTO Mitsuharu
2005-07-19 14:26     ` string-as-unibyte Stefan Monnier
2005-07-20  0:36       ` Kenichi Handa [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

  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=E1Dv2ZL-0003hq-00@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).