Re: freebsd, mutt, unicode

[mal content <artifact.one@xxxxxxxxxxxxxx>]

Hello!

> >| LC_CTYPE: en_GB.UTF-8
> >| LC_MESSAGES: en_GB.UTF-8
>
>     You can remove both variables: LANG suffices. What give:
>
> | $ locale
> | $ locale --all-locales | grep ^en_

$ locale
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_ALL=

$ locale -a | grep ^en_
en_AU.ISO8859-1
en_AU.ISO8859-15
en_AU.US-ASCII
en_AU.UTF-8
en_CA.ISO8859-1
en_CA.ISO8859-15
en_CA.US-ASCII
en_CA.UTF-8
en_GB.ISO8859-1
en_GB.ISO8859-15
en_GB.US-ASCII
en_GB.UTF-8
en_IE.UTF-8
en_NZ.ISO8859-1
en_NZ.ISO8859-15
en_NZ.US-ASCII
en_NZ.UTF-8
en_US.ISO8859-1
en_US.ISO8859-15
en_US.US-ASCII
en_US.UTF-8

>
> > The current relative .muttrc settings:
> >| set send_charset="iso-8859-1:utf-8"
> >| reset charset
>
>     Remove both lines.

Okay, they're gone.

> >| set config_charset="us-ascii"
>
>     I'm not sure that makes sense: What charset contain your [Mm]uttrcs
> and all sourced files including aliases?

They're definitely all ASCII, but I've removed this line too.

> > Still, no unicode.
>
>     You mean special chars are still octalised \320\223 and such, as if
> they were not printable? That could be not well installed locales, or...

Yes, all non-ascii characters come out octalised.

> What gives:
>
> | $ printf "\0320\0223" | iconv -f UTF-8 -t UTF-8 | hex
> | D0 93

I get the same output - 'd0 93'.

cheers,
M