Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Jolly Roger <jollyroger@pobox.com>
Newsgroups: comp.sys.mac.system
Subject: Re: Newsreaders =?UTF-8?Q?=21=C2=A1=21?=
Date: 4 Nov 2013 01:13:24 GMT
Organization: People for the Ethical Treatment of Pirates
Lines: 46
Message-ID: <bdoalkFg0jkU6@mid.individual.net>
References: <l4jfnl$995$1@dont-email.me> <291020131010406196%Jean-Pierre.Kuypers@adresse.invalid> <l4q08h$erd$1@tota-refugium.de> <1lbkqbf.14r6lsg19nu7j9N%jamiekg@wizardling.geek.nz> <slrnl720ns.18sg.g.kreme@mbp55.local> <1lbll8q.sm5jc4p4e5ecN%jamiekg@wizardling.geek.nz> <slrnl735vn.1oju.g.kreme@mbp55.local> <1lblws8.8epkxihf8otuN%jamiekg@wizardling.geek.nz> <l4ss6h$7n8$1@tota-refugium.de> <1lbmhib.15zjg4s1ib1d4vN%jamiekg@wizardling.geek.nz> <l4t4e4$4cl$1@tota-refugium.de> <1lbml3j.1hc6k8z1gydbx6N%jamiekg@wizardling.geek.nz> <l4tdmb$3j4$1@tota-refugium.de> <slrnl74gco.4nf.t-usenet@ID-685.user.individual.de> <l51vpq$esq$1@tota-refugium.de> <l52ude$f8f$5@talisker.lacave.net> <slrnl7a0kq.8c2.t-usenet@ID-685.user.individual.de> <l53l74$hal$1@tota-refugium.de> <bdl84iFqrepU1@mid.individual.net> <1lbrd63.1rcrp9e1clkpbbN%jamiekg@wizardling.geek.nz> <bdlkuhFtdm3U1@mid.individual.net> <1lbrnq1.15xgsj1n3c1kxN%jamiekg@wizardling.geek.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net 4pLHmGLlHmvXD02KaHrICQMn7hgtKpA85+umiqjOeSYtwR9JWK
Cancel-Lock: sha1:5BS2TRGD7QfAK1JfFWV09Ok3iNU=
User-Agent: slrn/1.0.1 (Darwin)
Xref: csiph.com comp.sys.mac.system:51814

On 2013-11-03, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
> Jolly Roger <jollyroger@pobox.com> wrote:
>
>> On 2013-11-02, Jamie Kahn Genet <jamiekg@wizardling.geek.nz> wrote:
>> > Jolly Roger <jollyroger@pobox.com> wrote:
>> >
>> >> I'm using slrn. How can I tell if it's configured to handle UTF-8
>> >> correctly?
>> >
>> > From your headers: "Content-Type: text/plain; charset=utf-8". So slrn at
>> > least thinks it's encoding your posts with UTF-8, and I'm fairly certain
>> > that is in fact the case :-) Try posting some of the expanded charset.
>> 
>> ¡™£¢∞§¶•ªº
>> 
>> Yuck. I was expecting to see something more like this:
>> 
>> <http://jollyroger.kicks-ass.org/unicode.png>
>> 
>> Wonder what's wrong...
>
> That is what I see in MacSOUP. Are you saying you don't see that in your
> own post in slrn? Well, search me *shrug* I've only ever used tin in
> recent memory when it comes to command line Usenet clients. You're the
> expert here compared to me, JR! :-)

Nope, I see:

<http://jollyroger.kicks-ass.org/unicode2.png>

I bet you it's the font I'm using in Terminal. I'm going to try
switching to something more mainstream to see if that changes things.

> Either way, I mean who really uses the full charset of Unicode in
> Usenet? I think it's just one or two rabid Unicode fans (that someone
> can be that much of a fan of character encodings bothers even someone as
> geeky as me...) stirring the pot, here.

It's more of an irritation to me, because it means I won;t be able to
read some posts.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR