Re: ASCII-only startup message?

[Random832]

On Tue, Dec 29, 2015, at 03:01, Yuri Khan wrote:
> On Tue, Dec 29, 2015 at 1:05 PM, Random832 <address@hidden>
> wrote:
> 
> > To take a step back and think about solving both problems... What
> > about a list of characters - to include, by default, quotation marks
> > and apostrophes and maybe a few other things like dashes - that are
> > allowed to be silently mapped to best-fit ASCII equivalents when
> > writing a buffer in a coding system that does not support them?
> 
> Bad idea. If the user fixes typography in a file and forgets to change
> the target encoding before saving, they risk losing their work.

Okay, how about, it prints an echo area message (but no confirmation
question, so no workflow interruption), and does not actually alter the
buffer (so they can save again after fixing the encoding, without having
lost anything)?