Composing in utf8 from latin1 terminal

[Derek Martin]

On Thu, Oct 25, 2018 at 06:14:18PM +0100, Nuno Silva wrote:
> > Also, depending on exactly why you're doing this multi-locale stuff,
> > an even better solution may be to let Mutt's send_charset handle it
> > for you.  
[...]
> But, if I understood the purpose of send_charset correctly, it only
> affects the encoding of the outgoing message. It won't change the
> encoding with which mutt reads the temporary file after I close the text
> editor, will it?

No, but why would you care?  It's just an intermediate data encoding.
What I'm saying is, forget about your latin1 terminal, do EVERYTHING
in Unicode, and let Mutt send the data out as latin1 if appropriate.
This may not be appropriate for your use case--it comes down to your
reason for using a latin1 terminal to run Mutt in.  I can't think of a
good reason to do that any longer... so my assumption is your end goal
is to produce an outgoing message in latin1 so some recipients who
can't yet handle Unicode properly can read it.

If your purpose is something else, that may not work, but like I said
I can't think of a reason why you'd need to do that.  A unicode
terminal should have no trouble letting you enter Portuguese (or
whatever other language) so long as your locale is correct (and
consistent across all programs) and your IME is configured properly.
Then Mutt can convert to latin1 to send.

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mutt.org/pipermail/mutt-users/attachments/20181025/8a0f58dc/attachment.asc>