set-process-filter-multibyte and etc.

[Kenichi Handa]

In article <address@hidden>, address@hidden (Kim F. Storm) writes:
>>  The only question is when to check
>>  default-enable-multibyte-characters.  When a process is
>>  created, or just before calling a filter?  I think the
>>  former is more like file I/O.  And it may be ok to have a
>>  function set-process-filter-multibyte which can change the
>>  multibyteness of a string to a filter on the way.

> Good points.  Also, there could be a new `:multibyte BOOL' argument to
> make-network-process to initialize the filter multibyteness of the new
> process; specifying this would override the setting of
> default-enable-multibyte-characters.

>>  Or, was the intention of set-process-multibyte actually
>>  set-process-filter-multibyte?

> At least, that was the problem I was looking at when I suggested it,
> so yes.

I've just installed changes for set-process-filter-multibyte
and etc.  I added the followings to etc/NEWS.  Could people
please fix my English.

---
Ken'ichi HANDA
address@hidden

** New function `set-process-filter-multibyte' sets the multibyteness
of a string given to a process's filter.

** New function `process-filter-multibyte-p' returns t if
a string given to a process's filter is multibyte.

** A filter function of a process is called with a multibyte string if
the filter's multibyteness is t.  That multibyteness is decided by the
value of `default-enable-multibyte-characters' when the process is
created and can be changed later by `set-process-filter-multibyte'.

** If a process's coding system is raw-text or no-conversion and its
buffer is multibyte, the output of the process is at first converted
to multibyte by `string-to-multibyte' then inserted in the buffer.
Previously, it was converted to multibyte by `string-as-multibyte',
which was not compatible with the behaviour of file reading.

** New function `string-to-multibyte' converts a unibyte string to a
multibyte string with the same individual character codes.