Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@metis.no>
Subject: UTF-8 (Was: More charset things)
Date: 14 Feb 1999 19:10:48 +0100	[thread overview]
Message-ID: <whn22gdffb.fsf_-_@viffer.oslo.metis.no> (raw)
In-Reply-To: Steinar Bang's message of "09 Feb 1999 09:05:56 +0100"

>>>>> Steinar Bang <sb@metis.no>:

>>>>> François Pinard <pinard@iro.umontreal.ca>:
>> That is why Lars could well decide, one of these days, to support
>> UTF-8 as an encoding (which it really is) on the same level as
>> Base64, and moreover, rather fun to implement.  It might be
>> convenient that Gnus do so as a contribution to the Unicode effort,
>> without really waiting for Emacs to do it.

One reason to support UTF-8 decoding and encoding, is that
son-of-son-of-1036 (or watchamacallit) 
	http://www.ietf.org/internet-drafts/draft-ietf-usefor-article-01.txt
seems to recommend UTF-8 for both the headers and bodies of news
messages. 

Hm... the way this works would probably be to have a UTF-8 decoding
that would always attempt to decode a news message and then revert to
a locale or newsgroup specific setting if the UTF-8 decoding breaks
down (use of the iso-8859-1 charset in the case of the no.*
hierarchy).

UTF-8 encoding should probably not be made default for a while yet.
At least it should be made newsgroup hierarchy dependent.

> But isn't UTF-8 support something that really should be done at the C
> level (like base64 is done in newer emacsen)?  Or am I thinking of
> UTF-7 here...? (does anyone have some handy online references?)

UTF-8 is defined in RFC2279
	ftp://ftp.ntnu.no/pub/rfc/rfc2279.txt

UTF-7 is defined in RFC2152
	ftp://ftp.ntnu.no/pub/rfc/rfc2152.txt

Both would probably be best off with decoding done in C.


  reply	other threads:[~1999-02-14 18:10 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-03 18:09 More charset things Lars Magne Ingebrigtsen
1999-02-04 14:56 ` Hrvoje Niksic
1999-02-04 17:08   ` Lars Magne Ingebrigtsen
1999-02-04 17:21     ` Hrvoje Niksic
1999-02-04 17:49       ` Lars Magne Ingebrigtsen
1999-02-05  0:47         ` Stephen J. Turnbull
1999-02-05  2:43           ` Hrvoje Niksic
     [not found]           ` <m3hft163aa.fsf@peorth.gweep.net>
1999-02-05 19:06             ` Vladimir Volovich
     [not found]               ` <m3sockqqjx.fsf@peorth.gweep.net>
1999-02-06 15:55                 ` Lars Magne Ingebrigtsen
     [not found]                   ` <m3lnia5922.fsf@peorth.gweep.net>
1999-02-07 21:02                     ` Hrvoje Niksic
1999-02-09 15:56                       ` Lars Magne Ingebrigtsen
1999-02-09 17:21                         ` Hrvoje Niksic
1999-02-09 17:31                           ` Alan Shutko
1999-02-09 17:37                           ` Lars Magne Ingebrigtsen
1999-02-09 18:06                             ` Hrvoje Niksic
1999-02-08 16:04                   ` Bill White
1999-02-09 16:04                     ` Lars Magne Ingebrigtsen
1999-02-06  8:17           ` Lars Magne Ingebrigtsen
1999-02-09 10:27           ` Displayed [ 0: Stephen J. Turnbull ] but it had lots of lines Alf-Ivar Holm
1999-02-09 16:14             ` Lars Magne Ingebrigtsen
1999-02-09 22:07           ` More charset things Jan Vroonhof
     [not found]           ` <m3hft163aa.fsf@p <byu2wv6xkb.fsf@bolzano.math.ethz.ch>
1999-02-09 22:13             ` Hrvoje Niksic
1999-02-07 20:43         ` François Pinard
1999-02-08  2:09           ` Martin Buchholz
1999-02-22 15:52             ` François Pinard
1999-02-08 14:49           ` Robert Bihlmeyer
     [not found]           ` <m37lttydo2.fsf@peorth.gweep.net>
1999-02-08  9:55             ` Kai.Grossjohann
1999-02-08 15:52             ` François Pinard
     [not found]               ` <m3n22ou09w.fsf@peorth.gweep.net>
1999-02-08 23:19                 ` François Pinard
1999-02-09  8:05               ` Steinar Bang
1999-02-14 18:10                 ` Steinar Bang [this message]
1999-02-09 16:03               ` Lars Magne Ingebrigtsen
1999-02-08 17:29             ` Karl Eichwalder
1999-02-08 22:03             ` James H. Cloos Jr.
1999-02-09  5:29               ` Russ Allbery
1999-02-09  7:33                 ` James H. Cloos Jr.
1999-02-10  2:13                   ` Stephen Zander
1999-02-11 10:09           ` Jan Vroonhof
1999-02-07 19:37       ` François Pinard
1999-02-08  0:06         ` Kenichi Handa
1999-02-07 19:35     ` François Pinard
1999-02-08 13:37       ` Simon Josefsson
1999-02-08 23:43         ` Kenichi Handa

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=whn22gdffb.fsf_-_@viffer.oslo.metis.no \
    --to=sb@metis.no \
    /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).