Gnus development mailing list
 help / color / mirror / Atom feed
From: Pavel.Janik@inet.cz (Pavel Janík ml.)
Cc: ding@gnus.org
Subject: Re: People with From: <mail@domain.com>
Date: 25 Apr 2000 15:36:36 +0200	[thread overview]
Message-ID: <m3ya62z4ij.fsf@SnowWhite.inet.cz> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 25 Apr 2000 13:04:14 +0200"

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

   From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
   Date: Tue, 25 Apr 2000 13:04:14 +0200

Hi,

   > Hm.  When I eval the following code, I get the right thing:
   > 
   > (mail-extract-address-components "Kai.Grossjohann@cs.uni-dortmund.de (Kai Großjohann)")
   > 
   > I get the same thing with gnus-extract-address-components.

And if you have

(set-language-environment "czech")

in the .emacs as I have? But in your headers there is:

From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=)

So mail-extr should correctly parse it (because there is a specification of
the charset) and return your address and your name correctly even if I have
different language environment. But it does not for me, cause I have czech
language environment chosen. But how is my language environment connected to
the mail-extract-... function? I do not know. But I think there is an error
somewhere...

If mail-extr is only getting


[-- Attachment #2: Type: text/plain, Size: 495 bytes --]

From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)

ie. without ?iso-8859-1?q? things in it, then the caller is buggy because it
should inform mail-extr of the charset used or if it does, the function does
not use this information and use language-environment.

   > FWIW, I see your name correctly, including the `ml.'.  (What does that
   > mean, btw?)

:-) ml. is like jr. in english. Hmm, I should probably read how to use
personality in Gnus.
-- 
Pavel Janík ml.
Pavel.Janik@inet.cz

  parent reply	other threads:[~2000-04-25 13:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-22  9:55 Pavel.Janik
2000-04-22 11:09 ` Lars Magne Ingebrigtsen
2000-04-23 20:07   ` Pavel.Janik
2000-04-24 14:31     ` Lars Magne Ingebrigtsen
2000-04-24 17:04       ` Pavel Janik ml.
2000-04-24 18:39         ` Kai Großjohann
2000-04-24 18:56           ` Pavel Janík ml.
2000-04-25 11:04             ` Kai Großjohann
2000-04-25 11:38               ` Lars Magne Ingebrigtsen
2000-04-25 11:35                 ` Kai Großjohann
2000-04-25 20:03                   ` Florian Weimer
2000-04-25 20:15                     ` Kai Großjohann
2000-04-26 17:14                       ` Florian Weimer
2000-04-26 17:29                         ` Shenghuo ZHU
2000-04-26 18:06                           ` Florian Weimer
2000-04-26 18:15                             ` Shenghuo ZHU
2000-04-25 13:36               ` Pavel Janík ml. [this message]
2000-04-25 14:47                 ` Kai Großjohann
2000-04-25 15:31                   ` Pavel Janík ml.
2000-04-25 17:10                     ` Kai Großjohann
2000-04-25 10:45           ` Florian Weimer
2000-04-25 11:11             ` Kai Großjohann
2000-04-25  6:42 ` Jaap-Henk Hoepman
2000-04-26 14:05 ` Erik Toubro Nielsen
2000-04-26 20:59   ` Pavel Janík ml.
2000-04-28  2:00   ` Shenghuo ZHU

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3ya62z4ij.fsf@SnowWhite.inet.cz \
    --to=pavel.janik@inet.cz \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).