Gnus development mailing list
 help / color / mirror / Atom feed
From: Jonas Steverud <d4jonas@dtek.chalmers.se>
Subject: Re: Decoding ISO8859-15 -- offending headers
Date: Sun, 18 Aug 2002 10:42:01 +0200	[thread overview]
Message-ID: <wtnu1lsy2w6.fsf@licia.dtek.chalmers.se> (raw)
In-Reply-To: <iluvg6vlxlh.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 31 Jul 2002 17:35:06 +0200")

Simon Josefsson <jas@extundo.com> writes:

[...]
> Ok.  Jonas, does using a non-ISO8859-1 locale modify the behaviour for
> your original problem?  What locale settings do you use?

I don't remeber what I have answered and the mailing list archive's
Glimps index "was not found" when I searched att gnus.org so I can't
check which article (the message-id) is was that offended Gnus.

My locales are accordingly:
On the Solaris where Emacs lives:
> locale
LANG=
LC_CTYPE=iso_8859_1
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=

I ssh from a Mac OS X running XFree86 with OrorborOSX 0.8b2 as WM and
there I have:
> env | egrep '^L[A,C]'
LANG=sv_SE
LC_CTYPE=iso_8859_1

Since I don't know the offending article I cannot (yet) check how the
locale affects Gnus. I do plan to drop the issue since it is not a
great matter - *very* few articles are a problem.

What is a greater problem (as a side note) is the \201 that is printed
in the Groups buffer for 0.06 and 0.07. (See other mails regarding
this.) They prevents me from upgrading... :-/ (Since they are so ugly.)

-- 
(          www.dtek.chalmers.se/~d4jonas/         !     Wei Wu Wei     )
(        Meaning of U2 Lyrics, Roleplaying        !  To Do Without Do  )



  parent reply	other threads:[~2002-08-18  8:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  6:33 Jonas Steverud
2002-07-26 19:39 ` Simon Josefsson
2002-07-27  9:09   ` Jonas Steverud
2002-07-27 14:03     ` Simon Josefsson
2002-07-27 15:17       ` Jonas Steverud
2002-07-27 20:45         ` Simon Josefsson
2002-07-27 21:42           ` Simon Josefsson
2002-07-28  8:46           ` Jonas Steverud
2002-07-28 14:04           ` Reiner Steib
2002-07-29 11:44             ` Simon Josefsson
2002-07-29 14:13               ` Reiner Steib
2002-07-31 15:35                 ` Simon Josefsson
2002-08-01  6:37                   ` Jonas Steverud
2002-08-18  8:42                   ` Jonas Steverud [this message]
2002-08-18 10:27                     ` Simon Josefsson
2002-08-18 10:46                       ` Jonas Steverud
2002-08-18 11:08                         ` Simon Josefsson
2002-08-18 11:38                           ` Jonas Steverud
2002-08-19  3:14                           ` Daiki Ueno
2002-08-19  6:53                             ` Jonas Steverud
2002-08-19  8:54                               ` Kai Großjohann
2002-08-19  9:13                                 ` Simon Josefsson
2002-08-19  9:12                             ` Simon Josefsson
2002-08-19 11:05                               ` Kai Großjohann
2002-08-19 14:28                                 ` Simon Josefsson
2002-08-19 17:02                                   ` Kai Großjohann
2002-08-19 17:13                                     ` Simon Josefsson

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=wtnu1lsy2w6.fsf@licia.dtek.chalmers.se \
    --to=d4jonas@dtek.chalmers.se \
    /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).