From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, raman@users.sourceforge.net
Subject: Re: suggestion: function: buffer-bytes
Date: Mon, 09 Jul 2007 11:44:47 +0900 [thread overview]
Message-ID: <E1I7jF1-0002Nl-B8@etlken.m17n.org> (raw)
In-Reply-To: <jwvk5teoqvj.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 05 Jul 2007 10:42:31 -0400)
In article <jwvk5teoqvj.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > But for the use case I needed, namely someone composing blog
> > entries using nxml-mode,
> > and then building up an http post message from what they created,
> > the position-bytes solution does work.
> If it worked in some case, it was only by accident, unless they specifically
> decided to use emacs-mule as the coding system for their file (and to switch
> wholesale to utf-8 at the exact time they upgrade their Emacs), which would
> be rather unusual.
Right. By the way, currently emacs-mule uses 2-bytes, for
instance, for Latin-1 characters, and UTF-8 also uses
2-bytes for them. So, in the case of sending a Latin-1 text
to a process with UTF-8, position-bytes solution works just
by chance.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2007-07-09 2:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 0:18 suggestion: function: buffer-bytes T. V. Raman
2007-07-01 1:39 ` Stefan Monnier
2007-07-01 2:40 ` T. V. Raman
2007-07-01 6:31 ` David Kastrup
2007-07-01 8:22 ` Kenichi Handa
2007-07-01 12:39 ` Stefan Monnier
2007-07-02 0:48 ` Kenichi Handa
2007-07-01 17:47 ` T. V. Raman
2007-07-02 1:11 ` Kenichi Handa
2007-07-04 16:31 ` T. V. Raman
2007-07-05 14:42 ` Stefan Monnier
2007-07-09 2:44 ` Kenichi Handa [this message]
2007-07-01 19:34 ` Eli Zaretskii
2007-07-02 0:55 ` Kenichi Handa
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=E1I7jF1-0002Nl-B8@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@users.sourceforge.net \
/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.