From: Tiphaine Turpin <tiphaine.turpin@inria.fr>
To: 10919@debbugs.gnu.org
Subject: bug#10919: emacs-mule/utf-8 difference
Date: Thu, 01 Mar 2012 16:48:30 +0100 [thread overview]
Message-ID: <4F4F9A4E.50506@inria.fr> (raw)
In-Reply-To: <4F4F984D.2000901@inria.fr>
I just found a solution which seems to work: using emacs-internal
instead of emacs-mule. So it seems to be just a documentation problem
(or a problem with my reading of it).
Tiphaine
On 01/03/2012 16:39, Tiphaine Turpin wrote:
> Hi,
>
> I have a problem regarding coding systems:
>
> I'm using process-send-string to send substrings of a buffer through a
> socket, after setting the process encoding and decoding systems to
> emacs-mule.
> I expect the number of bytes written to match the byte-length of the
> substring as obtained by position-bytes, since the specification of
> position-bytes in emacs-devel is to always work with the emacs-mule
> encoding. From emacs-devel:
>
> "The byte sequence of a buffer after decoded is always in emacs-mule
> (in emacs-unicode-2 branch, it's utf-8). So, changing
> buffer-file-coding-system or any other coding-system-related variables
> doesn't affects position-bytes."
>
> However, this is not the case with 3bytes utf8 characters:
> position-bytes counts them as 3 bytes, but process-send-string wirtes
> 4 bytes.
>
> Setting the process coding systems for the socket to utf-8 solves the
> problem, but I don't think it will with other coding systems, even if
> I used buffer-file-coding-system instead, since position-bytes does
> not use it.
>
> What is the real expected behavior of these things, and how to make
> this correct ?
>
> Regards,
>
> Tiphaine Turpin
>
next prev parent reply other threads:[~2012-03-01 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 15:39 bug#10919: emacs-mule/utf-8 difference Tiphaine Turpin
2012-03-01 15:48 ` Tiphaine Turpin [this message]
2012-03-01 17:45 ` Stefan Monnier
2012-03-01 17:54 ` 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=4F4F9A4E.50506@inria.fr \
--to=tiphaine.turpin@inria.fr \
--cc=10919@debbugs.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 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.