From: "Eli Zaretskii" <eliz@gnu.org>
Subject: Re: How to find "bad" characters that cannot be saved using some encoding
Date: Mon, 08 Nov 2004 10:19:32 +0200 [thread overview]
Message-ID: <01c4c56b$Blat.v2.2.2$d2230720@zahav.net.il> (raw)
In-Reply-To: <107e75b8.0411071600.76156474@posting.google.com> (steve.tolkin@fmr.com)
> From: steve.tolkin@fmr.com (Steven Tolkin)
> Date: 7 Nov 2004 16:00:19 -0800
>
> According to this old message fixing this was on some TODO list.
> Was this ever done?
Yes. The current development version shows the problematic characters
in the *Warning* buffer.
prev parent reply other threads:[~2004-11-08 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 0:00 How to find "bad" characters that cannot be saved using some encoding Steven Tolkin
2004-11-08 8:19 ` Eli Zaretskii [this message]
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='01c4c56b$Blat.v2.2.2$d2230720@zahav.net.il' \
--to=eliz@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).