From: "Alexandre Oberlin" <please@nospam.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Single unrecognized character wrecks entire display
Date: Wed, 22 Aug 2012 11:36:21 +0200 [thread overview]
Message-ID: <op.wjfrmvhndp0apa@eucalyptus> (raw)
In-Reply-To: mailman.7220.1345329241.855.help-gnu-emacs@gnu.org
Thank you Peter for your answer.
> Yes! When you try save a faulty "text" in UTF-8 then GNU Emacs will name
> the faulty codes.
The problem is that it names a full list as bad characters, when only one.
utf-8-mac cannot encode these: \351 \350 \351 \342 \351 \234 \350 \350
\311 \240
How can I spot the true non utf-8 without trying them all?
Windows, c'est un peu comme le beaujolais nouveau: à chaque nouvelle
cuvée on sait que ce sera dégueulasse, mais on en prend quand même, par
masochisme.
Masochisme ou obligation ?
Alexandre
On Sun, 19 Aug 2012 00:33:25 +0200, Peter Dyballa <Peter_Dyballa@web.de>
wrote:
>
> Am 18.08.2012 um 18:35 schrieb Alexandre Oberlin:
>
>> Is there a way to quickly spot the offending character within emacs in
>> such cases ?
>
> Yes! When you try save a faulty "text" in UTF-8 then GNU Emacs will name
> the faulty codes. \234 is such a faulty code. In HEX it's (U+00)9C –
> obviously an 8-bit control character. With \240 or U+00A0 you have again
> a text character.
>
> œ is U+0153 or \523. You need to update your translator.
>
> --
> Greetings
>
> Pete
>
> Windows, c'est un peu comme le beaujolais nouveau: à chaque nouvelle
> cuvée on sait que ce sera dégueulasse, mais on en prend quand même, par
> masochisme.
>
>
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
next prev parent reply other threads:[~2012-08-22 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 16:35 Single unrecognized character wrecks entire display Alexandre Oberlin
2012-08-18 22:33 ` Peter Dyballa
[not found] ` <mailman.7220.1345329241.855.help-gnu-emacs@gnu.org>
2012-08-22 9:36 ` Alexandre Oberlin [this message]
2012-08-22 15:18 ` Peter Dyballa
[not found] ` <mailman.7419.1345648764.855.help-gnu-emacs@gnu.org>
2012-08-24 13:46 ` Alexandre Oberlin
2012-08-24 14:54 ` Alexandre Oberlin
2012-08-24 15:08 ` Peter Dyballa
2012-08-24 15:01 ` Peter Dyballa
2012-08-22 15:01 ` Stefan Monnier
2012-08-24 13:13 ` Alexandre Oberlin
2012-08-25 3:07 ` 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=op.wjfrmvhndp0apa@eucalyptus \
--to=please@nospam.com \
--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).