encoding warnings replying to iOS/MacOS msgs

[Matt Price]

Hi,

I'm not sure if this is an mu4e error,  something related to message mode, or a problem with my text encoding set up.  Pretty well every time I reply ot certain respondents -- I think all of the are Apple users -- I get an error similar to this one:
-----------
These default coding systems were tried to encode text
in the buffer ‘1490704406.29de897ad18730e9.ansul:2,S’:
  (utf-8-unix (618 . 4194274) (619 . 4194176) (620 . 4194196) (623 .
  4194274) (624 . 4194176) (625 . 4194201) (1904 . 4194242) (1905 .
  4194217))
However, each of them encountered characters it couldn’t encode:
  utf-8-unix cannot encode these:       
\342\200\211 \342\200\224
Click on a character (or switch to this window by ‘C-x o’
and select the characters by RET) to jump to the place it appears,
where ‘C-u C-x =’ will give information about it.

Select one of the safe coding systems listed below,
or cancel the writing with C-g and edit the buffer
   to remove or modify the problematic characters,
or specify any other coding system (and risk losing
   the problematic characters).

  raw-text no-conversion
--------------------

This has been going on for about a month. In fact it appears that UTF-8-unix DOES support these characters -- if I forward one of these messages to myself, the fancy characters -- usually apostrophes and n or m dashes -- come through fine:


> Yes, would be very hard—we’ll be in Florence.

I have the following lines in my customize settings:

'(current-language-environment "UTF-8")
'(mm-coding-system-priorities (quote (utf-8-emacs raw-text utf-8-hfs-unix)))

I have only the very vaguest understanding of text encodings. Does anyone here have any suggestions for next steps in trying to manage this issue?

Thank you!

Matt

[Matt Price]

I see this has already been reported and a temporary fix discussed:
https://groups.google.com/forum/#!topic/mu-discuss/NJgRONE7Xuk