On 2024-06-21 10:34, Michael Kjörling wrote:
> On 21 Jun 2024 09:52 +0200, from mutt-users@mutt.org (Jan Eden via
> Mutt-users):
> >> I noticed that non-ascii characters in recipient names become garbled
> >> recently (in Mutt 2.2.13, installed via Homebrew
On 21 Jun 2024 09:52 +0200, from mutt-users@mutt.org (Jan Eden via Mutt-users):
>> I noticed that non-ascii characters in recipient names become garbled
>> recently (in Mutt 2.2.13, installed via Homebrew):
>>
>> "Basi´c, P."
>>
>> becomes
&g
On 2024-06-21 09:44, Jan Eden via Mutt-users wrote:
> Hi,
>
> I noticed that non-ascii characters in recipient names become garbled
> recently (in Mutt 2.2.13, installed via Homebrew):
>
> "Basi´c, P."
>
> becomes
>
> "Basi´c, P."
>
>
Hi,
I noticed that non-ascii characters in recipient names become garbled
recently (in Mutt 2.2.13, installed via Homebrew):
"Basi´c, P."
becomes
"Basi´c, P."
The effect is not visible when composing the message in mutt, but in the
sent message (in the Sent mailbox),
Dear Chris,
try to set 'rfc2047_parameters = yes' in Your .muttrc.
Please refer to the explanation in the mutt help for this parameter,
too.
Hope, this helps You,
Markus
On 3.03.14, Chris Down wrote:
On 1.5.22, when displaying attachments that are encoded in KOI-8 (and
presumably
On 1.5.22, when displaying attachments that are encoded in KOI-8 (and
presumably other non-ASCII character encodings), the attachment name in
the attach menu is displayed in a quoted-printable format, and is not
decoded to the current locale. Is there some way to enable decoding of
the attachment
Hello,
I would like to ask if any of you has seen following...
When I send out email and add attachments, that contain non-ascii
characters in the name (such as žluťoučký-kůň.txt),
the name is not correctly viewed in some clients. For example Outlook 2010
+ changes it into ATT-00185.txt or
On Tue, Jun 10, 2008 at 04:59:17AM +1200, Chris Bannister wrote:
> On Mon, Jun 09, 2008 at 03:18:30PM +0200, Harald Weis wrote:
> > The query function `Q' does not seem to support non-ASCII characters.
> > My abook contains a lot of French and German names.
> > Is th
On Mon, Jun 09, 2008 at 03:18:30PM +0200, Harald Weis wrote:
> The query function `Q' does not seem to support non-ASCII characters.
> My abook contains a lot of French and German names.
> Is there a way to use a regular expression to search for say `Cédric'?
> Of course,
The query function `Q' does not seem to support non-ASCII characters.
My abook contains a lot of French and German names.
Is there a way to use a regular expression to search for say `Cédric'?
Of course, `dric' helps, but it's not nice.
Thank you in advance,
Harald Weis
On 27.09.2007 (12:22), Kyle Wheeler wrote:
> If someone took a utf-8-encoded email (read: sequence of bytes) and
> handed it to a file reader that only understood windows-1252, it would
> get rendered, it would just look wrong. For example, this character: ☺
> That character is not in windows-125
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, September 27 at 05:50 PM, quoth Eyolf Østrem:
>> 3. Along similar lines, windows-1252 contains the entire set of
>> possible values, 0 to 255, and has a character assigned to each.
>> Thus, no email will *ever* not match windows-1252. Th
On 27.09.2007 (09:11), Kyle Wheeler wrote:
> >set assumed_charset ="us-ascii:windows-1252:latin-1:utf-8"
>
> For what it's worth, this setting is pretty pointless for most
> Westerners. The best setting for Westerners is:
>
> set assumed_charset="windows-1252"
>
> The reason this is bette
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, September 27 at 12:56 PM, quoth Eyolf Østrem:
>This puzzled me at first, because I didn't know where that latin1
>coding came from, but I assume it is because of send_charset or
>assumed_charset, right?
Yup. It's send_charset that matte
On 25.09.2007 (23:16), Ionel Mugurel Ciobica wrote:
> > Eyolf Østrem/Oestrem/=?iso-8859-1?Q?=D8strem?=
>
> That is not Unicode. Unicode would be this:
>
> | Eyolf =?UTF-8?Q?=C3=98strem?=
This puzzled me at first, because I didn't know where that latin1
coding came from, but I assume it is becau
On Tue, Sep 25, 2007 at 10:03:30AM +0200, Eyolf Østrem wrote:
> There was a thread a short while ago about non-ascii characters in the
> "From" name during which I changed my name from Oestrem to Østrem, and
> it works.
> Today, I happened to find one of my own messages in
On 25-09-2007, at 21h 35'01", Kyle Wheeler wrote about "Re: More on non-ascii
chars in headers"
> On Tuesday, September 25 at 11:16 PM, quoth Ionel Mugurel Ciobica:
> >> Eyolf =?iso-8859-1?Q?=D8strem?=
> >
> >That is not Unicode. Unicode would b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, September 25 at 11:16 PM, quoth Ionel Mugurel Ciobica:
>> Eyolf =?iso-8859-1?Q?=D8strem?=
>
>That is not Unicode. Unicode would be this:
>
>| Eyolf =?UTF-8?Q?=C3=98strem?=
>
>This is the (safe) way to transfer no
On 25-09-2007, at 10h 03'30", Eyolf Østrem wrote about "More on non-ascii chars
in headers"
> Not so nice to look at... Is there still some setting I should
> make/change, or is this down to marc.info's inability to handle
> unicode characters?
>
> Eyol
On 25.09.2007 (09:02), Kyle Wheeler wrote:
> The answer is, unfortunately, no. There's no way to specify
> "alternatives" in your From header. Plus, even if there was, it's
> doubtful that marc.info would support them, given that it doesn't seem
> interested or capable of decoding the existing R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, September 25 at 10:03 AM, quoth Eyolf Østrem:
>Eyolf =?iso-8859-1?Q?=D8strem?=
>
>Not so nice to look at... Is there still some setting I should
>make/change, or is this down to marc.info's inability to handle
>unicode characters?
The
On 25.09.2007 (04:13), Jiang Qian wrote:
> > Not so nice to look at... Is there still some setting I should
> > make/change, or is this down to marc.info's inability to handle
> > unicode characters?
> Your name appears(including "Ø)" fine on my mutt display. My default
> encoding is unicode($LANG
On Tue, Sep 25, 2007 at 10:03:30AM +0200, Eyolf Østrem wrote:
> Eyolf =?iso-8859-1?Q?=D8strem?=
RFC 2822 (is that the right number?) does not allow non-ascii characters
in headers, and there is another RFC that describes how to encode
non-ascii characters in headers. The above is your n
On Tue, Sep 25, 2007 at 10:03:30AM +0200, Eyolf Østrem wrote:
> There was a thread a short while ago about non-ascii characters in the
> "From" name during which I changed my name from Oestrem to Østrem, and
> it works.
> Today, I happened to find one of my own messages in
There was a thread a short while ago about non-ascii characters in the
"From" name during which I changed my name from Oestrem to Østrem, and
it works.
Today, I happened to find one of my own messages in a search of the
list at http://marc.info/?l=mutt-users, and there, my name
On Thu, Aug 01, 2002 at 05:14:59PM +1000, Erik Christiansen wrote:
> On Wed, Jul 31, 2002 at 09:57:49AM -0400, Mark J. Reed wrote:
>
> > If you use the vim editor for composing messages, then you can
> > set up digraphs to enter non-ASCII characters;
> [...]
>For so
On Wed, Jul 31, 2002 at 09:57:49AM -0400, Mark J. Reed wrote:
> If you use the vim editor for composing messages, then you can
> set up digraphs to enter non-ASCII characters; it also supports a
> completely general but more awkward input method where you can type
> control-V fol
essages, then you can
set up digraphs to enter non-ASCII characters; it also supports a
completely general but more awkward input method where you can type
control-V followed by the decimal character code of the character
you want, or the letter 'u' followed by the hexadecimal Unicode co
On Wed, Jul 31, 2002 at 02:16:09PM +0200, Roman Neuhauser wrote:
> % setenv LANG en_US.ISO8859-1
> or
> % export LANG=en_US.ISO8859-1
> depending on the type of shell you use.
> permanent fix lies in your shell's start up files. export $LANG with
> appropriate value from
> Date: Wed, 31 Jul 2002 13:58:48 +0200
> From: Erik van der Meulen <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: Display of non-ascii chars
>
> On Wed, Jul 31, 2002 at 01:46:24PM +0200, Roman Neuhauser wrote:
>
> > looks like you have $LANG s
On Wed, Jul 31, 2002 at 01:46:24PM +0200, Roman Neuhauser wrote:
> looks like you have $LANG set to C, POSIX, or something like that.
> what happens if you just cat(1) the message (i. e. view it w/o any
> intervening program)? i'd guess it won't come up "right" either.
Thanks a lot f
> Date: Wed, 31 Jul 2002 13:32:49 +0200
> From: Erik van der Meulen <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Display of non-ascii chars
>
> Dear all, I have some issue with the displaying of non-ascii chars in my
> mail. I have to admit that I am not 10
Dear all, I have some issue with the displaying of non-ascii chars in my
mail. I have to admit that I am not 100% sure that this is a mutt-issue
or more shell or terminal related. Sorry if it is off-topic, I have
tried all kinds of things to get this right.
If an incoming mail contains accents
Recently, more and more emails are coming in where non-ASCII characters
are showing up in the sender's name or the message subject line. This
causes problems in Mutt's index mode. On a VT100 terminal, these
characters are displayed as a question mark ("?"). But ASCII chara
g my locale settings are right, but I've tried many different combos.
I'm currently using iso01-f16 font, and LC_CTYPE=es_ES.iso-8859-1, bitchx,
mc, lynx and other apps are doing right with my setup, but Mutt doesn't, or
at least, it doesn't as it (IMHO) should.
I can't
On Sat, Apr 24, 1999 at 07:45:11PM +0200, Dr. Matthias Prinz wrote:
> I use mutt under Linx with X11 inside an xterm.
> I use iso-8859-1 encoding.
>
> Now: non-ascii-chars like the german umlauts äüö are coded correctly,
> but displayed as a question-mark.
> What can I do t
Hi,
I've installed mutt recently.
I use mutt under Linx with X11 inside an xterm.
I use iso-8859-1 encoding.
Check out the headers of this e-mail for more details.
The pager is set to builtin.
Now: non-ascii-chars like the german umlauts äüö are coded correctly,
but displayed as a que
37 matches
Mail list logo
