To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.generalOpen lugnet.admin.general in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / General / 855
854  |  856
Subject: 
Re: Posting with MIME encoded FROM header
Newsgroups: 
lugnet.admin.general
Date: 
Tue, 19 Jan 1999 13:04:54 GMT
Viewed: 
1265 times
  
lehman@javanet.com (Todd Lehman) writes:

Hmm, I don't know.  At first I want to say no it shouldn't -- because it's
totally unreadable with that encoding.

This was my first reaction as well.  It has always been considered bad
and ugly to post anything MIME encoded on news.  But as you say
yourself, this practice is becoming increasingly common, so you are
probably going to be be confronted with it sooner or later.

But OTOH, maybe yes it should, because maybe modern newsreaders are
smart enough to decode that into 8-bit ISO characters on the screen
and not show garbage squiggly encoding characters.  But I bet that's
hoping too much.  :-)

It's certainly hoping to much to think that _all_ newsreaders should
decode MIME encoded headers.  But RFC2047 headers have been used a long
time already, so I think a lot of news/mail readers have the capability
by now.

Over here, it is common for people to have non-ASCII names, so the
alternatives are to send it along as 8bit chars, which means the
"Glöckner" becomes "Glvckner" if the mail passes through a site which
does not support 8 bits, or to MIME encode it.  And the latter is
becoming usual, even though some mail readers show the result as
"garbage".

I suspect this problem is going to become increasingly observed as more and
more people come onboard with ISO-8859-1 characters above 128.

Indeed, yes.  What's the status for the mail->news gateway, BTW?  If
there are people there with non-ASCII characters in their names, things
are bound to conflict sooner or later.  Unless they use exclusively
ASCII characters in their FROM headers, of course.

That way, the article would be stored on the server using native
ISO-8859-1 encoding rather than the unreadable ASCIIfications.

This sounds like a nice idea.

Fredrik



Message has 2 Replies:
  Re: Posting with MIME encoded FROM header
 
(...) Haven't encountered any problems yet (that have been reported, anyway) but I'll bet that if +128 characters aren't ISO-8859-1 encoded on the way out, the problem is going to pop up sooner or later. (...) I guess I'll need to stuff in an (...) (26 years ago, 19-Jan-99, to lugnet.admin.general)
  Re: Posting with MIME encoded FROM header
 
(...) (Just came across this old thread and realized this hadn't yet been fixed.) OK, I've just installed a filter which does this conversion based on the RFC 2047 specification. This eliminiates nasties like =?ISO-8859-1?Q?f=F2=...=20b=E2r?= in (...) (21 years ago, 27-May-03, to lugnet.admin.general, lugnet.admin.nntp)  

Message is in Reply To:
  Re: Posting with MIME encoded FROM header
 
(...) Hmm, I don't know. At first I want to say no it shouldn't -- because it's totally unreadable with that encoding. But OTOH, maybe yes it should, because maybe modern newsreaders are smart enough to decode that into 8-bit ISO characters on the (...) (26 years ago, 19-Jan-99, to lugnet.admin.general)

4 Messages in This Thread:


Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR