[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Wed, 20 Jul 2005 09:36:15 +0900
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)
In article <address@hidden>, Stefan Monnier <address@hidden> 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.
>> 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