From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: "Ernest Adrogué" <nfdisco@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: python-shell-send-region uses wrong encoding?
Date: Tue, 29 Oct 2013 19:07:29 +0100 [thread overview]
Message-ID: <22C8B5B1-01A6-4307-B22A-0F7AF4CBA05C@Web.DE> (raw)
In-Reply-To: <20131029163426.GA29055@doriath.local>
Am 29.10.2013 um 17:34 schrieb Ernest Adrogué:
> in all these cases the sequence is converted into
> 0xF6, which is the UTF-16 encoding for "ö" that Python uses internally, as
> the output from repr() shows..
No!
UTF-16 is a text encoding that uses for each character in the BMP (Basic Multilingual Plane) 2 bytes or 16 bits – therefore the name. In UTF-16 ö is encoded as 0x00F6. (Above it uses twice 2 bytes, i.e. 4 bytes, which are distinct from UTF-32.)
--
Greetings
Pete
Make it simple, as simple as possible but no simpler.
– Albert Einstein
next prev parent reply other threads:[~2013-10-29 18:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 11:30 python-shell-send-region uses wrong encoding? Ernest Adrogué
2013-10-29 14:24 ` Drew Adams
2013-10-29 14:37 ` Ernest Adrogué
2013-10-29 16:00 ` Drew Adams
2013-10-29 16:54 ` Ernest Adrogué
2013-10-29 17:11 ` Eli Zaretskii
2013-10-29 14:26 ` Andreas Röhler
2013-10-29 14:55 ` Ernest Adrogué
2013-10-29 15:29 ` Andreas Röhler
2013-10-29 15:34 ` Peter Dyballa
2013-10-29 16:34 ` Ernest Adrogué
2013-10-29 17:15 ` Eli Zaretskii
2013-10-29 17:53 ` Ernest Adrogué
2013-10-29 19:10 ` Eli Zaretskii
2013-10-29 20:48 ` Ernest Adrogué
2013-10-29 18:07 ` Peter Dyballa [this message]
2013-10-29 20:37 ` Ernest Adrogué
2013-10-29 17:28 ` Stefan Monnier
2013-10-30 3:20 ` Stefan Monnier
2013-10-30 6:45 ` Andreas Röhler
2013-10-30 11:37 ` Stefan Monnier
2013-10-30 12:08 ` Yuri Khan
2013-10-30 12:45 ` Andreas Röhler
2013-10-31 14:30 ` Ernest Adrogué
2013-10-31 14:31 ` Ernest Adrogué
2013-10-31 17:54 ` Ernest Adrogué
2013-10-31 20:35 ` Stefan Monnier
2013-11-04 19:15 ` Stefan Monnier
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=22C8B5B1-01A6-4307-B22A-0F7AF4CBA05C@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=nfdisco@gmail.com \
/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.
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).