From: ken <gebser@speakeasy.net>
To: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Re: replacing characters and whacky trans-buffer conversion
Date: Thu, 08 Mar 2007 07:16:45 -0500 [thread overview]
Message-ID: <45EFFEAD.7050808@speakeasy.net> (raw)
In-Reply-To: <266B0820-DD96-45C5-96B7-B564953313B9@Web.DE>
On 03/06/2007 11:28 AM somebody named Peter Dyballa wrote:
>
> Am 06.03.2007 um 16:15 schrieb ken:
>
>> An email comes in with this (emdash) character in it: –
>
> It's only an EN DASH, U+2013 (dec 8211, oct 20023).
Looking at it, it's obvious you're right. The author of the email used
it where an emdash should have been used instead. I guess I shouldn't
have blindly assumed the author was correct... should have trusted my
own eyes. Thanks for pointing that out... brings up another issue with
what I'm trying to do.
> There are only a few
> encodings that contain it:
>
> CP1250
> CP1251
> CP1252
> NeXT
> Mac-Greek
> Mac-Cyrillic
> Mac-Roman
> Adobe Standard Encoding
>
> (not complete, I presume). This character has in UTF-8 a representation
> of 0xE2 0x80 0x92, three bytes. It seems that somehow each of this three
> bytes is converted into some three byte representation. A malfunction in
> GNOME? (At least I had once such problems in Fedora Core 1.)
>
> Can you try to paste into an UTF-8 encoding buffer? Its mode-line should
> start with -u: (or -U: in GNU Emacs 23.0.0).
How do I open up a utf-8 buffer? I'd much prefer to do this just for
this one time, not change my emacs configuration to do it forever.
>
> --
> Greetings
>
> ~ O
> Pete ~~_\\_/%
> ~ O o
>
>
--
"Genius might be described as a supreme capacity for getting its
possessors into trouble of all kinds."
-- Samuel Butler
next prev parent reply other threads:[~2007-03-08 12:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 15:15 replacing characters and whacky trans-buffer conversion ken
2007-03-06 16:28 ` Peter Dyballa
2007-03-07 7:38 ` Matthew Flaschen
2007-03-07 9:59 ` Peter Dyballa
2007-03-08 12:16 ` ken [this message]
2007-03-08 16:31 ` Peter Dyballa
2007-03-08 20:43 ` ken
2007-03-08 23:14 ` Peter Dyballa
[not found] ` <mailman.688.1173395790.7795.help-gnu-emacs@gnu.org>
2007-03-09 14:28 ` Oliver Scholz
2007-03-07 20:48 ` ken
2007-03-07 21:03 ` ken
2007-03-07 21:30 ` Peter Dyballa
2007-03-08 1:11 ` ken
[not found] ` <mailman.627.1173316331.7795.help-gnu-emacs@gnu.org>
2007-03-08 7:50 ` Stefan Monnier
2007-03-08 10:40 ` ken
2007-03-08 11:55 ` ken
[not found] ` <mailman.648.1173350436.7795.help-gnu-emacs@gnu.org>
2007-03-09 1:51 ` Stefan Monnier
2007-03-09 10:15 ` ken
2007-03-09 13:14 ` Peter Dyballa
2007-03-09 15:54 ` ken
2007-03-09 16:13 ` Peter Dyballa
2007-03-09 18:41 ` Reiner Steib
2007-03-10 18:29 ` ken
2007-03-10 18:57 ` Reiner Steib
2007-03-10 19:00 ` Peter Dyballa
2007-03-10 19:12 ` Eli Zaretskii
2007-03-09 10:21 ` ken
2007-03-09 13:02 ` Peter Dyballa
[not found] ` <mailman.699.1173435731.7795.help-gnu-emacs@gnu.org>
2007-03-09 20:20 ` Stefan Monnier
2007-03-10 18:32 ` ken
[not found] ` <mailman.698.1173435330.7795.help-gnu-emacs@gnu.org>
2007-03-09 20:34 ` Stefan Monnier
2007-03-09 22:00 ` Oliver Scholz
[not found] <mailman.528.1173194164.7795.help-gnu-emacs@gnu.org>
2007-03-06 16:41 ` Oliver Scholz
2007-03-06 17:52 ` 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=45EFFEAD.7050808@speakeasy.net \
--to=gebser@speakeasy.net \
--cc=Peter_Dyballa@Web.DE \
--cc=help-gnu-emacs@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.
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).