Path: utzoo!utgpu!watserv1!watmath!att!news.cs.indiana.edu!spool2.mu.edu!samsung!uunet!world!spike
From: spike@world.std.com (Joe Ilacqua)
Newsgroups: news.software.b
Subject: Re: New USENET header: Language
Message-ID: <SPIKE.91Jan2155527@world.std.com>
Date: 2 Jan 91 20:55:27 GMT
Article-I.D.: world.SPIKE.91Jan2155527
References: <1990Dec22.081718.2109@looking.on.ca>
	<SPIKE.90Dec23141438@world.std.com> <ZM-+Y6D@b-tech.uucp>
	<SPIKE.90Dec30200625@world.std.com> <kd1oq1eo7C@herkules.sssab.se>
Sender: spike@world.std.com (Joe Ilacqua)
Organization: Software Tool & Die
Lines: 23
In-Reply-To: matoh@sssab.se's message of 2 Jan 91 09:17:49 GMT

In article <kd1oq1eo7C@herkules.sssab.se> matoh@sssab.se (Mats Ohrman) writes:
<spike@world.std.com (Joe Ilacqua) writes:
<>	As for multiple languages, list all the languages and dialects
<>in the "Language:" header and use a font or encoding scheme that gives
<>you the character sets you need.  Just because I post a message
<>encoded in ASCII doesn't mean you can't follow up in JIS, so long as
<>your posting server converts my text and sets the correct "Encoding:"
<>header.
<The problem is that there may not be any standard encoding for a specific
<language. For exemple, an article written in Swedish may have any of
<at least three different encodings, all being different "standards".
<The language don't give you enough information to choose encodings, and
<if it is the encoding you're after anyway, why don't specify it in the header.

	The way I look at it "Language:" is to allow humans to decide
if they can and want to read a message.  "Encoding:" specifies how
that language is encoded.  The fact that there are three ways to
encode Swedish does not change that fact that they language is
Swedish.

->Spike
-- 
The World - Public Access Unix - +1 617-739-9753  24hrs {3,12,24,96,192}00bps