Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!world!spike
From: spike@world.std.com (Joe Ilacqua)
Newsgroups: news.software.b
Subject: Re: New USENET header: Language
Message-ID: <SPIKE.90Dec30200625@world.std.com>
Date: 31 Dec 90 01:06:25 GMT
References: <1990Dec22.081718.2109@looking.on.ca>
	<SPIKE.90Dec23141438@world.std.com> <ZM-+Y6D@b-tech.uucp>
Sender: spike@world.std.com (Joe Ilacqua)
Organization: Software Tool & Die
Lines: 25
In-Reply-To: zeeff@b-tech.ann-arbor.mi.us's message of 24 Dec 90 03:29:33 GMT

In article <ZM-+Y6D@b-tech.uucp> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
<Putting the character set in the header limits us to only one language per 
<article.  I'd much prefer to see some escape mechanism in the body.  
<This would allow things like an english posting with a proper xxx 
<language name in the signature.  

	Read my message again.  I said put the encoding method in the
header, I did not say the encoding method had to be a font There is no
reason "Encoding:" could not just specify a method of switching fonts.
In fact I would go as far as to say that 'Encoding: JIS' is just that,
it sez this article uses JIS escape codes to change fonts.

	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.

	I want to know alot about the form of an article and I do not
want to grovel through the text trying to figure it out.

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